You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/12/10 20:00:13 UTC
[jira] [Commented] (PHOENIX-2511) Allow precision to be specified
for TIMESTAMP
[ https://issues.apache.org/jira/browse/PHOENIX-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051465#comment-15051465 ]
James Taylor commented on PHOENIX-2511:
---------------------------------------
[~maryannxue] - would you be able to take this one? I think it'll help make Phoenix cooperate better with Calcite for date/time types.
> Allow precision to be specified for TIMESTAMP
> ---------------------------------------------
>
> Key: PHOENIX-2511
> URL: https://issues.apache.org/jira/browse/PHOENIX-2511
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
>
> We should allow a precision to be specified for our TIMESTAMP type declaration. For legacy usage of TIMESTAMP, we can either upgrade existing types to a precision of 9 or use that as the default value. Going forward, we should have a default value of 3 (for millisecond resolution) which is more standard.
> For query compilation, we can likely use the Date/Time expression instead of the Timestamp ones (i.e. use DateAddExpression instead of TimestampAddExpression), but we'd need to take care on the return type. Might need to have an intermediate class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)