Fix EXTENDED_DOC_VALUES_PARAMS test cluster feature flag.#140519
Fix EXTENDED_DOC_VALUES_PARAMS test cluster feature flag.#140519martijnvg merged 4 commits intoelastic:mainfrom
Conversation
)" This reverts commit 8e3d3c9.
And use it in x-pack yaml integration test.
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
craigtaverner
left a comment
There was a problem hiding this comment.
If this works, it is great. I think we should add test-release to this PR to be sure of it.
| path: /_query | ||
| parameters: [ ] | ||
| capabilities: [ extended_doc_values_params ] | ||
| cluster_features: ["mapper.keyword.high_cardinality_length_function_fuse_to_load"] |
There was a problem hiding this comment.
Does this work? How does it connect to extended_doc_values_options_feature_flag_enabled?
There was a problem hiding this comment.
Ah, I spoke too soon. The line in XPackRestIT turns on this feature for all tests, so we no longer need to have a condition here related to the extended doc values params.
There was a problem hiding this comment.
It doesn't, the feature flag is now always set for test clusters in release builds.
|
The release-tests checkPart3 fail because of the same reason that was reported here: #140388 (comment) I will merge this PR. |
…0519) And use it in x-pack yaml integration test.
…0519) And use it in x-pack yaml integration test.
And use it in x-pack yaml integration test.