You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Website]: TS command is incompatible with data views #8568
The issue asks to clarify on the ES|QL TS command page that ES|QL views cannot be used as the TS source. The published page currently documents the syntax as TS index_pattern [METADATA fields] and describes index_pattern as indices, data streams, or aliases, but does not state the view restriction. The linked Elasticsearch change adds an explicit verification error for views used with TS.
Request accuracy
Accurate — the linked commit e89d1b0 adds the error “Views are not supported in TS command” after view resolution.
Update the TS command reference to state that ES|QL views cannot be used as the TS source, even though views are accepted as source names by FROM.
Include the user-facing verification error or an equivalent explanation so users know why a TS query against a view fails.
Scope the statement to the release where the behavior applies, and verify the wording against the supported-version matrix before merging.
Check the TS examples and the adjacent FROM/views references for consistency; add a cross-link only if it materially helps users choose between FROM and TS.
Scope boundary
No change appears necessary to the general FROM command or ES|QL views page unless maintainers want a broader cross-reference about which source commands support views.
Questions to go deeper
Should the restriction be documented as applying from 9.4.5 onward, or should the page scope it to the exact Elasticsearch release where the fix shipped?
Should the docs use “ES|QL views” consistently, or is “data views” a product term that needs a separate clarification?
Is the exact verification error stable enough to quote, or should the page describe the behavior without reproducing the message?
Does the team want a cross-reference from the ES|QL views page, or is the TS reference the sole intended target?
Should the docs use “ES|QL views” consistently, or is “data views” a product term that needs a separate clarification?
@frconil I'm pretty sure when we talk about views in ESQL (at least in the Elasticsearch docs) we're talking about logical views and data views is different Kibana beast entirely AFAIK
Activity
github-actions commentedon Sep 28, 2026
Elastic Docs AI Menu
Check one box to run an AI workflow for this issue.
docs-scope). Status: completed. View progress.Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.
github-actions commentedon Sep 29, 2026
✅ ScopeBot finished. https://github.com/elastic/docs-content/actions/runs/36569724782
github-actions commentedon Sep 29, 2026
🟢 ScopeBot Results: Full assessment
Summary
The issue asks to clarify on the ES|QL TS command page that ES|QL views cannot be used as the TS source. The published page currently documents the syntax as
TS index_pattern [METADATA fields]and describesindex_patternas indices, data streams, or aliases, but does not state the view restriction. The linked Elasticsearch change adds an explicit verification error for views used with TS.Request accuracy
Accurate — the linked commit e89d1b0 adds the error “Views are not supported in TS command” after view resolution.
Recommended docs targets
How to tackle this
Scope boundary
No change appears necessary to the general FROM command or ES|QL views page unless maintainers want a broader cross-reference about which source commands support views.
Questions to go deeper
leemthompo commentedon Oct 26, 2026
@kkrik-es @felixbarny any thoughts on this one?
leemthompo commentedon Oct 26, 2026
@frconil I'm pretty sure when we talk about views in ESQL (at least in the Elasticsearch docs) we're talking about logical views and data views is different Kibana beast entirely AFAIK