Skip to content

ES|QL: Add note in Known Issues for #130644 #130996

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

Merged
merged 8 commits into from
Jul 11, 2025
Merged

ES|QL: Add note in Known Issues for #130644 #130996

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
1dde95e
Add note in Known Issues for #130644
luigidellaquila Jul 10, 2025
200ea23
Implement suggestions
luigidellaquila Jul 11, 2025
90f8579
Update docs/release-notes/known-issues.md
luigidellaquila Jul 11, 2025
e29650d
Update docs/release-notes/known-issues.md
luigidellaquila Jul 11, 2025
fa69062
Update docs/release-notes/known-issues.md
luigidellaquila Jul 11, 2025
3462cce
Update docs/release-notes/known-issues.md
luigidellaquila Jul 11, 2025
b72be71
Update docs/release-notes/known-issues.md
luigidellaquila Jul 11, 2025
0bd351f
Fix wording
luigidellaquila Jul 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/reference/query-languages/esql/limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,3 +250,6 @@ Work around this limitation by converting the field to single value with one of
* CSV export from Discover shows no more than 10,000 rows. This limit only applies to the number of rows that are retrieved by the query and displayed in Discover. Queries and aggregations run on the full data set.
* Querying many indices at once without any filters can cause an error in kibana which looks like `[esql] > Unexpected error from Elasticsearch: The content length (536885793) is bigger than the maximum allowed string (536870888)`. The response from {{esql}} is too long. Use [`DROP`](/reference/query-languages/esql/commands/processing-commands.md#esql-drop) or [`KEEP`](/reference/query-languages/esql/commands/processing-commands.md#esql-keep) to limit the number of fields returned.

## Known issues [esql-known-issues]

Refer to [Known issues](/release-notes/known-issues.md) for a list of known issues for {{esql}}.
24 changes: 22 additions & 2 deletions docs/release-notes/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,20 @@ mapped_pages:
Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed in a future release. Review the Elasticsearch known issues to help you make informed decisions, such as upgrading to a new version.

## 9.0.3 [elasticsearch-9.0.3-known-issues]
A bug in the merge scheduler in Elasticsearch 9.0.3 may prevent shards from closing when there isn’t enough disk space to complete a merge. As a result, operations such as closing or relocating an index may hang until sufficient disk space becomes available.
* A bug in the merge scheduler in Elasticsearch 9.0.3 may prevent shards from closing when there isn’t enough disk space to complete a merge. As a result, operations such as closing or relocating an index may hang until sufficient disk space becomes available.
To mitigate this issue, the disk space checker is disabled by default in 9.0.3 by setting `indices.merge.disk.check_interval` to `0` seconds. Manually enabling this setting is not recommended.

This issue is planned to be fixed in future patch release [#129613](https://github.com/elastic/elasticsearch/pull/129613)
This issue is planned to be fixed in future patch release [#129613](https://github.com/elastic/elasticsearch/pull/129613)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@leemthompo the problem is there since 8.16, so also in 9.0.0.
Should the note be in 9.0.0 section instead? What is the best practice here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

(Sorry, I mean the new note of course, two lines below...)

Copy link
Contributor

Choose a reason for hiding this comment

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

@luigidellaquila I think the best practice is to add the known issue to all affected versions

Copy link
Contributor

Choose a reason for hiding this comment

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

this might be hard to do for all the 8.x versions, but probably manageable for the 9.x versions

Copy link
Contributor

Choose a reason for hiding this comment

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

🤔 I wonder if we added a known issues section (or link) in the ESQL limitations page that would be helpful too? Just thinking out loud

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think the best practice is to add the known issue to all affected versions

OK, I'm adding the same note in the 9.0.0 section.

I wonder if we added a known issues section (or link) in the ESQL limitations page that would be helpful too?

I think it makes sense. Probably, in terms of maintenance effort, a link to the known issues is easier to manage. My concern is that we could end up with misalignments if we duplicate information.

I'm adding a new section, please have a look if you have a chance.

Copy link
Contributor

Choose a reason for hiding this comment

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

LGTM


* A bug in ES|QL STATS command may lead to wrong results. The bug only happens in a very specific case, ie. with `STATS ... BY keyword1, keyword2`:
exactly two grouping fields, both keywords, where the first field has high cardinality (more than 65k distinct values).

The issue is described in detail in [this issue](https://github.com/elastic/elasticsearch/issues/130644).
The problem was introduced in 8.16.0 and [fixed](https://github.com/elastic/elasticsearch/pull/130705) in 8.17.9, 8.18.7, 9.0.4,

Possible work-arounds are:
* switching the order of the grouping keys (eg. `STATS ... BY keyword2, keyword1`, if the `keyword2` has a lower cardinality)
* reducing the grouping key cardinality, filtering out values before STATS.

## 9.0.0 [elasticsearch-9.0.0-known-issues]
* Elasticsearch on Windows might fail to start, or might forbid some file-related operations, when referencing paths with a case different from the one stored by the filesystem. Windows treats paths as case-insensitive, but the filesystem stores them with case. Entitlements, the new security system used by Elasticsearch, treat all paths as case-sensitive, and can therefore prevent access to a path that should be accessible.
Expand Down Expand Up @@ -40,3 +50,13 @@ This issue will be fixed in a future patch release (see [PR #126990](https://git
DELETE _index_template/.watches
POST /_watcher/_start
```

* A bug in ES|QL STATS command may lead to wrong results. The bug only happens in a very specific case, ie. with `STATS ... BY keyword1, keyword2`:
exactly two grouping fields, both keywords, where the first field has high cardinality (more than 65k distinct values).

The issue is described in detail in [this issue](https://github.com/elastic/elasticsearch/issues/130644).
The problem was introduced in 8.16.0 and [fixed](https://github.com/elastic/elasticsearch/pull/130705) in 8.17.9, 8.18.7, 9.0.4,

Possible work-arounds are:
* switching the order of the grouping keys (eg. `STATS ... BY keyword2, keyword1`, if the `keyword2` has a lower cardinality)
* reducing the grouping key cardinality, filtering out values before STATS.
Loading