[
https://issues.apache.org/jira/browse/CALCITE-7410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059483#comment-18059483
]
Mihai Budiu commented on CALCITE-7410:
--------------------------------------
I will actually implement the suggestion from [~julianhyde] in a comment of
CALCITE-4282: instead of hardwiring the precision of the timestamp, it is the
same as the precision of the input timestamp column.
> TIMESTAMP type for TUMBLE and HOP is hardwired to TIMESTAMP(3)
> --------------------------------------------------------------
>
> Key: CALCITE-7410
> URL: https://issues.apache.org/jira/browse/CALCITE-7410
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.41.0
> Reporter: Mihai Budiu
> Assignee: Mihai Budiu
> Priority: Minor
> Labels: pull-request-available
>
> This precludes implementations computing on higher precision timestamps.
> This is hardwired in SqlWindowTableFunction.inferRowType.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
