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

["Timo Walther (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther closed FLINK-11017.
--------------------------------
    Resolution: Fixed

Fixed in master: 3720bfbc7af992b41563b16793815282103945f2
Fixed in 1.7.1: a583b4a71a10322809400a87840e412c1c0c20d6
Fixed in 1.6.3: 4d3574e5789144fe3dcbcb0e0bc7038b7f4e9dc4

> 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 & SQL
>    Affects Versions: 1.6.2, 1.7.0
>            Reporter: Dawid Wysakowicz
>            Assignee: Dawid Wysakowicz
>            Priority: Major
>              Labels: pull-request-available
>             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)