[
https://issues.apache.org/jira/browse/FLINK-30069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juntao Hu updated FLINK-30069:
------------------------------
Affects Version/s: 1.16.1
1.15.3
> Expected prune behavior for matches with same priority
> ------------------------------------------------------
>
> Key: FLINK-30069
> URL: https://issues.apache.org/jira/browse/FLINK-30069
> Project: Flink
> Issue Type: Bug
> Components: Library / CEP
> Affects Versions: 1.15.3, 1.16.1
> Reporter: Juntao Hu
> Priority: Major
>
> When a pattern produces several matches with same priority, is it the
> expected behavior to keep only the first dequeued one?
> E.G.
> pattern: A.followedByAny(B).followedBy(C)
> seq: a1, b1, b2, b3, c1
> aftermatch strategy: skip_to_next
> Potential matches (a1, b1, c1) (a1, b2, c1) (a1, b3, c1) reach final state at
> the same time and have the same priority, but (a1, b1, c1) is the first one
> in the queue, thus (a1, b2, c1) and (a1, b3, c1) will be dropped by
> skip_to_next strategy.
> If it's by-design, I guess it relies on two things:
> * take must be the first transition for every state, if exists
> * priority queue is first-in-first-out for items with same priority
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
