docs(semantic_text): add index version limitation

[mromaios]

Doc update for: #133080

[elasticsearchmachine]

Pinging @elastic/search-relevance (Team:Search - Relevance)

[elasticsearchmachine]

Pinging @elastic/core-docs (Team:Docs)

[github-actions]

🔍 Preview links for changed docs

• docs/reference/elasticsearch/mapping-reference/semantic-text.md

[kderusso]

Can we change this to use an applies to tag, somewhere at the top of the document?

[mromaios]

Can we change this to use an applies to tag, somewhere at the top of the document?

@kderusso what structure do you have in mind?

This is related to the index version, so it wasn't clear to me how to apply applies_to effectively. semantic_text is available from 8.15.0

[kderusso]

This is related to the index version, so it wasn't clear to me how to apply applies_to effectively. semantic_text is available from 8.15.0

Good point - @leemthompo any ideas here? Or is this sufficient?

[leemthompo]

This should fine because these are the 9.x docs, so we don't really use applies_to for pre-9.x stuff in any case :)

[leemthompo]

That said, more importantly @mromaios @kderusso this info also needs to be in the 8.x docs, which requires opening a separate PR against the 8.19 version of this page and backporting

[mromaios]

Thanks for reviewing @leemthompo!

That said, more importantly @mromaios @kderusso this info also needs to be in the 8.x docs, which requires opening a separate PR against the 8.19 version of this page and backporting

One is already up: #133374

[leemthompo]

👍

[kderusso]

If it's good with @leemthompo it's good with me 😉

[mromaios]

Oops these were left behind, apologies 🙇 (+#133374)
@kderusso , @Mikep86 we still want these in right, the implementation changed but the limitations stands
Defer Semantic Text Failures on Pre-8.11 Indices

[Mikep86]

@mromaios Yes, i think we still want this. Thanks for catching it!

[kderusso]

Yep, still correct, just because you can create the field doesn't mean it will work

[github-actions]

ℹ️ 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 overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel