Skip to content

[9.0] [DOCS] Clarify Update API does not replace fields with sparse_vector field (#135788) #135828

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 2, 2025
Merged

[9.0] [DOCS] Clarify Update API does not replace fields with sparse_vector field (#135788) #135828

merged 1 commit into from
Oct 2, 2025

Conversation

leemthompo
Copy link
Contributor

Backports the following commits to 9.0:

@leemthompo
[DOCS] Clarify Update API does not replace fields with sparse_vector …
77e2c0f 
…field (elastic#135788)

* [DOCS] Clarify Update API does not replace fields with sparse_vector field

Updated the documentation for `sparse_vector` fields to clarify merging behavior, replacement methods, and limitations.

🚗 Compiled all the admonitions into a limitations section

* Fix links

* Fix rank link to rank_features

* idem

* Fix formatting and wording

* Add applies_to and products metadata
@leemthompo leemthompo added :Search Relevance/Search Catch all for Search Relevance >docs General docs changes auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Docs Meta label for docs team Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels Oct 2, 2025
@elasticsearchmachine elasticsearchmachine mentioned this pull request Oct 2, 2025
Merged
@elasticsearchmachine elasticsearchmachine merged commit 2cb3259 into elastic:9.0 Oct 2, 2025
6 checks passed
@leemthompo leemthompo deleted the backport/9.0/pr-135788 branch October 2, 2025 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >docs General docs changes :Search Relevance/Search Catch all for Search Relevance Team:Docs Meta label for docs team Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@leemthompo @elasticsearchmachine