[SPARK-50311][PYTHON] Support (add|remove|get|clear)Tag(s) APIs for PySpark
#48843
+314
−208
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
itholic
changed the title
(add|remove|get|clear)Tag(s) for PySpark(add|remove|get|clear)Tag(s) APIs for PySpark
itholic
commented
Nov 14, 2024
| from pyspark.testing.connectutils import ReusedConnectTestCase | ||
|
|
||
|
|
||
| class JobCancellationParityTests(JobCancellationTestsMixin, ReusedConnectTestCase): |
There was a problem hiding this comment.
Moved this suite from pyspark.sql.tests.connect.test_session and integrated with JobCancellationTests
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 support
(add|remove|get|clear)Tag(s)for PySparkWhy are the changes needed?
For improving the compatibility between Spark Connect and Spark Classic. These tag-related APIs are currently only supported from Spark Connect.
Does this PR introduce any user-facing change?
New APIs are added
How was this patch tested?
Added UTs
Was this patch authored or co-authored using generative AI tooling?
No