You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use mappings to format doc-value fields by default. (#30831)
Doc-value fields now return a value that is based on the mappings rather than
the script implementation by default.
This deprecates the special `use_field_mapping` docvalue format which was added
in #29639 only to ease the transition to 7.x and it is not necessary anymore in
7.0.
Copy file name to clipboardExpand all lines: rest-api-spec/src/main/resources/rest-api-spec/test/search/10_source_filtering.yml
+11-17
Original file line number
Diff line number
Diff line change
@@ -144,12 +144,9 @@ setup:
144
144
---
145
145
"docvalue_fields":
146
146
- skip:
147
-
version: " - 6.4.0"
148
-
reason: format option was added in 6.4 and the deprecation message changed in 6.4.1
149
-
features: warnings
147
+
version: " - 6.9.99"
148
+
reason: Triggers a deprecation warning before 7.0
150
149
- do:
151
-
warnings:
152
-
- 'There are doc-value fields which are not using a format. The output will change in 7.0 when doc value fields get formatted based on mappings by default. It is recommended to pass [format=use_field_mapping] with a doc value field in order to opt in for the future behaviour and ease the migration to 7.0: [count]'
153
150
search:
154
151
body:
155
152
docvalue_fields: [ "count" ]
@@ -158,12 +155,9 @@ setup:
158
155
---
159
156
"multiple docvalue_fields":
160
157
- skip:
161
-
version: " - 6.4.0"
162
-
reason: format option was added in 6.4 and the deprecation message changed in 6.4.1
163
-
features: warnings
158
+
version: " - 6.9.99"
159
+
reason: Triggered a deprecation warning before 7.0
164
160
- do:
165
-
warnings:
166
-
- 'There are doc-value fields which are not using a format. The output will change in 7.0 when doc value fields get formatted based on mappings by default. It is recommended to pass [format=use_field_mapping] with a doc value field in order to opt in for the future behaviour and ease the migration to 7.0: [count, include.field1.keyword]'
reason: format option was added in 6.4 and the deprecation message changed in 6.4.1
177
-
features: warnings
169
+
version: " - 6.99.99"
170
+
reason: Triggered a deprecation warning before 7.0
178
171
- do:
179
-
warnings:
180
-
- 'There are doc-value fields which are not using a format. The output will change in 7.0 when doc value fields get formatted based on mappings by default. It is recommended to pass [format=use_field_mapping] with a doc value field in order to opt in for the future behaviour and ease the migration to 7.0: [count]'
181
172
search:
182
173
docvalue_fields: [ "count" ]
183
174
- match: { hits.hits.0.fields.count: [1] }
184
175
185
176
---
186
177
"docvalue_fields with default format":
187
178
- skip:
188
-
version: " - 6.3.99"
189
-
reason: format option was added in 6.4
179
+
version: " - 6.99.99"
180
+
reason: Only triggers warnings on 7.0+
181
+
features: warnings
190
182
- do:
183
+
warnings:
184
+
- "[use_field_mapping] is a special format that was only used to ease the transition to 7.x. It has become the default and shouldn't be set explicitly anymore."
Copy file name to clipboardExpand all lines: rest-api-spec/src/main/resources/rest-api-spec/test/search/30_limits.yml
+5-8
Original file line number
Diff line number
Diff line change
@@ -67,8 +67,8 @@ setup:
67
67
"Docvalues_fields size limit":
68
68
69
69
- skip:
70
-
version: " - 6.3.99"
71
-
reason: "The object notation for docvalue_fields is only supported on 6.4+"
70
+
version: " - 6.99.99"
71
+
reason: "Triggers warnings before 7.0"
72
72
- do:
73
73
catch: /Trying to retrieve too many docvalue_fields\. Must be less than or equal to[:] \[2\] but was \[3\]\. This limit can be set by changing the \[index.max_docvalue_fields_search\] index level setting\./
0 commit comments