Skip to content
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

Closed
potiuk opened this issue Jul 9, 2019 · 0 comments
Closed

Support for Oozie lib .jar files #301

potiuk opened this issue Jul 9, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@potiuk
Copy link
Collaborator

potiuk commented Jul 9, 2019

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.

@potiuk potiuk added the enhancement New feature or request label Jul 9, 2019
@potiuk potiuk changed the title Oozie support for lib .jar files Support for Oozie lib .jar files Jul 9, 2019
@potiuk potiuk mentioned this issue Jul 9, 2019
4 tasks
@potiuk potiuk removed this from the Delta (nice-to-have time permitting) milestone Jul 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants