[jira] [Commented] (OOZIE-2827) More directly view of the coordinator’s history from perspective of workflow action.

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929714#comment-15929714 ] 

Hadoop QA commented on OOZIE-2827:
----------------------------------

Testing JIRA OOZIE-2827

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:red}-1{color} the patch contains 1 line(s) longer than 132 characters
.    {color:green}+1{color} the patch does adds/modifies 3 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: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:red}-1{color} There are [1] new bugs found below threshold in total that must be fixed.
.    {color:green}+1{color} There are no new bugs found in [client].
.    {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/distcp].
.    {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:red}-1{color} There are [1] new bugs found below threshold in [core] that must be fixed.
.    You can find the FindBugs diff here (look for the red and orange ones): core/findbugs-new.html
.    The most important FindBugs errors are:
.    Dereferenced at CoordWfActionInfoXCommand.java:[line 76]: Possible null pointer dereference of null in org.apache.oozie.command.coord.CoordWfActionInfoXCommand.execute()
.    Known null at CoordWfActionInfoXCommand.java:[line 74]
{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:green}+1 TESTS{color}
.    Tests run: 1894
{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/3699/

> More directly view of the coordinator’s history from perspective of workflow action.
> ------------------------------------------------------------------------------------
>
>                 Key: OOZIE-2827
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2827
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Alonzo Zhou
>         Attachments: OOZIE-2827-0001.patch
>
>
> Background: 
> When we monitor a coordinator job, statistics of historical workflow instances such as running time can be directly visualized.
> But, we lack the ability to monitor historical statistics of coordinator from perspective of  workflow action.For example, running time of a coordinator action is longer than before, but we can't see the exact change tendency of a sepcific workflow action in it。
> Functional optimization: 
> More detailed view of the coordinator’s history can be observed from perspective of  workflow action.Furthermore,  the trend of a workflow action can be shown directly on front-end graph.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)