Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR passes configuration context to
Query
,DeleteIndex
andDeleteComposableTemplate
runners to make them serverless-aware and change their behaviour if Rally targets serverless cluster.Changes:
Query
,DeleteIndex
andDeleteComposableTemplate
stop getting and setting cluster settings throughset_destructive_requires_name()
as cluster settings are not available to serverless users. In case ofDeleteIndex
this replaces the earlier crude workaround throughcontextlib.suppress
introduced in Fix serverless public use in trivial tracks #1785.DeleteComposableTemplate
runner starts to ignoredelete_matching_indices
template option. Wildcard deletes are not available to serverless users (!).DeleteIndexTemplate
runner is not fixed as legacy templates are not available in serverless.Query
runner (search
,paginated-search
,composite-agg
andscroll-search
operations). In non-serverless use we typically rely on"index.requests.cache.enable": false
index setting for this purpose but it is not available to serverless users. As part of this change I've removed request params in/_search/scroll
which is present in certainQuery
scenarios, as/_search/scroll
does not acceptrequest_cache
parameter and it is the only parameter used.