You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The --archives option only works for YARM setups. Databricks, for example, does not use YARM so the --archives parameter has no effect.
Describe the solution you'd like
For the application .zip file to be transferred to all workers, extracted and the contents to be in the assembly search path.
Describe alternatives you've considered
A partial workaround is adding the applications .zip file name to the --files parameter meets the first requirement of transferring it to all workers. However, it is not automatically extracted or added to the assembly search path.
I have created two alternative pull requests for two different ways of fixing this.
Option 1 - #193 - Unzips all .zip archives in the working directory.
Option 2 - #194 - Only unzips a .zip archive matching the Application Archive name.
Both options then add the extracted folder to the Assembly Search Path.
Is your feature request related to a problem? Please describe.
This is in relation to one of the new features added in v0.4.0:
The
--archives
option only works for YARM setups. Databricks, for example, does not use YARM so the--archives
parameter has no effect.Describe the solution you'd like
For the application .zip file to be transferred to all workers, extracted and the contents to be in the assembly search path.
Describe alternatives you've considered
A partial workaround is adding the applications .zip file name to the
--files
parameter meets the first requirement of transferring it to all workers. However, it is not automatically extracted or added to the assembly search path.Databricks Spark-Submit example:
The text was updated successfully, but these errors were encountered: