[
https://issues.apache.org/jira/browse/BIGTOP-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated BIGTOP-1170:
----------------------------------
Attachment: 0001-BIGTOP-1170.-Add-an-easier-tool-for-uploading-creati.patch
Oozie has a script called oozie-setup.sh that can handle a lot of this, so it
would be good not to duplicate that. This patch packages that script, and
provides a wrapper that detects JAVA_HOME, blocks the use of the prepare-war
command that doesn't make sense in a Bigtop context, and invokes the underlying
script.
I just tested that it can correctly create and upgrade the sharelib (it does so
as the oozie user, so you need to invoke the script with 'sudo'). I originally
had the script `cd ~` after su-ing to oozie, just in case the command created
any files and needed to be in a directory where it could do so. I removed it
however so that relative paths to a sharelib would resolve correctly, and I did
not see any problems invoking this command in a directory where oozie does not
have write permissions.
> 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)
