More precise sharding logic for on|ignoring
#8461
Merged
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
Signed-off-by: Owen Diehl <[email protected]>
owen-d
changed the title
on|ignoring
Signed-off-by: Owen Diehl <[email protected]>
owen-d
force-pushed
the
non-shardable-vectorExpr-tests
branch
from
3ce0b2c to
1ea3be7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
While adding some tests to compliment #8448, I noticed some imprecision when determining whether a binary operation is shardable. Particularly,
ongrouping or when usingignoringwith a non-zero set of labels to ignore as this can mutate labels.ignoring ()is effectively the zero value which cannot mutate labels.