[SPARK-48250][PYTHON][CONNECT][TESTS] Enable array inference tests at test_parity_types.py #46550
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
zhengruifeng
approved these changes
May 13, 2024
|
nit: we might create subtasks under umbrella https://issues.apache.org/jira/browse/SPARK-47970 |
|
Merged to master. |
|
Oops, I saw a CI in differnet PR, and thought the tests passed. Sorry reverting |
|
Hm, actually the tests passed at https://github.com/HyukjinKwon/spark/actions/runs/9058021158 |
|
hmmm .. let me rebase and see |
HyukjinKwon
force-pushed
the
SPARK-48250
branch
3 times, most recently
from
afad546
to
83ca50e
Compare
|
Merged to master. |
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?
This PR proposes to enable some array inference tests at test_parity_types.py
Why are the changes needed?
For better test coverage for Spark Connect.
Does this PR introduce any user-facing change?
No, test-only.
How was this patch tested?
CI in this PR should verify them.
Was this patch authored or co-authored using generative AI tooling?
No.