Summary
The ES|QL editor now parses tuple expressions such as `(first_name, last_name) IN (FROM employees | KEEP first_name, last_name)`. It validates that the subquery column count and types match the left-hand tuple. Comma autocomplete inside tuples stays behind an internal flag until Elasticsearch marks the feature generally available. Published IN subquery docs still say the subquery must return exactly one column.
Why this needs docs: Editor support for multi-column IN is in 9.6, but published language docs still require a single column. Confirm Elasticsearch availability before changing that limitation.
Resources
Screenshots from PR
Availability
| Channel |
Details |
| Stack |
v9.6.0 |
| Serverless |
Aug 31–Sep 4 |
| Feature flag |
None — active by default |
Created with Docs Quest Scanner by @florent-leborgne
Suggested edits
Use ES|QL subqueries with IN and NOT IN > The subquery must return exactly one column
- What the docs say: The subquery must produce a single column to compare against the left-hand side expression. A subquery that returns zero or more than one column is rejected.
- What to add: If multi-column IN shipped for 9.6, replace the one-column rule with tuple syntax. Document that the subquery must return the same number of columns as the left-hand tuple and that types must match by position. Applies from 9.6.0 and in serverless.
Summary
The ES|QL editor now parses tuple expressions such as `(first_name, last_name) IN (FROM employees | KEEP first_name, last_name)`. It validates that the subquery column count and types match the left-hand tuple. Comma autocomplete inside tuples stays behind an internal flag until Elasticsearch marks the feature generally available. Published IN subquery docs still say the subquery must return exactly one column.
Why this needs docs: Editor support for multi-column IN is in 9.6, but published language docs still require a single column. Confirm Elasticsearch availability before changing that limitation.
Resources
Screenshots from PR
Availability
Created with Docs Quest Scanner by @florent-leborgne
Suggested edits
Use ES|QL subqueries with IN and NOT IN > The subquery must return exactly one column