-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for elastic/logs many-shards-quantitative #566
Fix for elastic/logs many-shards-quantitative #566
Conversation
"request-params": { | ||
"include_empty_fields": "false" | ||
} | ||
"base-operation-type": "raw-request", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The base-operation-type
parameter makes only sense with a custom runner referenced through "operation-type": "multi-cluster-wrapper"
. The purpose of it is to execute the base operation on all clusters passed to Rally. I don't think we need it in this challenge, so I would simplify to "operation-type": "raw-request"
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the input, corrected!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Track
field-caps-exclude-empty-fields
now usesraw-request
in order to work around python client not supporting new optional query parameterinclude_empty_fields
.closes #564