[
https://issues.apache.org/jira/browse/FLINK-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716116#comment-16716116
]
Hequn Cheng commented on FLINK-10543:
-------------------------------------
[~fhueske] Hi, would be nice if you can take a look at the PR.
The pr mainly include the following changes:
* Delete expired timers in {{ProcessFunctionWithCleanupState}}.
* Add {{CoProcessFunctionWithCleanupState}} for join. This can align the
cleanup logic in join with other operators.
* Use one {{ValueState}} to control clean up instead of two, i.e, take left
and right state of join as a whole.
* Leverage min and max retention time to clean up the state in join while
before, join regist clean up timer and clean up the state in a fixed interval.
In the new version, we can remove all records once in all as new records will
refresh the timer.
Best, Hequn
> Leverage efficient timer deletion in relational operators
> ---------------------------------------------------------
>
> Key: FLINK-10543
> URL: https://issues.apache.org/jira/browse/FLINK-10543
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Fabian Hueske
> Assignee: Hequn Cheng
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.8.0, 1.7.1
>
>
> FLINK-9423 added support for efficient timer deletions. This feature is
> available since Flink 1.6 and should be used by the relational operator of
> SQL and Table API.
> Currently, we use a few workarounds to handle situations when deleting timers
> would be the better solution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
