feat: constant keyword field #12285
Merged
feat: constant keyword field #12285
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hasnain2808
requested review from
abbashus,
adnapibar,
anasalkouz,
andrross,
Bukhtawar,
CEHENKLE,
dblock,
dbwiddis,
dreamer-89,
gbbafna,
kartg,
kotwanikunal,
mch2,
msfroh,
nknize,
owaiskazi19,
reta,
Rishikesh1159,
ryanbogan,
sachinpkale,
saratvemulapalli,
shwetathareja,
sohami,
tlfeng and
VachaShah
as code owners
github-actions
bot
added
discuss
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
Signed-off-by: Mohammad Hasnain <[email protected]>
msfroh
force-pushed
the
feature-constant-keyword
branch
from
6cdd963 to
917b2bb
Compare
|
❌ Gradle check result for 917b2bb: null 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? |
|
The backport to 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-12285-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1ec49bd3aee6cd4463ae91ffb6c09054d1bbc02b
# Push it to GitHub
git push --set-upstream origin backport/backport-12285-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.xThen, create a pull request where the |
msfroh
pushed a commit
to msfroh/OpenSearch
that referenced
this pull request
Apr 1, 2024
Constant keyword fields behave similarly to regular keyword fields, except that they are defined only in the index mapping, and all documents in the index appear to have the same value for the constant keyword field. --------- Signed-off-by: Mohammad Hasnain <[email protected]> (cherry picked from commit 1ec49bd)
8 tasks
dblock
pushed a commit
that referenced
this pull request
Apr 22, 2024
Constant keyword fields behave similarly to regular keyword fields, except that they are defined only in the index mapping, and all documents in the index appear to have the same value for the constant keyword field. --------- Signed-off-by: Mohammad Hasnain <[email protected]> (cherry picked from commit 1ec49bd) Signed-off-by: Michael Froh <[email protected]> Co-authored-by: Mohammad Hasnain Mohsin Rajan <[email protected]>
shiv0408
pushed a commit
to Gaurav614/OpenSearch
that referenced
this pull request
Apr 25, 2024
Constant keyword fields behave similarly to regular keyword fields, except that they are defined only in the index mapping, and all documents in the index appear to have the same value for the constant keyword field. --------- Signed-off-by: Mohammad Hasnain <[email protected]> Signed-off-by: Shivansh Arora <[email protected]>
harshavamsi
pushed a commit
to harshavamsi/OpenSearch
that referenced
this pull request
Apr 29, 2024
Constant keyword fields behave similarly to regular keyword fields, except that they are defined only in the index mapping, and all documents in the index appear to have the same value for the constant keyword field. --------- Signed-off-by: Mohammad Hasnain <[email protected]>
4 tasks
Merged
1 task
|
If I read #14807 this feature was broken when introduced. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds a Constant Keyword Field
Related Issues
Resolves #9981
Check List
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.