[jira] [Created] (FLINK-30069) Expected prune behavior for matches with same priority

["Juntao Hu (Jira)" <ji...@apache.org>]

Juntao Hu created FLINK-30069:
---------------------------------

             Summary: 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
            Reporter: Juntao Hu


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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)