[
https://issues.apache.org/jira/browse/TRAFODION-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TRAFODION-3115 started by Anoop Sharma.
-----------------------------------------------
> Support nanoseconds(9) precision for Timestamp columns
> ------------------------------------------------------
>
> Key: TRAFODION-3115
> URL: https://issues.apache.org/jira/browse/TRAFODION-3115
> Project: Apache Trafodion
> Issue Type: Improvement
> Reporter: Anoop Sharma
> Assignee: Anoop Sharma
> Priority: Minor
>
> Traf supports max fractional precision of 6 (microseconds) for Timestamp
> columns.
> It prevents values with fractional precision greater than 6 digits to be
> inserted into these columns.
> This becomes a bigger issue when dealing with Hive tables that have existing
> data with nanoseconds(9) precision. Selecting that data returns an error and
> causes queries to fail. Using a CAST to truncate data to timestamp(6) doesn't
> work either.
> Example:
> From Traf: create table hive.hive.ts (a timestamp);
> From Hive: insert into ts values ('2018-01-01 10:10:10.123456789');
> From Traf: selecting data from table 'ts' returns error:
> >>select * from hive.hive.ts;
> *** ERROR[8415] The provided DATE, TIME, or TIMESTAMP is not
> valid and cannot be converted. Source data:
> 2018-01-01 10:10:10.123456789
> --- 0 row(s) selected.
>
> >>select cast(a as timestamp(6)) from hive.hive.ts;
> *** ERROR[8415] The provided DATE, TIME, or TIMESTAMP is not
> valid and cannot be converted. Source data:
> 2018-01-01 10:10:10.123456789
> --- 0 row(s) selected.
>
> This Jira is filed to add support for max precision of 9 for Timestamp
> columns. of Traf and Hive tables.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
