[
https://issues.apache.org/jira/browse/CALCITE-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204464#comment-17204464
]
Julian Hyde commented on CALCITE-4282:
--------------------------------------
[~jark], Yes, that sounds more natural to me. I don't think it's appropriate
that particular functions should set the precision (especially when different
from the system's default precision for TIMESTAMP) but inheriting from the
input argument sounds elegant.
> Promote the window table functions window attribute data type with precision 3
> ------------------------------------------------------------------------------
>
> Key: CALCITE-4282
> URL: https://issues.apache.org/jira/browse/CALCITE-4282
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.25.0
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.26.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Now the {{window_start}} and {{window_end}} has a type of a Timestamp with
> default system precision. But, actually, many DB vendors has default
> precision as 6 (which is also defined in the SQL standard).
> We better promote the precision to 3 because:
> 1. For windowing, time unit as millisecond is enough
> 2. Make the precision deterministic instead of overriding by each engine's
> default one
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
