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

Robert Metzger commented on FLINK-19926:
----------------------------------------

Note, this has also been posted on the user@ list: 
https://lists.apache.org/thread.html/r24f918feccc6c296cb1e0f6a78e1a747cfd958862333349c8659f540%40%3Cuser.flink.apache.org%3E

> Wrong results for join post tumble grouping
> -------------------------------------------
>
>                 Key: FLINK-19926
>                 URL: https://issues.apache.org/jira/browse/FLINK-19926
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Runtime
>    Affects Versions: 1.11.1
>         Environment: Flink version: 1.11.1
>            Reporter: Satyam Shekhar
>            Priority: Major
>
> I have a table T0 with the following schema -
> {{root}}
> {{      |-- amount: BIGINT}}
> {{      |-- timestamp: TIMESTAMP(3)}}
> The table T0 has two rows -
> |amount|timestamp|
> |0|0|
> |1|86400000|
> The following query with tumble grouping returns the wrong result -
> {{WITH CTE AS }}
> {{    (SELECT SUM(amount) AS _output, }}
> {{    TUMBLE_END(`timestamp`, INTERVAL '1' SECOND) AS _dim0}}
> {{  FROM T0 GROUP BY TUMBLE(`timestamp`, INTERVAL '1' SECOND))}}
> {{SELECT V0._output as V0_output, V1._output AS V1_output, }}
> {{    V0._dim0 as V0_time, V1._dim0 as V1_time}}
> {{  FROM CTE as V0 INNER JOIN CTE V1 ON V0._dim0 = V1._dim0}}
>  
> The returned result is -
> |V0_output|V1_output|V0_time|V1_time|
> |1|1|86401000|86401000|
> The expected result is -
> |V0_output|V1_output|V0_time|V1_time|
> |0|0|1000|1000|
> |1|1|86401000|86401000|
> Running subquery for `CTE` returns the correct result -
> {{SELECT SUM(amount) AS _output,}}
> {{        TUMBLE_END(`timestamp`, INTERVAL '1' SECOND) AS _dim0}}
> {{   FROM T0 GROUP BY TUMBLE(`timestamp`, INTERVAL '1' SECOND)}}
> Result (this is correct) -
> |_output|_dim0|
> |0|1000|
> |1|86401000|
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to