[ 
https://issues.apache.org/jira/browse/TAJO-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095552#comment-15095552
 ] 

ASF GitHub Bot commented on TAJO-1925:
--------------------------------------

Github user blrunner commented on the pull request:

    https://github.com/apache/tajo/pull/853#issuecomment-171153500
  
    Rebased. Basically, Tajo column partition focus on Hive partition 
compatibility. Currently, Hive just created timestamp partition directories 
using date format. I think that Tajo just need to follow current Hive version 
rule. Because even if we implement long value time for timestamp partition 
directory, Hive can't handle it. 


> Improve hive compatibility with TIMESTAMP partition column.
> -----------------------------------------------------------
>
>                 Key: TAJO-1925
>                 URL: https://issues.apache.org/jira/browse/TAJO-1925
>             Project: Tajo
>          Issue Type: Improvement
>          Components: Catalog, Physical Operator
>    Affects Versions: 0.11.0, 0.12.0
>            Reporter: Jaehwa Jung
>            Assignee: Jaehwa Jung
>             Fix For: 0.12.0
>
>         Attachments: TAJO-1925.patch, TAJO-1925_2.patch, TAJO-1925_3.patch
>
>
> -Currently, Tajo allow to use TIMESTAMP column as a partition key. But if 
> users use TIMESTAMP partition column, Tajo doesn't keep the original 
> TIMESTAMP values. Actually, Tajo automatically converts TIMESTAMP values to 
> STRING literals which are accepted in the format YYYY-MM-DD HH:MM:SS. As a 
> result, Tajo can't keep mills of second and can't provide right hive 
> compatibility-
> We need to support hive compatibility for all partition column types. But 
> when using TIMESTAMP partition column, users might not get correct partitions 
> occasionally because tajo partition name is different from hive partition 
> name. Actually, Tajo automatically converts TIMESTAMP values to STRING 
> literals which are accepted in the format YYYY-MM-DD HH:MM:SS. But Hive 
> automatically converts it to STRING literals which are accepted in the format 
> YYYY-MM-DD HH:MM:SS.MS. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to