[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (93 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2824  Fix typos in documentation
https://issues.apache.org/jira/browse/OOZIE-2824
OOZIE-2820  more spelling errors in exceptions and logging
https://issues.apache.org/jira/browse/OOZIE-2820
OOZIE-2817  Increase test case stability in pre-commit job
https://issues.apache.org/jira/browse/OOZIE-2817
OOZIE-2816  Strip out the first command word from Sqoop action if its "sqoop"
https://issues.apache.org/jira/browse/OOZIE-2816
OOZIE-2813  Remove tabs and trailing whitespaces from oozie-defaul.xml
https://issues.apache.org/jira/browse/OOZIE-2813
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2796  oozie.action.keep.action.dir not getting noticed
https://issues.apache.org/jira/browse/OOZIE-2796
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2785  Master is not compiling with hadoop-1 profile
https://issues.apache.org/jira/browse/OOZIE-2785
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2780  Upgrade hadoop-common version to 2.6.0
https://issues.apache.org/jira/browse/OOZIE-2780
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2769  Extend FS action to allow setrep on a file
https://issues.apache.org/jira/browse/OOZIE-2769
OOZIE-2753  Update Docs for Jetty Tomcat changes
https://issues.apache.org/jira/browse/OOZIE-2753
OOZIE-2751  LocalOozieClient is missing methods from OozieClient
https://issues.apache.org/jira/browse/OOZIE-2751
OOZIE-2746  Several tests failure in TestV2ValidateServlet.java
https://issues.apache.org/jira/browse/OOZIE-2746
OOZIE-2739  Remove property expansion pattern from ShellMain's log4j properties 
content
https://issues.apache.org/jira/browse/OOZIE-2739
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2733  change org.apache.hadoop.fs.permission.AccessControlException to 
org.apache.hadoop.security.AccessControlException
https://issues.apache.org/jira/browse/OOZIE-2733
OOZIE-2726  Flaky test due to daylight saving changes
https://issues.apache.org/jira/browse/OOZIE-2726
OOZIE-2718  Improve -dryrun for bundles
https://issues.apache.org/jira/browse/OOZIE-2718
OOZIE-2713  Provide an option to log out contents of the localized jar files
https://issues.apache.org/jira/browse/OOZIE-2713
OOZIE-2701  Oozie to support Multiple HCatalog URIs
https://issues.apache.org/jira/browse/OOZIE-2701
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693  SimpleHCatDependencyCache.removeMissingDependency can throw NPE
https://issues.apache.org/jira/browse/OOZIE-2693
OOZIE-2692  Oozie job submit doesn't report error message to user if there is 
any issue with job conf
https://issues.apache.org/jira/browse/OOZIE-2692
OOZIE-2684  Bad database schema error for WF_ACTIONS table
https://issues.apache.org/jira/browse/OOZIE-2684
OOZIE-2681  fix javadoc to compile on JDK8 again
https://issues.apache.org/jira/browse/OOZIE-2681
OOZIE-2670  Upgrade Hbase to 1.2
https://issues.apache.org/jira/browse/OOZIE-2670
OOZIE-2668  Status update and recovery problems when coord action and its 
children not in sync
https://issues.apache.org/jira/browse/OOZIE-2668
OOZIE-2662  DB migration fails if DB is too big
https://issues.apache.org/jira/browse/OOZIE-2662
OOZIE-2652  Skip trash while deleting hive table partition
https://issues.apache.org/jira/browse/OOZIE-2652
OOZIE-2650  Retry coord start on database exceptions
https://issues.apache.org/jira/browse/OOZIE-2650
OOZIE-2644  Skip queuing Notification Commands when there's nothing to notify
https://issues.apache.org/jira/browse/OOZIE-2644
OOZIE-2641  rerunning an oozie coordinator job stucks on waiting
https://issues.apache.org/jira/browse/OOZIE-2641
OOZIE-2629  Get OozieShareLibCLI to perform a final rename to destPath when 
creating a Sharelib
https://issues.apache.org/jira/browse/OOZIE-2629
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues.apache.org/jira/browse/OOZIE-2618
OOZIE-260

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (86 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues-test.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues-test.apache.org/jira/browse/OOZIE-2618
OOZIE-2617  Read properties files in action configurations
https://issues-test.apache.org/jira/browse/OOZIE-2617
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues-test.apache.org/jira/browse/OOZIE-2616
OOZIE-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues-test.apache.org/jira/browse/OOZIE-2606
OOZIE-2589  CompletedActionXCommand priority param is of no effect
https://issues-test.apache.org/jira/browse/OOZIE-2589
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues-test.apache.org/jira/browse/OOZIE-2588
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues-test.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues-test.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues-test.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues-test.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues-test.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues-test.apache.org/jira/browse/OOZIE-2572
OOZIE-2571  Add scala.binary.version Maven property so that Scala 2.11 can be 
used
https://issues-test.apache.org/jira/browse/OOZIE-2571
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues-test.apache.org/jira/browse/OOZIE-2569
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues-test.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues-test.apache.org/jira/browse/OOZIE-2564
OOZIE-2552  Update ActiveMQ version for security and other fixes
https://issues-test.apache.org/jira/browse/OOZIE-2552
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues-test.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues-test.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues-test.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues-test.apache.org/jira/browse/OOZIE-2528
OOZIE-2521  Filter options are case sensitive for jobtye=bundle
https://issues-test.apache.org/jira/browse/OOZIE-2521
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues-test.apache.org/jira/browse/OOZIE-2518
OOZIE-2517  Add support for startCreatedTime and endCreatedTime filters for 
coord and bundles
https://issues-test.apache.org/jira/browse/OOZIE-2517
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues-test.apache.org/jira/browse/OOZIE-2513
OOZIE-2512  ShareLibservice returns incorrect path for jar
https://issues-test.apache.org/jira/browse/OOZIE-2512
OOZIE-2508  Documentation change for Coord action rerun [OOZIE-1735]
https://issues-test.apache.org/jira/browse/OOZIE-2508
OOZIE-2501  ZK reentrant lock doesn't work for few cases
https://issues-test.apache.org/jira/browse/OOZIE-2501
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues-test.apache.org/jira/browse/OOZIE-2500
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues-test.apache.org/jira/browse/OOZIE-2499
OOZIE-2498  Oozie CallerId configuration for downstream components 
https://issues-test.apache.org/jira/browse/OOZIE-2498
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues-test.apache.org/jira/browse/OOZIE-2495
OOZIE-2491  oozie acl cannot specify group,it does`t work
https://issues-test.apache.org/jira/browse/OOZIE-2491
OOZIE

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

[Alonzo Zhou (JIRA)]

Alonzo Zhou created OOZIE-2827:
--

 Summary: More directly view of the coordinator’s history from the 
workflow action dimension.
 Key: OOZIE-2827
 URL: https://issues.apache.org/jira/browse/OOZIE-2827
 Project: Oozie
  Issue Type: Improvement
Reporter: Alonzo Zhou


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)

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

[Alonzo Zhou (JIRA)]

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

Alonzo Zhou commented on OOZIE-2827:


web service API:
GET /oozie/v2/job/\{JOB-ID\}

parameter :
show=wf-actions
action-name=\{WF-ACTION-NAME\}
offset=\{OFFSET\}
len=\{LEN\}

> More directly view of the coordinator’s history from the workflow action 
> dimension.
> ---
>
> Key: OOZIE-2827
> URL: https://issues.apache.org/jira/browse/OOZIE-2827
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Alonzo Zhou
>
> 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)

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

[Alonzo Zhou (JIRA)]

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

Alonzo Zhou commented on OOZIE-2827:


Experimental result in real environment：
Request:
GET 
/oozie/v2/job/002-160122140107162-oozie-oozi-C?show=wf-actions&action-name=fs-a747&offset=2&len=2
Response：
HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
{code:none}
{
"coordJobId": "002-160122140107162-oozie-oozi-C", 
"actions": [
{
"errorMessage": null, 
"status": "OK", 
"stats": null, 
"data": null, 
"transition": "End", 
"externalStatus": "OK", 
"cred": "null", 
"conf": "
  
", 
"type": "fs", 
"endTime": "Fri, 22 Jan 2016 06:25:24 GMT", 
"externalId": "-", 
"id": "005-160122140107162-oozie-oozi-W@fs-a747", 
"startTime": "Fri, 22 Jan 2016 06:25:24 GMT", 
"externalChildIDs": null, 
"name": "fs-a747", 
"errorCode": null, 
"trackerUri": "-", 
"retries": 0, 
"toString": "Action name[fs-a747] status[OK]", 
"consoleUrl": "-"
}, 
{
"errorMessage": null, 
"status": "OK", 
"stats": null, 
"data": null, 
"transition": "End", 
"externalStatus": "OK", 
"cred": "null", 
"conf": "
  
", 
"type": "fs", 
"endTime": "Fri, 22 Jan 2016 06:25:25 GMT", 
"externalId": "-", 
"id": "006-160122140107162-oozie-oozi-W@fs-a747", 
"startTime": "Fri, 22 Jan 2016 06:25:25 GMT", 
"externalChildIDs": null, 
"name": "fs-a747", 
"errorCode": null, 
"trackerUri": "-", 
"retries": 0, 
"toString": "Action name[fs-a747] status[OK]", 
"consoleUrl": "-"
}
]
}
{code}

> More directly view of the coordinator’s history from the workflow action 
> dimension.
> ---
>
> Key: OOZIE-2827
> URL: https://issues.apache.org/jira/browse/OOZIE-2827
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Alonzo Zhou
>
> 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)

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

[Alonzo Zhou (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alonzo Zhou updated OOZIE-2827:
---
Summary: More directly view of the coordinator’s history from perspective 
of workflow action.  (was: More directly view of the coordinator’s history from 
the workflow action dimension.)

> 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
>
> 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)

[jira] [Updated] (OOZIE-2816) Strip out the first command word from Sqoop action if its "sqoop"

[Harsh J (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated OOZIE-2816:
---
Attachment: OOZIE-2816.003.patch

Yea I should've done that, my bad. I've unified the logic but a method felt 
overkill for a one-liner so I've left it inline. New patch attached & PR 
force-updated.

> Strip out the first command word from Sqoop action if its "sqoop"
> -
>
> Key: OOZIE-2816
> URL: https://issues.apache.org/jira/browse/OOZIE-2816
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Attachments: OOZIE-2816.000.patch, OOZIE-2816.001.patch, 
> OOZIE-2816.002.patch, OOZIE-2816.003.patch
>
>
> A [sorta 
> popular|https://www.google.com/search?q=%22No+such+sqoop+tool:+sqoop%22+oozie&*]
>  user error is to specify the command part of the sqoop action in the style 
> of the CLI: "sqoop import …" instead of just the required "import …". This 
> causes the Sqoop action to predictably fail with:
> {code}
> No such sqoop tool: sqoop. See 'sqoop help'.
> Intercepting System.exit(1)
> {code}
> A simple enhancement can prevent this burden on user. We can skip the first 
> command token if its "sqoop".



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

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

[Alonzo Zhou (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alonzo Zhou updated OOZIE-2827:
---
Attachment: OOZIE-2827-0001.patch

> 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)

[jira] [Created] (OOZIE-2828) Query tag is not functional for Hive2 action node in oozie

[Supreeth Sharma (JIRA)]

Supreeth Sharma created OOZIE-2828:
--

 Summary: Query tag is not functional for Hive2 action node in oozie
 Key: OOZIE-2828
 URL: https://issues.apache.org/jira/browse/OOZIE-2828
 Project: Oozie
  Issue Type: Bug
  Components: action
Reporter: Supreeth Sharma
Priority: Critical


'query' tag is not functional for Hive2 action node in oozie.Workflow is 
intended to create a hive table using Hive2 action node. Though workflow run 
successfully, table is not created.
Below is my workflow :
{code}




${resourceManager}
${nameNode}

jdbc:hive2://oozie-repro-2.openstacklocal:2181,oozie-repro-1.openstacklocal:2181,oozie-repro-3.openstacklocal:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2
create table test(col1 int)





${wf:errorMessage(wf:lastErrorNode())}



{code}


Same workflow I modified the Hive2 node to use  'script' tag and table got 
created successfully.



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

Jenkins build is back to normal : oozie-trunk-precommit-build #3698

[Apache Jenkins Server]

See 

[jira] [Commented] (OOZIE-2816) Strip out the first command word from Sqoop action if its "sqoop"

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2816:
--

Testing JIRA OOZIE-2816

Cleaning local git 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 1 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [core].
.{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 [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 [sharelib/hcatalog].
{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: 1896
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3698/

> Strip out the first command word from Sqoop action if its "sqoop"
> -
>
> Key: OOZIE-2816
> URL: https://issues.apache.org/jira/browse/OOZIE-2816
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Attachments: OOZIE-2816.000.patch, OOZIE-2816.001.patch, 
> OOZIE-2816.002.patch, OOZIE-2816.003.patch
>
>
> A [sorta 
> popular|https://www.google.com/search?q=%22No+such+sqoop+tool:+sqoop%22+oozie&*]
>  user error is to specify the command part of the sqoop action in the style 
> of the CLI: "sqoop import …" instead of just the required "import …". This 
> causes the Sqoop action to predictably fail with:
> {code}
> No such sqoop tool: sqoop. See 'sqoop help'.
> Intercepting System.exit(1)
> {code}
> A simple enhancement can prevent this burden on user. We can skip the first 
> command token if its "sqoop".



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

Build failed in Jenkins: oozie-trunk-precommit-build #3699

[Apache Jenkins Server]

See 


--
[...truncated 1.33 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/ForkNodeDef.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/LiteWorkflowLib.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/NodeDef.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/KillNodeDef.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/ControlNodeHandler.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/ActionNodeDef.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/StartNodeDef.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/DecisionNodeHandler.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/DBLiteWorkflowLib.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/EndNodeDef.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/KillNodeDef.KillNodeHandler.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/LiteWorkflowApp.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/LiteWorkflowValidator.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/NodeHandler.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/NodeHandler.Context.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/LiteWorkflowInstance.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/lite/JoinNodeDef.JoinNodeHandler.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/WorkflowInstance.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/workflow/WorkflowApp.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/DefaultConnectionContext.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/JMSExceptionListener.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/ConnectionContext.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/JMSJobEventListener.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/MessageReceiver.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/JMSSLAEventListener.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/JMSConnectionInfo.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/Message

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

[Hadoop QA (JIRA)]

[ 
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)

[jira] [Commented] (OOZIE-2816) Strip out the first command word from Sqoop action if its "sqoop"

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2816:
---

+1 (non-binding) for the patch. Thank you for the contribution [~qwertymaniac]!

> Strip out the first command word from Sqoop action if its "sqoop"
> -
>
> Key: OOZIE-2816
> URL: https://issues.apache.org/jira/browse/OOZIE-2816
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Attachments: OOZIE-2816.000.patch, OOZIE-2816.001.patch, 
> OOZIE-2816.002.patch, OOZIE-2816.003.patch
>
>
> A [sorta 
> popular|https://www.google.com/search?q=%22No+such+sqoop+tool:+sqoop%22+oozie&*]
>  user error is to specify the command part of the sqoop action in the style 
> of the CLI: "sqoop import …" instead of just the required "import …". This 
> causes the Sqoop action to predictably fail with:
> {code}
> No such sqoop tool: sqoop. See 'sqoop help'.
> Intercepting System.exit(1)
> {code}
> A simple enhancement can prevent this burden on user. We can skip the first 
> command token if its "sqoop".



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

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

[Alonzo Zhou (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alonzo Zhou updated OOZIE-2827:
---
Attachment: OOZIE-2827-0002.patch

> 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, OOZIE-2827-0002.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)

[jira] [Created] (OOZIE-2829) Improve sharelib upload to accept multiple source folders

[Peter Cseh (JIRA)]

Peter Cseh created OOZIE-2829:
-

 Summary: Improve sharelib upload to accept multiple source folders
 Key: OOZIE-2829
 URL: https://issues.apache.org/jira/browse/OOZIE-2829
 Project: Oozie
  Issue Type: Bug
  Components: tools
Reporter: Peter Cseh


Right now sharelib can be created via {{sharelib create -fs FS_URI -locallib 
SHARED_LIBRARY}} where the SHARED_LIBRARY can be a tarbal or a folder. 

It would be nice to have the possibility to define additional folders to be 
uploaded into the sharelib, so the users don't have to copy or link the files 
together on their machine.

The syntax could be something like -additional-lib 
sharelibName=/path/to/source/;/path/to/some/file,sharelibName2=/path/to/some/folder



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

Build failed in Jenkins: oozie-trunk-precommit-build #3700

[Apache Jenkins Server]

See 


--
[...truncated 1.33 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/StatusTransitXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/PreconditionException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/PauseTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/LocalOozieClient.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/test/EmbeddedServletContainer.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/decision/DecisionActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.ErrorType.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ssh/SshActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.RETRYPOLICY.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.JavaMailAuthenticator.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ControlNodeActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ForkActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/EndActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/StartActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/JoinActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/KillActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/SqoopActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/Hive2Credentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HCatCredentialHelper.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/LauncherMapperHelper.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/Credentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/ShellActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/ScriptLanguageActionExecutor.html
 longer than 100 c

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

[Hadoop QA (JIRA)]

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

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: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 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [core].
.{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 [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 [sharelib/hcatalog].
{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: 1894
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)

.Tests failing with errors:
.  

{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/3700/

> 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, OOZIE-2827-0002.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)

[jira] [Commented] (OOZIE-2813) Remove tabs and trailing whitespaces from oozie-defaul.xml

[Harsh J (JIRA)]

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

Harsh J commented on OOZIE-2813:


I'm +1 on this. Do we also have a checkstyle rule already that warns on new 
tab-including changes for XML files (to try and prevent future commits from 
recreating this problem)?

> Remove tabs and trailing whitespaces from oozie-defaul.xml
> --
>
> Key: OOZIE-2813
> URL: https://issues.apache.org/jira/browse/OOZIE-2813
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>  Labels: newbie
> Attachments: OOZIE-2813-001.patch
>
>
> oozie-default.xml has a buch of tab characters and trailing whitespaces in it.
> >> [9] 09:41 : oozie (master) :: grep "\t" 
> >> core/src/main/resources/oozie-default.xml |wc -l
>   75
> >> [10] 09:41 : oozie (master) :: grep " $" 
> >> core/src/main/resources/oozie-default.xml |wc -l
>   17
> Trailing whitespaces should be removed, while tabs have to replaced with 
> spaces.



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

[jira] [Commented] (OOZIE-2813) Remove tabs and trailing whitespaces from oozie-defaul.xml

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2813:
---

The 
[raw-patch-analisys|https://github.com/apache/oozie/blob/master/bin/test-patch-05-patch-raw-analysis#L85]
 step in our pre-commit hook checks for tabs and trailing whitespaces in the 
patches. They should be able to catch these in future commits.
Btw, there was no build for this patch from HadoopQA. It shouldn't break 
anything, but I wonder why it's missing. 


> Remove tabs and trailing whitespaces from oozie-defaul.xml
> --
>
> Key: OOZIE-2813
> URL: https://issues.apache.org/jira/browse/OOZIE-2813
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>  Labels: newbie
> Attachments: OOZIE-2813-001.patch
>
>
> oozie-default.xml has a buch of tab characters and trailing whitespaces in it.
> >> [9] 09:41 : oozie (master) :: grep "\t" 
> >> core/src/main/resources/oozie-default.xml |wc -l
>   75
> >> [10] 09:41 : oozie (master) :: grep " $" 
> >> core/src/main/resources/oozie-default.xml |wc -l
>   17
> Trailing whitespaces should be removed, while tabs have to replaced with 
> spaces.



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

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2817:
---

I don't think the pre-commit job finished for the second time either. I'm 
attaching the patch again.


> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



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

[jira] [Updated] (OOZIE-2817) Increase test case stability in pre-commit job

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh updated OOZIE-2817:
--
Attachment: OOZIE-2817-003.patch

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch, 
> OOZIE-2817-003.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



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

Build failed in Jenkins: oozie-trunk-precommit-build #3701

[Apache Jenkins Server]

See 


--
[...truncated 1.33 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordKillXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionSkipXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/TransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/IgnoreTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/BulkJobsXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/RerunTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/KillTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/SuspendTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/StatusTransitXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/PreconditionException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/PauseTransitionXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/LocalOozieClient.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/test/EmbeddedServletContainer.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/decision/DecisionActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.ErrorType.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutorException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ssh/SshActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.RETRYPOLICY.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/email/EmailActionExecutor.JavaMailAuthenticator.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ControlNodeActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/ForkActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/EndActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/StartActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/control/JoinActionExecutor.html
 longer than 100 characters.
[WARNING]

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2817:
--

Testing JIRA OOZIE-2817

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 7 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 1 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:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [core].
.{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 [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 [sharelib/hcatalog].
{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: 1892
{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/3701/

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch, 
> OOZIE-2817-003.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



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

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2817:
--

It's hard to verify that this is working correctly, but it seems okay as far as 
I can tell.  I think the best way is to commit it and we can see it working as 
we work on other JIRAs; we can always fix/update it later if need be.

+1

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch, OOZIE-2817-002.patch, 
> OOZIE-2817-003.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



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