You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2018/06/23 02:56:00 UTC

[jira] [Work started] (HIVE-18729) Druid Time column type

     [ https://issues.apache.org/jira/browse/HIVE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on HIVE-18729 started by Jesus Camacho Rodriguez.
------------------------------------------------------
> Druid Time column type
> ----------------------
>
>                 Key: HIVE-18729
>                 URL: https://issues.apache.org/jira/browse/HIVE-18729
>             Project: Hive
>          Issue Type: Task
>          Components: Druid integration
>            Reporter: slim bouguerra
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Blocker
>
> I have talked Offline with [~jcamachorodriguez] about this and agreed that the best way to go is to support both cases where Druid time column can be Timestamp or Timestamp with local time zone. 
> In fact, for the Hive-Druid internal table, this makes perfect sense since we have Hive metadata about the time column during the CTAS statement then we can handle both cases as we do for another type of storage eg ORC.
> For the Druid external tables, we can have a default type and allow the user to override that via table properties. 
> CC [~ashutoshc] and [~nishantbangarwa]. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)