Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7139#issuecomment-126765707
I see - so the right thing to do is to not build the package on every node
which needs this (driver / executor) but to build it once in the spark-submit
node and then carry the binary package along with the job in `--files` or
`--archives` etc. AFAIK this is how @sun-rui got the YARN cluster mode to work
(You can see the zip file of the SparkR package being created at [1])
Can we do something similar here ?
[1]
https://github.com/apache/spark/blob/27ae851ce16082775ffbcb5b8fc6bdbe65dc70fc/R/install-dev.sh#L47
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
