Skip to content

[8.x] Added known issue entry for synthetic source bug. (#113269) #113358

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 1 commit into from
Sep 23, 2024
Merged

[8.x] Added known issue entry for synthetic source bug. (#113269) #113358

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 8 additions & 0 deletions docs/reference/release-notes/8.15.0.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,14 @@ To work around this issue, you have a number of options:
<<esql-kibana-enable,disable ES|QL queries in {kib}>>
** Change the default data view in Discover to a smaller set of indices and/or one with fewer mapping conflicts.

* Synthetic source bug. Synthetic source may fail generating the _source at runtime, causing failures in get APIs or
partial failures in the search APIs. The result is that for the affected documents the _source can't be retrieved.
There is no workaround and the only option to is to upgrade to 8.15.2 when released.
+
If you use synthetic source then you may be affected by this bug if the following is true:
** If you have more fields then the `index.mapping.total_fields.limit` setting allows.
** If you use dynamic mappings and the `index.mapping.total_fields.ignore_dynamic_beyond_limit` setting is enabled.

[[breaking-8.15.0]]
[float]
=== Breaking changes
Expand Down
9 changes: 8 additions & 1 deletion docs/reference/release-notes/8.15.1.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,13 +24,20 @@ To work around this issue, you have a number of options:
<<esql-kibana-enable,disable ES|QL queries in {kib}>>
** Change the default data view in Discover to a smaller set of indices and/or one with fewer mapping conflicts.

* Index Stats, Node Stats and Cluster Stats API can return a null pointer exception if an index contains a `dense_vector` field
* Index Stats, Node Stats and Cluster Stats API can return a null pointer exception if an index contains a `dense_vector` field
but there is an index segment that does not contain any documents with a dense vector field ({es-pull}112720[#112720]). Workarounds:
** If the affected index already contains documents with a dense vector field, force merge the index to a single segment.
** If the affected index does not already contain documents with a dense vector field, index a document with a dense vector field
and then force merge to a single segment.
** If the affected index's `dense_vector` fields are unused, reindex without the `dense_vector` fields.

* Synthetic source bug. Synthetic source may fail generating the _source at runtime, causing failures in get APIs or
partial failures in the search APIs. The result is that for the affected documents the _source can't be retrieved.
There is no workaround and the only option to is to upgrade to 8.15.2 when released.
+
If you use synthetic source then you may be affected by this bug if the following is true:
** If you have more fields then the `index.mapping.total_fields.limit` setting allows.
** If you use dynamic mappings and the `index.mapping.total_fields.ignore_dynamic_beyond_limit` setting is enabled.

[[bug-8.15.1]]
[float]
Expand Down
Loading