-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-46530][PYTHON][SQL] Check Python executable when looking up available Data Sources #44519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
f009199 to
42f5fd2
Compare
|
cc @ueshin 🙏 |
|
I have reverted #44504 (CommitID: https://github.com/apache/spark/pull/44530/files |
|
Thanks. Let me fix up here. I know the reason. |
42f5fd2 to
2115645
Compare
61e5bb4 to
6f59d34
Compare
|
@LuciferYang @dongjoon-hyun @zhengruifeng if anyone is online can you merge this one please ? I will have to be away from keyboard today.. and this technically fixes the build. |
|
merged to master |
|
Thx thx |
|
late LGTM, thanks @HyukjinKwon for fixing this |
…file separator to correctly check PySpark library existence ### What changes were proposed in this pull request? This PR is a followup of #44519 that fixes a mistake of separating the paths. It should use `Files.pathSeparator`. ### Why are the changes needed? It works with testing mode, but it doesn't work with production mode otherwise. ### Does this PR introduce _any_ user-facing change? No, because the main change has not been released. ### How was this patch tested? Manually as described in "How was this patch tested?" at #44504. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #44590 from HyukjinKwon/SPARK-46530-followup. Authored-by: Hyukjin Kwon <[email protected]> Signed-off-by: Hyukjin Kwon <[email protected]>
What changes were proposed in this pull request?
This PR is a sort of followup of #44504 but addresses a separate issue. This PR proposes to check:
Why are the changes needed?
For some OSes such as Windows, or minimized Docker containers, there is no Python installed, and it will just fail even when users want to use Scala only. We should check the Python executable, and skip if that does not exist.
Does this PR introduce any user-facing change?
No because the main change has not been released out yet.
How was this patch tested?
Manually tested.
Was this patch authored or co-authored using generative AI tooling?
No.