Hi @zhaojiandong, this behavior is intentional: Druid always uses UTC, 
regardless of system time zone. This makes the parsing behavior consistent even 
if, for example, your Druid machines and Hadoop machines aren't running in the 
time zone. I think a better way to address #6343 is to add a "timeZone" feature 
to the TimestampSpec object. Then Druid could use that instead of UTC, if a 
user provides it. What do you think?

[ Full content available at: 
https://github.com/apache/incubator-druid/pull/6344 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to