You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "xuqianjin (JIRA)" <ji...@apache.org> on 2018/11/30 06:02:00 UTC

[jira] [Commented] (FLINK-11017) Time interval for window aggregations in SQL is wrongly translated if specified with YEAR_MONTH resolution

    [ https://issues.apache.org/jira/browse/FLINK-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704307#comment-16704307 ] 

xuqianjin commented on FLINK-11017:
-----------------------------------

[~dawidwys] I want to try to solve it.

> Time interval for window aggregations in SQL is wrongly translated if specified with YEAR_MONTH resolution
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-11017
>                 URL: https://issues.apache.org/jira/browse/FLINK-11017
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API &amp; SQL
>    Affects Versions: 1.6.2, 1.7.0
>            Reporter: Dawid Wysakowicz
>            Assignee: Dawid Wysakowicz
>            Priority: Major
>             Fix For: 1.6.3, 1.8.0, 1.7.1
>
>
> If a time interval was specified with {{YEAR TO MONTH}} resolution like e.g.:
> {code}
> SELECT * 
> FROM Mytable
> GROUP BY 
>     TUMBLE(rowtime, INTERVAL '1-2' YEAR TO MONTH)
> {code}
> it will be wrongly translated to 14 milliseconds window. We should allow for only DAY TO SECOND resolution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)