Skip to content

Conversation

@luigidellaquila
Copy link
Contributor

JOIN command is in the grammar, but we have no implementation for it.

Since it's part of EQL spec, it makes sense to parse it correctly, but we'll make it return a validation exception with a meaningful error message.

Fixes: #122000

@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine elasticsearchmachine added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v9.1.0 labels Feb 7, 2025
@elasticsearchmachine
Copy link
Collaborator

Hi @luigidellaquila, I've created a changelog YAML for you.

Copy link
Contributor

@astefan astefan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@luigidellaquila luigidellaquila merged commit 32dd91d into elastic:main Feb 10, 2025
17 checks passed
@luigidellaquila
Copy link
Contributor Author

Thanks @astefan!

@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
9.0
8.18
8.x
8.16
8.17

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

Labels

:Analytics/EQL EQL querying auto-backport Automatically create backport pull requests when merged >bug Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.16.5 v8.17.3 v8.18.1 v8.19.0 v9.0.0 v9.0.1 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

EQL: better validation for (unsupported) JOIN command

3 participants