[
https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760036#comment-13760036
]
Hadoop QA commented on OOZIE-1461:
----------------------------------
Testing JIRA OOZIE-1461
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 11 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:red}-1 COMPILE{color}
. {color:red}-1{color} HEAD does not compile
. {color:red}-1{color} patch does not compile
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
. {color:red}-1{color} distro tarball fails with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/767/
> provide an option to auto-deploy launcher jar onto HDFS system libpath
> ----------------------------------------------------------------------
>
> Key: OOZIE-1461
> URL: https://issues.apache.org/jira/browse/OOZIE-1461
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Ryota Egashira
> Assignee: Virag Kothari
> Fix For: trunk
>
> Attachments: OOZIE-1461_2.patch, OOZIE-1461_2.patch,
> OOZIE-1461.patch, OOZIE-1461.patch, OOZIE-1461.patch
>
>
> after OOZIE-1311, 1315, when oozie.action.ship.launcher.jar is false,
> launcher jar is shipped from sharelib, but it requires manual process for
> admin people to upload jar files onto the sharelib at server-start time,
> before actually starting running workflow actions. This JIRA to provide an
> option to remove the manual process, and make oozie server (ActionService) to
> automatically create and upload launcher jar files onto HDFS (tmp directory
> under oozie.service.WorkflowAppService.system.libpath), and allow workflow
> actions to consume from there. every time oozie server starts, it
> automatically creates a new directory to upload launcher jars to, and also
> purges stale directories previously created (older than 7 days,
> configurable).
> if false (which is current default). the behavior is the same with previous,
> launcher jars provided from sharelib (when
> oozie.action.ship.launcher.jar=false) or each workflow action creates and
> ships launcher jar (when oozie.action.ship.launcher.jar=true)
--
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
