[ https://issues.apache.org/jira/browse/HIVE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesus Camacho Rodriguez resolved HIVE-18729. -------------------------------------------- Resolution: Fixed Fix Version/s: 3.2.0 4.0.0 Tests run as part of HIVE-20213. Pushed to master, branch-3. Thanks for reviewing [~ashutoshc] > 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 > Fix For: 4.0.0, 3.2.0 > > Attachments: HIVE-18729.01.branch-3.patch, HIVE-18729.01.patch, > HIVE-18729.branch-3.patch, HIVE-18729.patch > > > 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)