[
https://issues.apache.org/jira/browse/FLINK-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-15160:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Clean up is not applied if there are no incoming events for a key.
> ------------------------------------------------------------------
>
> Key: FLINK-15160
> URL: https://issues.apache.org/jira/browse/FLINK-15160
> Project: Flink
> Issue Type: Bug
> Components: Library / CEP
> Affects Versions: 1.8.2, 1.9.1, 1.10.0
> Reporter: Dawid Wysakowicz
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> In CepOperator the pruning of timed out partial matches happens along with
> feeding events into the NFA. Either when unbuffering on Watermark or
> according to the processing time.
> 1. Processing time
> The state is pruned only with the timestamps of incoming events. If there are
> no incoming events no pruning happens
> 2. Event time
> It is slightly more complicated, but the outcome is similar. We register
> timers that pop events from the buffer, but we do not register any timers for
> when the timeout of a partial match could happen. Therefore if there will be
> no more events we will never prune matches.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
