[Feature] Implementation of regex Command In PPL

[RyanL1997]

Description

Implementation of regex Command In PPL

Details:

• Core logic of regex

<source> | [commands] | regex <field>=<pattern> | [commands]
<source> | [commands] | regex <field>!=<pattern> | [commands]  

• field: The field name to apply regex matching against
• pattern: Java regex pattern string (supports standard regex metacharacters)
• !=: Negated matching - returns records that do NOT match the pattern
• =: Positive matching - returns records that match the pattern

For the handling of default field (_source / _raw):

• Tracking at issue [FEATURE] Support Default Field in PPL Commands #4111

Related Issues

• Relate [RFC] Add regex Command to PPL (Calcite Engine) #4082

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dai-chen]

Thanks for the changes!

[opensearch-trigger-bot]

The backport to 2.19-dev failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-2.19-dev 2.19-dev
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-2.19-dev
# Create a new branch
git switch --create backport/backport-4083-to-2.19-dev
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9b88f23f343c774a1b8c57f80b6e2943cb602f4f
# Push it to GitHub
git push --set-upstream origin backport/backport-4083-to-2.19-dev
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-2.19-dev

Then, create a pull request where the base branch is 2.19-dev and the compare/head branch is backport/backport-4083-to-2.19-dev.

[RyanL1997]

Will manual backport it.

[opensearch-trigger-bot]

The backport to 2.19-dev failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-2.19-dev 2.19-dev
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-2.19-dev
# Create a new branch
git switch --create backport/backport-4083-to-2.19-dev
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9b88f23f343c774a1b8c57f80b6e2943cb602f4f
# Push it to GitHub
git push --set-upstream origin backport/backport-4083-to-2.19-dev
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-2.19-dev

Then, create a pull request where the base branch is 2.19-dev and the compare/head branch is backport/backport-4083-to-2.19-dev.

[ykmr1224]

Can you do manual backport or see what is conflicting?
It is blocking #4214