[SPARK-55663][PYTHON] Unify __module__ for data source functions#54457
Open
gaogaotiantian wants to merge 3 commits intoapache:masterfrom
Open
[SPARK-55663][PYTHON] Unify __module__ for data source functions#54457gaogaotiantian wants to merge 3 commits intoapache:masterfrom
gaogaotiantian wants to merge 3 commits intoapache:masterfrom
Conversation
HyukjinKwon
approved these changes
Feb 24, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What changes were proposed in this pull request?
Always set
__module__to be something meaningful for datasource functions and workers.Why are the changes needed?
The data source profiler depends on the module name of the worker/function. When invoked with simpler worker, the
__module__would be__main__which is not informative enough for the profilers. We should avoid having them to be__main__.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Locally simple worker + profiler recognizes it.
Was this patch authored or co-authored using generative AI tooling?
No.