[
https://issues.apache.org/jira/browse/FLINK-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716101#comment-16716101
]
sunjincheng commented on FLINK-10543:
-------------------------------------
Hi [~fhueske] from the point of compatibility I agree this change should not cp
to release-1.7. I'll revert the change from release-1.7.
Thank you for reminding we only back port bug fixes to release branches that do
not break compatibility.
I think the improvement is necessary on the master to reduce the storage and
access pressure on useless states.
If you find there are any incorrect semantics changes, we can file new JIRA. to
fix.
Thanks, Jincheng
> 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)
