-
Notifications
You must be signed in to change notification settings - Fork 313
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
Use zeros instead of whitespaces as padding bytes #899
Conversation
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 @drawlerr !
Arrg. Seems we've managed to coax out an unrelated race condition in Rally during the integration test. I've written this up in #900, but for now I'm just going to run tests again as we shouldn't be unlucky enough to hit it twice in a row: @elasticsearchmachine run tests |
@elasticmachine test this please |
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 changing this. I'm fine with the actual change but:
- IMHO this is a breaking change: We should label it as such and add a small note to your migration docs.
- I don't think this is a bug but rather an enhancement?
- Once merged, can you please keep an eye on all our update-related workloads as their performance might be impacted by this change? If this is the case, can you please add an according annotation?
Woohoo |
It is more realistic to use 0-padding than whitespace padding in IDs, and this is the format Elasticsearch prefers anyways.
Applying @jpountz 's patch for ID generation, fixing associated tests.
Closes #896