[
https://issues.apache.org/jira/browse/HIVE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521681#comment-16521681
]
Hive QA commented on HIVE-18729:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12928888/HIVE-18729.branch-3.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/12062/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12062/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12062/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12928888/HIVE-18729.branch-3.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12928888 - PreCommit-HIVE-Build
> 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
> Attachments: 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)
