[DOCS] Clarify Update API does not replace fields with sparse_vector field #135788
Conversation
This file contains hidden or 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
…field Updated the documentation for `sparse_vector` fields to clarify merging behavior, replacement methods, and limitations. 🚗 Compiled all the admonitions into a limitations section
🔍 Preview links for changed docs |
ℹ️ Important: Docs version tagging👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version. We use applies_to tags to mark version-specific features and changes. Expand for a quick overviewWhen to use applies_to tags:✅ At the page level to indicate which products/deployments the content applies to (mandatory) What NOT to do:❌ Don't remove or replace information that applies to an older version 🤔 Need help?
|
leemthompo
added
>docs
elasticsearchmachine
added
Team:Docs
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
|
Pinging @elastic/core-docs (Team:Docs) |
leemthompo
added
auto-backport
leemthompo
added a commit
to leemthompo/elasticsearch
that referenced
this pull request
Oct 2, 2025
…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
added a commit
to leemthompo/elasticsearch
that referenced
this pull request
Oct 2, 2025
…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
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 2, 2025
…field (#135788) (#135829) * [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
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 2, 2025
…field (#135788) (#135828) * [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
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.
Closes #135626
Updated the documentation for
sparse_vectorfields to clarify merging behavior, replacement methods, and limitations.🚗 Compiled all the admonitions into a limitations section