File tree Expand file tree Collapse file tree 2 files changed +16
-1
lines changed
docs/reference/release-notes Expand file tree Collapse file tree 2 files changed +16
-1
lines changed Original file line number Diff line number Diff line change @@ -44,6 +44,14 @@ To work around this issue, you have a number of options:
44
44
<<esql-kibana-enable,disable ES|QL queries in {kib}>>
45
45
** Change the default data view in Discover to a smaller set of indices and/or one with fewer mapping conflicts.
46
46
47
+ * Synthetic source bug. Synthetic source may fail generating the _source at runtime, causing failures in get APIs or
48
+ partial failures in the search APIs. The result is that for the affected documents the _source can't be retrieved.
49
+ There is no workaround and the only option to is to upgrade to 8.15.2 when released.
50
+ +
51
+ If you use synthetic source then you may be affected by this bug if the following is true:
52
+ ** If you have more fields then the `index.mapping.total_fields.limit` setting allows.
53
+ ** If you use dynamic mappings and the `index.mapping.total_fields.ignore_dynamic_beyond_limit` setting is enabled.
54
+
47
55
[[breaking-8.15.0]]
48
56
[float]
49
57
=== Breaking changes
Original file line number Diff line number Diff line change @@ -24,13 +24,20 @@ To work around this issue, you have a number of options:
24
24
<<esql-kibana-enable,disable ES|QL queries in {kib}>>
25
25
** Change the default data view in Discover to a smaller set of indices and/or one with fewer mapping conflicts.
26
26
27
- * Index Stats, Node Stats and Cluster Stats API can return a null pointer exception if an index contains a `dense_vector` field
27
+ * Index Stats, Node Stats and Cluster Stats API can return a null pointer exception if an index contains a `dense_vector` field
28
28
but there is an index segment that does not contain any documents with a dense vector field ({es-pull}112720[#112720]). Workarounds:
29
29
** If the affected index already contains documents with a dense vector field, force merge the index to a single segment.
30
30
** If the affected index does not already contain documents with a dense vector field, index a document with a dense vector field
31
31
and then force merge to a single segment.
32
32
** If the affected index's `dense_vector` fields are unused, reindex without the `dense_vector` fields.
33
33
34
+ * Synthetic source bug. Synthetic source may fail generating the _source at runtime, causing failures in get APIs or
35
+ partial failures in the search APIs. The result is that for the affected documents the _source can't be retrieved.
36
+ There is no workaround and the only option to is to upgrade to 8.15.2 when released.
37
+ +
38
+ If you use synthetic source then you may be affected by this bug if the following is true:
39
+ ** If you have more fields then the `index.mapping.total_fields.limit` setting allows.
40
+ ** If you use dynamic mappings and the `index.mapping.total_fields.ignore_dynamic_beyond_limit` setting is enabled.
34
41
35
42
[[bug-8.15.1]]
36
43
[float]
You can’t perform that action at this time.
0 commit comments