Fix rally-annotations index creation #1747
Merged
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.
Addresses #1746.
The following naive fix reveals more problems:
Output:
Stack trace:
Therefore the problem is not only the missing
index
object inannotations-template.json
which is what #1746 suggests but also upgraded Python Elasticsearch client is more strict when evaluatingbody
parameter in indexcreate
method.This PR addresses the problem by aligning
rally-annotations
index creation handling with other indices, i.e. by usingrally-annotations
index template. This simplicity comes at a cost of slightly "wasteful" configuration if users decided to increasedatastore.number_of_shards
setting (rally-annotations
is tiny).I've tested the change in staging environment: