## What is the purpose of the change Add option to throw exception when found match does not have any events mapped to variable that is used in SKIP_TO_FIRST/LAST. This is to conform with SQL standard for MATCH_RECOGNIZE.
## Brief change log * throwing exception when there is no events mapped to variable used in SKIP_TO_FIRST/LAST * added option to enable/disable this feature ## Verifying this change This change added tests and can be verified as follows: * `org.apache.flink.cep.nfa.AfterMatchSkipITCase#testSkipToFirstNonExistentPosition` * `org.apache.flink.cep.nfa.AfterMatchSkipITCase#testSkipToFirstNonExistentPositionWithoutException` * `org.apache.flink.cep.nfa.AfterMatchSkipITCase#testSkipToLastNonExistentPosition` * `org.apache.flink.cep.nfa.AfterMatchSkipITCase#testSkipToLastNonExistentPositionWithoutException` ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (**yes** / no) - If yes, how is the feature documented? (not applicable / **docs** / **JavaDocs** / not documented) [ Full content available at: https://github.com/apache/flink/pull/6758 ] This message was relayed via gitbox.apache.org for [email protected]
