Test inset with NaN only for Spark from 3.1.3
#9928
Merged
Conversation
This file contains 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: Nghia Truong <[email protected]>
ttnghia
added
documentation
jlowe
reviewed
Dec 1, 2023
Co-authored-by: Jason Lowe <[email protected]>
Co-authored-by: Jason Lowe <[email protected]>
Signed-off-by: Nghia Truong <[email protected]>
ttnghia
commented
Dec 1, 2023
jlowe
approved these changes
Dec 1, 2023
|
build |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Before Apache Spark 3.1.3, the
insetoperator may treatNaNas different values (https://issues.apache.org/jira/browse/SPARK-36792) while our plugin and Spark from 3.1.3 comparesNaNas equal values. This eliminatesNaNfrom the input test for Spark before version 3.1.3 and updates documentation about such inconsistent outcomes ofNaNcomparison.Closes #9687.