[
https://issues.apache.org/jira/browse/HIVE-15850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesus Camacho Rodriguez updated HIVE-15850:
-------------------------------------------
Comment: was deleted
(was: GitHub user jcamachor opened a pull request:
https://github.com/apache/hive/pull/145
HIVE-15850: Proper handling of timezone in Druid storage handler
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jcamachor/hive HIVE-15850
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/145.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #145
----
commit 059df15af406a60832851a36ea214edb268339b9
Author: Jesus Camacho Rodriguez <[email protected]>
Date: 2017-02-09T09:18:48Z
HIVE-15850: Proper handling of timezone in Druid storage handler
----
)
> Proper handling of timezone in Druid storage handler
> ----------------------------------------------------
>
> Key: HIVE-15850
> URL: https://issues.apache.org/jira/browse/HIVE-15850
> Project: Hive
> Issue Type: Bug
> Components: Druid integration
> Affects Versions: 2.2.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Critical
>
> We need to make sure that filters on timestamp are passed to Druid with
> correct timezone.
> After CALCITE-1617, Calcite will generate a Druid query with intervals
> without timezone specification. In Druid, these intervals will be assumed to
> be in UTC (if Druid is running in UTC, which is currently the
> recommendation). However, in Hive, those intervals should be assumed to be in
> the user timezone. Thus, we should respect Hive semantics and include the
> user timezone in the intervals passed to Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
