[
https://issues.apache.org/jira/browse/CALCITE-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677078#comment-16677078
]
Julian Hyde commented on CALCITE-2656:
--------------------------------------
It's more like a missing feature. Calcite's enumerable convention represents
TIME and TIMESTAMP values in milliseconds. Thus cannot handle precision greater
than 3. Supporting precision larger than 3 is a major task. The fix in this
case should be that we should throw an error that we cannot implement
TIMESTAMP(6).
Note that since CALCITE-1690 we can represent TIME and TIMESTAMP literals of
arbitrary precision. Just not implement them in enumerable convention.
> Timestamp Micro and Nano Strings literals are getting rounded to milliseconds
> ------------------------------------------------------------------------------
>
> Key: CALCITE-2656
> URL: https://issues.apache.org/jira/browse/CALCITE-2656
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.16.0
> Reporter: Wamsi Viswanath
> Assignee: Julian Hyde
> Priority: Major
>
> explain calcite select m_6 = cast( '1999-07-11 14:02:53.874533' as
> TIMESTAMP(6)) from test;
> Explanation
> LogicalProject(EXPR$0=[=($18, 1999-07-11 14:02:53.875)])
> EnumerableTableScan(table=[[mapd, test]])
>
> Please let me know if this is an expected behavior ? Thank you!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
