[
https://issues.apache.org/jira/browse/OOZIE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852464#comment-15852464
]
Hadoop QA commented on OOZIE-2786:
----------------------------------
Testing JIRA OOZIE-2786
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
. {color:red}WARNING: the current HEAD has 1 RAT warning(s), they should be
addressed ASAP{color}
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in
[hadooplibs/hadoop-utils-2].
. {color:green}+1{color} There are no new bugs found in [client].
{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}
. Tests run: 1868
. Tests failed: 0
. Tests errors: 2
. The patch failed the following testcases:
.
. Tests failing with errors:
.
testCoordRerunWithFailedOption(org.apache.oozie.command.coord.TestCoordRerunXCommand)
. testOozieSharelibCLICreate(org.apache.oozie.tools.TestOozieSharelibCLI)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3611/
> Pass Oozie workflow ID and settings to Spark application configuration
> ----------------------------------------------------------------------
>
> Key: OOZIE-2786
> URL: https://issues.apache.org/jira/browse/OOZIE-2786
> Project: Oozie
> Issue Type: Improvement
> Components: action
> Reporter: Xiaobin Zheng
> Assignee: Xiaobin Zheng
> Priority: Critical
> Attachments: OOZIE-2786-1.patch
>
>
> When using Oozie to launch Spark applications, the Oozie work flow ID and etc
> do not show up in Spark Application's Environment settings. There is no Spark
> application ID exposed from Oozie side as well about the Spark applications
> Oozie launches.
> When looking at applications in Spark History Server, it is hard to figure
> out which Oozie workflow launched it. This makes debugging the workflow hard.
> We want to be able to let Spark History server display the Oozie workflow ID
> in the application's 'Environment' settings.
> For reference, oozie properties that can be passed to Spark are:
> oozie.job.id
> oozie.HadoopAccessorService.created
> oozie.action.spark.setup.hadoop.conf.dir
> oozie.child.mapreduce.job.tags
> oozie.action.id
> oozie.action.rootlogger.log.level
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
