Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.23.0
-
None
-
None
Description
Downstream projects will be generating their own classpath file to allow yarn to launch containers correctly in a unit-test env which may potentially create a clash if 2 versions are present.
The current code in MRApps assumes that the generated classpath is always present which may need to be addressed if this file is not present when deployed on a cluster. An option for a fix could be to pass the location of the classpath file via the MiniYarnCluster constructor and propagate that to MRApps via some form of configuration value.