[
https://issues.apache.org/jira/browse/OOZIE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571952#comment-13571952
]
Bowen Zhang commented on OOZIE-1054:
------------------------------------
I don't think we should delegate the parsing to the OozieSharelibCLI like the
way in OozieDBCLI.
If the user types: oozie-setup.sh prepare-war -hadooop version hadoop_home
-extjs path sharelib create -fs uri -locallib path, are we trying to jam all
these command line stuff to OozieSharelibCLI via "${@}"? This is adding
unnecessary complexities into OozieSharelibCLI.
And if the user types: oozie-setup.sh prepare-war -hadooop version hadoop_home
-extjs path sharelib create -fs uri, then are we letting the java class to
figure out the default sharelib.tar.gz?
BTW, when I type oozie-setup.sh help, it will indeed print out the usage info,
isn't it what we want?
> Create script to properly upload sharelib to HDFS
> -------------------------------------------------
>
> Key: OOZIE-1054
> URL: https://issues.apache.org/jira/browse/OOZIE-1054
> Project: Oozie
> Issue Type: New Feature
> Components: scripts
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Bowen Zhang
> Priority: Minor
> Fix For: trunk
>
> Attachments: oozie-1054.patch, oozie-1054.patch, oozie-1054.patch,
> oozie-1054.patch, oozie-1054.patch, oozie-1054.patch, oozie-1054.patch,
> oozie-1054.patch, oozie-1054.patch, oozie-1054.patch, oozie-1054.patch
>
>
> A common confusion-point for users is how to properly install the sharelib in
> HDFS. It would be really useful if we could create a script to properly
> upload the sharelib to HDFS so we can get rid of the confusion around this.
> Alternatively, instead of a new script, we could have the oozie-setup.sh
> script take an argument that does this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
