[jira] [Comment Edited] (FLINK-11188) Bounded over should not enable state retention time

["Hequn Cheng (JIRA)" <ji...@apache.org>]

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

Hequn Cheng edited comment on FLINK-11188 at 12/22/18 1:41 PM:
---------------------------------------------------------------

[~fhueske] Thanks for your suggestions. 
I will close this one and create a new one(FLINK-11210) to address the problem for OVER RANGE. 
OVER ROWS has already cleaned up its state based on the retention configuration, so we don't need a jira for it.

Best, Hequn


was (Author: hequn8128):
[~fhueske] Thanks for your suggestions. 
I will close this one and create a new one to address the problem for OVER RANGE. 
OVER ROWS has already cleaned up its state based on the retention configuration, so we don't need a jira for it.

Best, Hequn

> Bounded over should not enable state retention time 
> ----------------------------------------------------
>
>                 Key: FLINK-11188
>                 URL: https://issues.apache.org/jira/browse/FLINK-11188
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>            Reporter: Hequn Cheng
>            Assignee: Hequn Cheng
>            Priority: Major
>
> As discussed in FLINK-11172, time-based operations (GROUP BY windows, OVER windows, time-windowed join, etc.) are inherently bound by time and automatically clean up their state. We should not add state cleanup or TTL for these operators.
> If I understand correctly, we should not add the retention logic for rows-bounded operations either. I think we should disable state retention logic for:
>  - ProcTimeBoundedRangeOver
>  - ProcTimeBoundedRowsOver
>  - RowTimeBoundedRangeOver
>  - RowTimeBoundedRowsOver
> Any suggestions are appreciated!



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