hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-18729) Druid Time column type
Date Sun, 24 Jun 2018 21:21:00 GMT


Hive QA commented on HIVE-18729:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
was found in seen patch url's cache and a test was probably run already on it. Aborting...

This message is automatically generated.

ATTACHMENT ID: 12928888 - PreCommit-HIVE-Build

> Druid Time column type
> ----------------------
>                 Key: HIVE-18729
>                 URL:
>             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

View raw message