[
https://issues.apache.org/jira/browse/OOZIE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569156#comment-13569156
]
Alejandro Abdelnur commented on OOZIE-1054:
-------------------------------------------
Bowen,
Things look good. Is there any reason why you the sharelibCLI class does not
use OozieCLI (like like the DB tool) to handle the params options? I think that
would simplify the script and the sharelibCLI.
Also, and I'm bringing here OOZIE-670 in scope. As we are consolidating all
setup configuration in Oozie setup, we should see that options feel consistent
for the different tasks.
My thoughts on how things should be through {{oozie-setup.sh}} after everything
is consolidated is:
{code}
oozie-setup.sh prepare-war [-jars <PATHS>] [-extjs <PATH>]
db create -run [-sqlfile <FILE>]
db upgrade -run [-sqlfile <FILE>]
db postupgrade -run [-sqlfile <FILE>]
sharelib create -locallib <PATH> -fs <FS_URI>
sharelib upgrade -locallib <LOCAL_PATH> -fs <FS_URI>
{code}
This means that the oozie-setup.sh script would do for db and sharelib is to
delegate to the CLI removing the sub-command (db or sharelib).
This means that the java CLI (db and sharelib) will have to handle the
subsubcommand and options. the DB CLI already does this. So the integration of
DB CLI in oozie-setup.sh would be simple. That is why I'm asking to do the same
for the sharelib CLI.
Makes sense?
> 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
>
>
> 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
