[multistage] Handle Integer.MIN_VALUE in FieldSelectionKeySelector #10596
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.
Saw this in our production where one of the inputs hashes to
Integer.MIN_VALUE
.Math.abs
returns negation of the input number if the input number is negative. So forInteger.MIN_VALUE
, it returns the same value. This is also documented in the docs forMath.abs
.In other places like
MurmurPartitionFunction
,HashCodePartitionFunction
, etc. we seem to be already doing this so looks like it's a known thing.