[
https://issues.apache.org/jira/browse/FLINK-11188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu closed FLINK-11188.
---------------------------
Resolution: Fixed
Blink planner already follows Fabian's conclusion:
- OVER RANGE should automatically clean up its state.
- OVER ROWS should clean up based on the idle state retention configuration.
I will close this issue.
> 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
> Priority: Major
> Labels: auto-unassigned
>
> 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)
