[
https://issues.apache.org/jira/browse/CALCITE-7410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059424#comment-18059424
]
Mihai Budiu commented on CALCITE-7410:
--------------------------------------
This reverts CALCITE-4282
I think that this is a better solution: if the precision of the columns
window_start and window_end is actually unspecified, it is "inherited" from the
precision of the descriptor column. E.g., if the descriptor column has a
precision of 6, window_start will have a precision of 6; if the descriptor
column has a precision of 0, window_start will also have a precision of 0.
> 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)
