[
https://issues.apache.org/jira/browse/FLINK-11188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727068#comment-16727068
]
Fabian Hueske commented on FLINK-11188:
---------------------------------------
Thanks for creating the issue [~hequn8128]. As I commented on FLINK-11172, I
think we should not discard state of operators that are explicitly defined on a
time range because
1. they automatically clean up their state
2. removing state, will result in incomplete / invalid results
However, OVER ROWS windows are a bit different because they are defined on a
row count. An OVER ROWS window on an inactive key will preserve its state
forever and wait for more records. For these windows, state cleanup should be
supported, IMO.
> 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)
