[CI][Transform] fix GroupByOptimizerTests randomization failure part 2 #76009
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hendrikmuhs
added
>test
Collaborator
|
Pinging @elastic/ml-core (Team:ML) |
benwtrent
approved these changes
Aug 3, 2021
elasticsearchmachine
pushed a commit
to elasticsearchmachine/elasticsearch
that referenced
this pull request
Aug 3, 2021
elastic#76009) avoid clashing field name by using a unique prefix fixes elastic#75957
Collaborator
💚 Backport successful
|
lockewritesdocs
pushed a commit
to lockewritesdocs/elasticsearch
that referenced
this pull request
Aug 3, 2021
elastic#76009) avoid clashing field name by using a unique prefix fixes elastic#75957
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
avoid clashing field name by using a unique prefix
fixes #75957
Similar to #75928: the random generation of fieldnames generated a duplicate, this is usually not a problem, but in this failure case, the field was configured as runtime which breaks the test for certain random seeds