[
https://issues.apache.org/jira/browse/FLINK-31017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687118#comment-17687118
]
Martijn Visser commented on FLINK-31017:
----------------------------------------
[~Juntao Hu] Are you committing to fixing this in 1.18? Else I'll remove the
fixVersion for now, because that should only be set if indeed it's expected
that it will make that version
> Early-started partial match timeout not yield completed matches
> ---------------------------------------------------------------
>
> Key: FLINK-31017
> URL: https://issues.apache.org/jira/browse/FLINK-31017
> Project: Flink
> Issue Type: Bug
> Components: Library / CEP
> Affects Versions: 1.17.0, 1.15.3, 1.16.1
> Reporter: Juntao Hu
> Priority: Major
> Fix For: 1.18.0
>
>
> Pattern example:
> {code:java}
> Pattern.begin("A").where(startsWith("a")).oneOrMore().consecutive().greedy()
> .followedBy("B")
> .where(count("A") > 2 ? startsWith("b") : startsWith("c"))
> .within(Time.seconds(3));{code}
> Sequence example, currently without any output:
> a1 a2 a3 a4 c1
> When match[a3, a4, c1] completes, partial match[a1, a2, a3, a4] is earlier,
> so NFA#processMatchesAccordingToSkipStrategy() won't give any result, which
> is the expected behavior. However, when partial match[a1, a2, a3, a4] is
> timed-out, completed match[a3, a4, c1] should be "freed" from NFAState to
> output.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
