[
https://issues.apache.org/jira/browse/FLINK-11188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323413#comment-17323413
]
Flink Jira Bot commented on FLINK-11188:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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 SQL / API
> Reporter: Hequn Cheng
> Assignee: Hequn Cheng
> Priority: Major
> Labels: stale-assigned
>
> 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
(v8.3.4#803005)
