fix constant_keyword field type

[kkewwei]

Description

Fix constant_keyword field type not working

Related Issues

Resolves #14638

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

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.

[github-actions]

❌ Gradle check result for c2a96fb: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 7715ac8: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 78e95da:

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.82%. Comparing base (1299919) to head (7ae9a4e).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main   #14807   +/-   ##
=========================================
  Coverage     71.81%   71.82%           
- Complexity    62432    62472   +40     
=========================================
  Files          5145     5145           
  Lines        293307   293310    +3     
  Branches      42407    42407           
=========================================
+ Hits         210644   210662   +18     
+ Misses        65346    65335   -11     
+ Partials      17317    17313    -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[opensearch-trigger-bot]

The backport to 2.x 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/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-14807-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 cb743710b2ee5c8ed7de7123891463fc3a7a7fde
# Push it to GitHub
git push --set-upstream origin backport/backport-14807-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-14807-to-2.x.

[dblock]

@kkewwei Can you please backport this manually?

[gaobinlong]

@dblock do you think we should also backport this PR to 2.14 and 2.15 branch?

[dblock]

@dblock do you think we should also backport this PR to 2.14 and 2.15 branch?

We only do security releases from those, so I would say no unless you need it (some people do use those branches as upstream).

[kkewwei]

@kkewwei Can you please backport this manually?

of course.

[opensearch-trigger-bot]

The backport to 2.16 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/OpenSearch/backport-2.16 2.16
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.16
# Create a new branch
git switch --create backport/backport-14807-to-2.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 cb743710b2ee5c8ed7de7123891463fc3a7a7fde
# Push it to GitHub
git push --set-upstream origin backport/backport-14807-to-2.16
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.16

Then, create a pull request where the base branch is 2.16 and the compare/head branch is backport/backport-14807-to-2.16.