[FLINK-629] getFieldNotNull added to Tuple and updated operators #73
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
…d Comparators to use that where appropriate
Contributor
zhijiangW
pushed a commit
to zhijiangW/flink
that referenced
this pull request
Jul 23, 2019
This closes apache#73.
tzulitai
pushed a commit
to tzulitai/flink
that referenced
this pull request
Jan 15, 2021
This closes apache#73.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Operators which use key comparisons now use getFieldNotNull for getting the key fields, which will throw NullKeyFieldException if the key is null. Aggregators are also updated to use getFieldNotNull and will throw a NullFieldExceptions if the field is null.
The TupleSerializer now throws NullFieldException when it encounters a null field it cannot serialize instead of a NullPointerException.