-
Notifications
You must be signed in to change notification settings - Fork 115
Allow multi-fields in semantic_text property #5375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Following you can find the validation changes against the target branch for the API.
You can validate this API yourself by using the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM based on elastic/elasticsearch#120128 and how other fields implement this support
@kderusso Thank you for the review! And thank you, as I wasn't able to figure out which PR added that. |
(cherry picked from commit e5a0cb8)
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.1 9.1
# Navigate to the new working tree
cd .worktrees/backport-9.1
# Create a new branch
git switch --create backport-5375-to-9.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e5a0cb8fad70ebd7eaab102ff077c5af526ea2b2
# Push it to GitHub
git push --set-upstream origin backport-5375-to-9.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.1 Then, create a pull request where the |
(cherry picked from commit e5a0cb8) # Conflicts: # output/schema/schema.json
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
Added in elastic/elasticsearch#120128