You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Anoop Sharma (JIRA)" <ji...@apache.org> on 2018/04/23 18:46:00 UTC
[jira] [Updated] (TRAFODION-3040) Support nanosecond fractional
precision for time,timestamp, interval columns
[ https://issues.apache.org/jira/browse/TRAFODION-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anoop Sharma updated TRAFODION-3040:
------------------------------------
Summary: Support nanosecond fractional precision for time,timestamp, interval columns (was: Support nanosecond fractional precision for time,timestamp interval columns)
> Support nanosecond fractional precision for time,timestamp, interval columns
> ----------------------------------------------------------------------------
>
> Key: TRAFODION-3040
> URL: https://issues.apache.org/jira/browse/TRAFODION-3040
> Project: Apache Trafodion
> Issue Type: Improvement
> Reporter: Anoop Sharma
> Assignee: Anoop Sharma
> Priority: Minor
>
> Trafodion supports max of 6 digits(microseconds) of fractional precision for timestamp, time and interval second datatypes.
> Besides restricting traf columns to microseconds, it also prevents reading of external hive data inserted with nanosecond precision. An error is returned when that data is selected. That same data could be accessed directly from hive shell.
>
> From hive:
> hive> select * from thivens;
> OK
> thivens.a
> *2018-01-01 10:10:10.123456789*
> Time taken: 0.198 seconds, Fetched: 1 row(s)
> hive>
> From traf:
> *>>select * from hive.hive.thivens;*
> *** 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 being filed to allow timestamp/time/interval datatype to go up to 9 digits(nanoseconds) of fractional precision. It should apply to column definitions, CAST clause, CALL procedure columns, and be supported for selects,insert/update statements.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)