[FLINK-24865][CEP] Support MATCH_RECOGNIZE in Batch mode

[SteNicholas]

What is the purpose of the change

MATCH_RECOGNIZE only works currently in Streaming mode. It should also be supported in Batch mode.

Brief change log

• FlinkBatchRuleSets adds the BatchPhysicalMatchRule for the batch rule of the MATCH_RECOGNIZE.
• Introduces the BatchExecMatch to add the batch ExecNode which matches along with MATCH_RECOGNIZE.

Verifying this change

• BatchOperatorNameTest adds the testMatch test case for the batch operator of the MATCH_RECOGNIZE.
• Adds the MatchRecognizeTest and MatchRecognizeValidationTest for the batch mode of the MATCH_RECOGNIZE.

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, Kubernetes/Yarn, 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)

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit 98deafa (Thu Jan 20 05:24:01 UTC 2022)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[flinkbot]

CI report:

• c6b38c5 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[MartijnVisser]

@SteNicholas I have to check, let me get back to you asap

[twalthr]

Thanks for working on this @SteNicholas. I will review it today or Monday latest.

[SteNicholas]

@twalthr @MartijnVisser, could anyone help to review this pull request?

[twalthr]

@SteNicholas sorry for the delay. The SQL upgrade story still keeps us busy. I guess we have to postpone this to Flink 1.16.

[godfreyhe]

Thanks for the contribution @SteNicholas, I left some comments and integration testing is missed

[SteNicholas]

@godfreyhe, I have addressed the above comments and updated this pull request. PTAL.

[godfreyhe]

Thanks for the update, I left some comments

[SteNicholas]

@godfreyhe, thanks for your review. I have addressed above comments. PTAL.

[godfreyhe]

Thanks for the update, LGTM

[SteNicholas]

@flinkbot run azure