docs: fix coordinator-mode lookup join lifecycle tag (#7626) - #7868
Draft
florent-leborgne wants to merge 2 commits into
Draft
docs: fix coordinator-mode lookup join lifecycle tag (#7626)#7868florent-leborgne wants to merge 2 commits into
florent-leborgne wants to merge 2 commits into
Conversation
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Repeating the applies_to tag mid-paragraph before a second sentence is the floating-between-sentences case the tagging rules forbid. Merge back into one sentence, and drop the autocomplete/validation caveat since it doesn't clear the gap bar on its own.
florent-leborgne
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR addresses #7626 with the following change:
explore-analyze/query-filter/languages/esql-kibana.md: fixed theapplies_tolifecycle tag on the coordinator-mode lookup join mention (stack: ga 9.6→stack: preview 9.6+/serverless: preview) so it matches the actual lifecycle state on the Elasticsearch reference page (esql-lookup-join.md), the source of truth for this Elasticsearch-side feature. The two pages previously disagreed: one said GA, the other said preview, for the same capability at the same version.Note on scope
The issue's original suggested edit asked to "update the Planned badge to the shipping version" once the Elasticsearch-side feature ships. That edit wasn't needed: both the reference page and this page already tag the coordinator-mode content with a future version (
9.6+), and docs-builder automatically flips the "Planned" badge to the live lifecycle badge once that version ships. No source edit is required for that flip.An earlier draft of this PR also added a sentence noting that the Kibana ES|QL editor accepts the
_coordinator:prefix without autocomplete or validation (confirmed against kibana#280453). On review, that caveat didn't clear the bar for a real documentation gap — the general claim it was meant to guard against sits several paragraphs above in an unrelated intro, and a reader following this specific coordinator-mode instruction isn't likely to still be holding it. Dropped to keep the change to the one clearly necessary fix.Resolves
Closes #7626