[
https://issues.apache.org/jira/browse/FLINK-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764783#comment-16764783
]
Tzu-Li (Gordon) Tai commented on FLINK-10996:
---------------------------------------------
[~aitozi] I'm changing this ticket's "Fix Version" since we're about to release
1.7.2 now, and this doesn't seem like a blocking issue.
I wonder if this counts as a new feature and shouldn't be included in a bugfix
release anyways. Therefore, I added 1.8.0 as the new fix version.
Please let me know if you disagree.
> Enable state ttl in cep
> -----------------------
>
> Key: FLINK-10996
> URL: https://issues.apache.org/jira/browse/FLINK-10996
> Project: Flink
> Issue Type: Improvement
> Components: CEP
> Affects Versions: 1.7.1
> Reporter: aitozi
> Assignee: aitozi
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In flink cep, although the within clause can clean up the data when data is
> expire. But If the specific key data never come again, the partial matched
> data will not be deleted again which will lead to the state leak. With the
> state ttl feature support by flink runtime, we has the ability to expire the
> correlative data asyncly .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
