-
Notifications
You must be signed in to change notification settings - Fork 49
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
Support for Oozie lib .jar files #301
Labels
enhancement
New feature or request
Comments
potiuk
changed the title
Oozie support for lib .jar files
Support for Oozie lib .jar files
Jul 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Ooozie adds all the .jar files which are in the lib folder of the workflow application to the classpath automatically. This is currently only implemented in Java Mapper.
Describe the solution you'd like
All the mappers should have .jar files added to the classpath.
Describe alternatives you've considered
No alternatives.
Additional context
Each Oozie operator has its own way of adding jars to classpath so it should be done in mapper-specific way. Currently in workflow.py the lib folder is scanned for all .jar files and they are stored in Workflow.
For all the Map-Reduce jobs that are not executed as single-node mapper (on master), the .jar files should be added to Local Cache.
The text was updated successfully, but these errors were encountered: