Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use UTC instead of default timezone for creation date in CAT endpoint #12636

Merged
merged 1 commit into from Aug 4, 2015

Conversation

s1monw
Copy link
Contributor

@s1monw s1monw commented Aug 4, 2015

this change was added recently which uses default timezone for the creation
date on CAT endpoints. We should be consistent and use UTC across the board.
This commit adds #getDefaultTimzone() to forbidden API and fixes the REST tests.

Relates to #11688
@nik9000 do you wanna take a look since you merged #11688

this change was added recently which uses default timezone for the creation
date on CAT endpoints. We should be consistent and use UTC across the board.
This commit adds #getDefaultTimzone() to forbidden API and fixes the REST tests.

Relates to elastic#11688
@rmuir
Copy link
Contributor

rmuir commented Aug 4, 2015

looks good

s1monw added a commit that referenced this pull request Aug 4, 2015
Use UTC instead of default timezone for creation date in CAT endpoint
@s1monw s1monw merged commit 9b34273 into elastic:master Aug 4, 2015
@s1monw s1monw deleted the forbid_default_timezone branch August 4, 2015 12:54
@nik9000
Copy link
Member

nik9000 commented Aug 4, 2015

see http://build-us-00.elastic.co/job/es_core_master_window-2008/1920/testReport/org.elasticsearch.test.rest/Rest0IT/test__yaml_cat_indices_10_basic_Test_cat_indices_output_/ for a related failure

I didn't realize it'd spit out Z there. I was trying to test with the -Dtests.timezone and it wasn't taking. Nor did I realize we were consistent about UTC - its good that we are though.

@nik9000
Copy link
Member

nik9000 commented Aug 4, 2015

looks good to me too

@s1monw
Copy link
Contributor Author

s1monw commented Aug 4, 2015

I didn't realize it'd spit out Z there. I was trying to test with the -Dtests.timezone and it wasn't taking. Nor did I realize we were consistent about UTC - its good that we are though.

yeah it's better to be consistent and our timezone randomization will cause it to fail which is good too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants