Github user buckhx commented on the pull request:
https://github.com/apache/spark/pull/12398#issuecomment-211420495
I could see the pipBase approach working.
The other testing blocker I have is that it seems like that context that's
getting created in the test is able to use local packages. The test package
that's created is able to be imported on the workers without distributing it
via addPyPackage.
https://github.com/apache/spark/pull/12398/files#diff-388a156f4ce454fe98d7a99a0f7f0012R1950
Is there a way to get the mocked workers to not use the master python path?
The pip part is nice, but I think the meat of this PR is in the
addPyPackage.
I looked into adding a flag to the CLI, but kind of went down a rabbit hole
trying to figure it out. I'd advocate adding it to the CLI, but think someone
working in the spark core space could get that integrated much more efficiently
than myself.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
