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

Druid docs need best practices for handling time zones #2356

Closed
drcrallen opened this issue Jan 29, 2016 · 4 comments
Closed

Druid docs need best practices for handling time zones #2356

drcrallen opened this issue Jan 29, 2016 · 4 comments

Comments

@drcrallen
Copy link
Contributor

Documentation on druid.io needs to have best practices around timezones. Currently all the docs really say is to set user.timezone to UTC, but don't really give much other information if you don't want to use UTC in queries or query results. Examples of how to issue queries in other timezones and how to ensure results return in the timezone you desire would be helpful.

@du00cs
Copy link
Contributor

du00cs commented Feb 1, 2016

Ingestion with UTC is nice, what you care about maybe more likely related to query side. Granularity Doc mentioned that

   "granularity":{"type": "period", "period": "P1D", "timeZone": "America/Los_Angeles", "origin": "1970-01-01T20:30:00-08:00"}

drcrallen added a commit to metamx/druid that referenced this issue Feb 1, 2016
@fjy fjy closed this as completed in #2364 Feb 1, 2016
navis pushed a commit to navis/druid that referenced this issue Jun 10, 2016
@PanYifeng
Copy link

I have some problem about timezone. I am in China and I want to set my timezone to Standard Time in China. I tried many, such as "Asian/Beijing", "Asian/Shanghai" and "Asian/Chongqing". But none of them work as expected. Who can tell me what's wrong and list the valid timezone values?
Any ideas would be appreciated!

@gianm
Copy link
Contributor

gianm commented May 18, 2017

@PanYifeng, there is a list on wikipedia here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. An offset should also work, like "+08:00" or "-03:00".

@PanYifeng
Copy link

@gianm Thank you! On referring to List_of_tz_database_time_zones, I found I had made a spelling mistake. As I replaced "Asian/Shanghai" with "Asia/Shanghai", the problem was solved.

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

No branches or pull requests

4 participants