[
https://issues.apache.org/jira/browse/TAJO-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaehwa Jung updated TAJO-1925:
------------------------------
Description:
-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.
was: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
> When using TIMESTAMP column as a partition key, Tajo need to keep keep the
> original TIMESTAMP values.
> -----------------------------------------------------------------------------------------------------
>
> Key: TAJO-1925
> URL: https://issues.apache.org/jira/browse/TAJO-1925
> Project: Tajo
> Issue Type: Bug
> Components: Catalog, Physical Operator
> Affects Versions: 0.11.0, 0.12.0
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Priority: Critical
> Fix For: 0.12.0, 0.11.1
>
>
> -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)
