[SPARK-35705][PYTHON] Adjust pandas-on-spark test_groupby_multiindex_columns test for different pandas versions
#32851
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
|
Test build #139599 has finished for PR 32851 at commit
|
|
Kubernetes integration test starting |
HyukjinKwon
approved these changes
Jun 10, 2021
|
Merged to master. |
|
Kubernetes integration test status failure |
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.
What changes were proposed in this pull request?
Adjust pandas-on-spark test_groupby_multiindex_columns test in order to pass with different pandas versions.
Why are the changes needed?
pandas had introduced bugs as below:
For pandas 1.1.3 and 1.1.4
Type error: only integer scalar arrays can be converted to a scalar index
For pandas < 1.0.4
Type error: Can only tuple-index with a MultiIndex
We ought to adjust
test_groupby_multiindex_columnstests by comparing with a predefined return value, rather than comparing with the pandas return value in the pandas versions above.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit tests.