Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[ES|QL] report nested fields as unsupported #116413

Open
drewdaemon opened this issue Nov 7, 2024 · 1 comment
Open

[ES|QL] report nested fields as unsupported #116413

drewdaemon opened this issue Nov 7, 2024 · 1 comment
Labels
:Analytics/ES|QL AKA ESQL >enhancement Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo)

Comments

@drewdaemon
Copy link
Contributor

Description

Right now most fields that aren't supported in ES|QL are reported (in the table) and the messaging (error messages) indicates that they exist but are not supported.

However nested fields are treated as if they don't exist at all. The ask is to align the behavior so that all unsupported fields are treated the same.
@drewdaemon drewdaemon added :Analytics/ES|QL AKA ESQL >enhancement needs:triage Requires assignment of a team area label Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) labels Nov 7, 2024
@drewdaemon drewdaemon mentioned this issue Nov 7, 2024
Closed
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Analytics/ES|QL AKA ESQL >enhancement Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@drewdaemon @elasticsearchmachine