[
https://issues.apache.org/jira/browse/BIGTOP-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855846#comment-13855846
]
Robert Kanter commented on BIGTOP-1170:
---------------------------------------
That sounds like a good idea. oozie-setup.sh has a script (that simply runs a
java program in Oozie) to upload the sharelib properly. Upcoming changes in
Oozie will make it more difficult for you to simply upload the sharelib to HDFS
because it will be in a timestamped dir (e.g.
/user/oozie/share/lib/lib_TIMESTAMP/pig) so having your script call the
oozie-setup.sh would be best. This will also be helpful to prevent users from
calling oozie-setup.sh directly in Bigtop when they want to update the
sharelib, which we don't really want because there's some other commands in
oozie-setup.sh that should only be used in a tarball deployment.
> Add an easier tool for uploading / creating the sharelib
> --------------------------------------------------------
>
> Key: BIGTOP-1170
> URL: https://issues.apache.org/jira/browse/BIGTOP-1170
> Project: Bigtop
> Issue Type: Bug
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Attachments:
> 0001-BIGTOP-1170.-Add-an-easier-tool-for-uploading-creati.patch
>
>
> Here's an idea for making Oozie sharelib management easier if users want to
> update or other customize their oozie sharelib. Currently init-hdfs.sh
> installs the "default" sharelib for you (assuming that Oozie is installed at
> the time you run it). According to some Oozie devs, however, the difficulty
> of correctly installing the oozie sharelib is the biggest source of user
> problems - so I think providing a tool to install it later or installed a
> slightly different sharelib would be helpful.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
