Skip to content

[Website]: TS command is incompatible with data views #8568

Open

Description

@frconil

Before you submit

  • This issue is about a documentation page, flow, or piece of content.

Type of issue

Missing information

What documentation page or section is affected

https://www.elastic.co/docs/reference/query-languages/esql/commands/ts

What happened?

As of 9.4.5 (see PR elastic/elasticsearch#153366 ), the TS command does not accept data views any more. This used to work until then.

While the documentation states TS index_pattern [METADATA fields], we could potentially make the data views situation clearer.

Additional info

No response

Activity

  1. added
    source:webIssues originating from the elastic.co docs
    on Sep 28, 2026
  2. github-actions commented on Sep 28, 2026

    @github-actions
    Contributor

    Elastic Docs AI Menu

    Check one box to run an AI workflow for this issue.

    Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

  3. added
    Team:DeveloperIssues owned by the Developer Docs Team
    triagedTriage has been run on this issue
    and removed
    needs-teamIssues pending triage by the Docs Team
    on Sep 28, 2026
  4. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor
  5. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    🟢 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 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.

    Recommended docs targets

    Page URL Action Confidence Why this page?
    ES QL TS command https://www.elastic.co/docs/reference/query-languages/esql/commands/ts Update existing page High

    How to tackle this

    1. 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.
    2. Include the user-facing verification error or an equivalent explanation so users know why a TS query against a view fails.
    3. Scope the statement to the release where the behavior applies, and verify the wording against the supported-version matrix before merging.
    4. 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?

    Generated from Gh Aw Issue Scope · ◷

  6. leemthompo commented on Oct 26, 2026

    @leemthompo
    Member

    @kkrik-es @felixbarny any thoughts on this one?

  7. leemthompo commented on Oct 26, 2026

    @leemthompo
    Member

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Confidence: 0.8Mostly clear; minor unknownsEffort: 0.1~1-2 hours (0.1 week)Impact: 3Meaningful improvement or harmReach: 2Small but real audienceTeam:DeveloperIssues owned by the Developer Docs Teamsource:webIssues originating from the elastic.co docstriagedTriage has been run on this issue

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions