[
https://issues.apache.org/jira/browse/OOZIE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057610#comment-15057610
]
Hadoop QA commented on OOZIE-547:
---------------------------------
Testing JIRA OOZIE-547
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:red}-1{color} the patch contains 58 line(s) with 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 8 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:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:red}-1{color} the patch seems to introduce 7 new javac warning(s)
{color:red}-1 BACKWARDS_COMPATIBILITY{color}
. {color:red}-1{color} the patch seems to change 4 line(s) with 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: 1709
. Tests failed: 4
. Tests errors: 0
. The patch failed the following testcases:
. testWorkflowJobMappings(org.apache.oozie.client.rest.TestJsonToBean)
. testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
. testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)
. testUpdateSLA(org.apache.oozie.sla.TestSLAService)
{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}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2655/
> build workflow progress information in Oozie
> --------------------------------------------
>
> Key: OOZIE-547
> URL: https://issues.apache.org/jira/browse/OOZIE-547
> Project: Oozie
> Issue Type: New Feature
> Reporter: Hadoop QA
> Assignee: zhu jin wei
> Attachments: oozie-547-1.patch, oozie-547-2.patch, oozie-547.patch
>
>
> For a user, knowing progress of her workflow is always desirable. This ticket
> is to introduce this support to Oozie.
> I know it's a hard problem. For my initial effort, I plan to start with
> simple workflows that do not contain decision nodes or fork/join nodes, i.e.,
> chain type workflows. I plan to use percentage of finished actions as the
> overall wf progress estimate.
> Going forward we can improve the estimation by:
> 1) handle general workflows that contain decision, fork/join nodes;
> 2) incorporate the action level progress into wf level progress estimation to
> make the estimate better. To be more specific:
> In the case of "opaque" actions like pig/hive/jaql where the status can only
> be 0% or 100% (or failure) we plug that value into the overall DAG status of
> 0-100%. If a DAG had say 4 opaque actions, the progress would move in
> discrete steps 0, 25, 50, 75, 100%. For the m/r actions where the JobTracker
> gives values between 0-100% for an action then the overall progress will be
> smoother. We can do same thing for pig/hive/jaql actions as well if they
> expose their own progress info.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
