[ 
https://issues.apache.org/jira/browse/OOZIE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549315#comment-16549315
 ] 

Attila Sasvari commented on OOZIE-2829:
---------------------------------------

If you look at how Hadoop components are handling/pass multiple files/jars, you 
pretty often see a comma separated list of files:

- YARN / Map-Reduce: {{--libjars}}:
https://hadoop.apache.org/docs/r2.8.2/hadoop-project-dist/hadoop-common/CommandsManual.html#Generic_Options
- Apache Spark: spark-submit 
https://spark.apache.org/docs/latest/submitting-applications.html
- Apache Pig - pig.additional.jars.uris
- Apache Oozie - Sharelib mapping file: 
https://oozie.apache.org/docs/5.0.0/AG_Install.html#Oozie_Share_Lib

I think it would be better to specify a comma separated list of files for a 
given extra sharelib. 

> Improve sharelib upload to accept multiple source folders
> ---------------------------------------------------------
>
>                 Key: OOZIE-2829
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2829
>             Project: Oozie
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 5.0.0
>            Reporter: Peter Cseh
>            Assignee: Julia Kinga Marton
>            Priority: Major
>             Fix For: 5.1.0
>
>         Attachments: OOZIE-2829-006.patch, OOZIE-2829-007.patch, 
> OOZIE-2829-008.patch, OOZIE-2829-01.patch, OOZIE-2829-02.patch, 
> OOZIE-2829-03.patch, OOZIE-2829-04.patch, OOZIE-2829-05.patch
>
>
> Right now sharelib can be created via {{sharelib create -fs FS_URI -locallib 
> SHARED_LIBRARY}} where the SHARED_LIBRARY can be a tarbal or a folder. 
> It would be nice to have the possibility to define additional folders to be 
> uploaded into the sharelib, so the users don't have to copy or link the files 
> together on their machine.
> The syntax could be something like -additional-lib 
> sharelibName=/path/to/source/;/path/to/some/file,sharelibName2=/path/to/some/folder



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to