Skip to content

[docs-agent] Note editor lacks autocomplete/validation for coordinator-mode lookup joins - #7862

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
docs-agent/7626-coordinator-lookup-join-editor-support-6ec81b284e3a2505
Draft

[docs-agent] Note editor lacks autocomplete/validation for coordinator-mode lookup joins#7862
github-actions[bot] wants to merge 1 commit into
mainfrom
docs-agent/7626-coordinator-lookup-join-editor-support-6ec81b284e3a2505

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds one sentence to the "Cross-cluster and cross-project lookup joins" section of Use ES|QL in the Kibana UI noting that the ES|QL editor accepts the _coordinator: prefix for coordinator-mode lookup joins, but doesn't offer autocomplete suggestions or validation for coordinator-mode lookup indices. Without this note, the surrounding text ("suggests lookup mode indices and join condition fields") could mislead readers into thinking a coordinator-mode query with a nonexistent lookup index is valid or fully assisted by the editor.

The stack applies_to badge on this section was already ga 9.6 in the current source (updated in a same-day, unrelated commit), so no badge change was needed here.

Triage rationale

  • Kibana PR elastic/kibana#280453 (merged) confirms the editor change: it strips/ignores the _coordinator: prefix for index-existence checks and validation, and explicitly skips lookup-index validation for coordinator targets (see validate.ts/sources.ts diffs and the added test skips lookup index existence validation for coordinator targets). No autocomplete entries are added for coordinator-mode targets.
  • The underlying Elasticsearch feature (Coordinator lookup join for remote clusters elasticsearch#153804, "Coordinator lookup join for remote clusters") is merged and labeled v9.6.0, consistent with the issue's reported stack availability (v9.6.0) and the already-present stack: ga 9.6 badge on this page.
  • The other suggested edit target, the LOOKUP JOIN reference page (esql-lookup-join.md), is sourced from the elastic/elasticsearch repository via the (redacted) cross-repo link, not docs-content`. Its "Planned" badge is out of scope for this repository and must be updated at the source.

Drafting sources

Reader test

  • Reader goal: a Kibana user writing ES|QL in the Discover/ES|QL editor understanding coordinator-mode LOOKUP JOIN support and why they might not see autocomplete or validation errors.
  • 2 rounds. Round 1 flagged the wording as ambiguous about whether validation was "reduced" or "absent"; revised to explicitly state "won't see errors even if the index doesn't exist." Round 2 passed with no blocking comprehension gaps.

Closes #7626

This draft PR was produced autonomously by docs-agent-experimental in experimental mode.

Safe-output PRs do not trigger CI by default. A maintainer must trigger the required checks manually.

Generated by 🧪 docs-agent-experimental for #7626 · sonnet50 · 68.6 AIC · ⌖ 4.97 AIC · ⊞ 10.2K ·

  • expires on Aug 21, 2026, 3:55 PM UTC

… joins

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot added automation Created or managed by automation docs-agent Run the experimental docs agent labels Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation Created or managed by automation docs-agent Run the experimental docs agent

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ES|QL editor accepts coordinator-mode lookup joins (_coordinator: prefix)

1 participant