[jira] [Created] (OOZIE-2438) Oozie client "jobs -filter" diagnostic message clarification

2016-01-14 Thread Satish Subhashrao Saley (JIRA) 
Satish Subhashrao Saley created OOZIE-2438:
--

 Summary: Oozie client "jobs -filter" diagnostic message 
clarification
 Key: OOZIE-2438
 URL: https://issues.apache.org/jira/browse/OOZIE-2438
 Project: Oozie
  Issue Type: Bug
Reporter: Satish Subhashrao Saley
Assignee: Satish Subhashrao Saley
Priority: Minor


Oozie client "jobs -filter" diagnostic message clarification
$ oozie jobs -filter 'status=RUNNING,user=udb_grid'
Error: E0420 : E0420: Invalid jobs filter [status=RUNNING,user=udb_grid], 
elements must be name=value pairs
The diagnostic wording should be "elements must be semicolon-separated 
name=value pairs".
The documentation might note that because a semicolon is used (in place, say of 
a comma), the entire filter string must be quoted or escaped to prevent the 
shell from stopping at the semicolon.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OOZIE-2246) CoordinatorInputCheckCommand does not behave properly when har file is one of data dependency and doesn't exist

2016-01-14 Thread Satish Subhashrao Saley (JIRA) 

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

Satish Subhashrao Saley reassigned OOZIE-2246:
--

Assignee: Satish Subhashrao Saley  (was: Ryota Egashira)

> CoordinatorInputCheckCommand does not behave properly when har file is one of 
> data dependency and doesn't exist
> ---
>
> Key: OOZIE-2246
> URL: https://issues.apache.org/jira/browse/OOZIE-2246
> Project: Oozie
>  Issue Type: Bug
>Reporter: Ryota Egashira
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2246-v2.patch, OOZIE-2246-v3.patch, 
> OOZIE-2246.patch
>
>
> when har file doesn't exist, FileSystem.createFileSystem in 
> HadoopAccessorService throw exception, failing CoordActionInputCheck.
> thus, even thought there are other data dependencies which already exist, it 
> is not reflected on DB.
> coordinator job cannot start until the har file becomes available anyway, and 
> once available, this error doesn't happen, so basic functionality is fine, 
> but it's misleading.
> {code}
> 2014-03-13 22:00:00,051 WARN CallableQueueService$CallableWrapper:542 
> [pool-2-thread-288] - USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] 
> exception callable [coord_action_input], E1021: Coord Action Input Check 
> Error: org.apache.oozie.service.HadoopAccessorException: E0902: Exception 
> occured: [Invalid path for the Har Filesystem. No index file in 
> har://:8020/data/2014031322/archive.har]
> org.apache.oozie.command.CommandException: E1021: Coord Action Input Check 
> Error: org.apache.oozie.service.HadoopAccessorException: E0902: Exception 
> occured: [Invalid path for the Har Filesystem. No index file in 
> har://:8020/data/2014031322/archive.har]
> at 
> org.apache.oozie.command.coord.CoordActionInputCheckXCommand.execute(CoordActionInputCheckXCommand.java:182)
> at 
> org.apache.oozie.command.coord.CoordActionInputCheckXCommand.execute(CoordActionInputCheckXCommand.java:67)
> at org.apache.oozie.command.XCommand.call(XCommand.java:280)
> at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.io.IOException: 
> org.apache.oozie.service.HadoopAccessorException: E0902: Exception occured: 
> [Invalid path for the Har Filesystem. No index file in 
> har://:8020/data/2014031322/archive.har]
> at 
> org.apache.oozie.command.coord.CoordActionInputCheckXCommand.pathExists(CoordActionInputCheckXCommand.java:493)
> at 
> org.apache.oozie.command.coord.CoordActionInputCheckXCommand.checkListOfPaths(CoordActionInputCheckXCommand.java:459)
> at 
> org.apache.oozie.command.coord.CoordActionInputCheckXCommand.checkResolvedUris(CoordActionInputCheckXCommand.java:429)
> at 
> org.apache.oozie.command.coord.CoordActionInputCheckXCommand.checkInput(CoordActionInputCheckXCommand.java:259)
> at 
> org.apache.oozie.command.coord.CoordActionInputCheckXCommand.execute(CoordActionInputCheckXCommand.java:132)
> ... 6 more
> Caused by: org.apache.oozie.service.HadoopAccessorException: E0902: Exception 
> occured: [Invalid path for the Har Filesystem. No index file in 
> har://:8020/data/2014031322/archive.har]
> at 
> org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorService.java:430)
> at 
> org.apache.oozie.dependency.FSURIHandler.getFileSystem(FSURIHandler.java:134)
> at org.apache.oozie.dependency.FSURIHandler.exists(FSURIHandler.java:99)
> at 
> org.apache.oozie.command.coord.CoordActionInputCheckXCommand.pathExists(CoordActionInputCheckXCommand.java:488)
> ... 10 more
> Caused by: java.io.IOException: Invalid path for the Har Filesystem. No index 
> file in har://:8020/data/2014031322/archive.har
> at org.apache.hadoop.fs.HarFileSystem.initialize(HarFileSystem.java:139)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2160)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:303)
> at 
> org.apache.oozie.service.HadoopAccessorService$2.run(HadoopAccessorService.java:422)
> at 
> org.apache.oozie.service.HadoopAccessorService$2.run(HadoopAccessorService.java:420)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1284)
> at 
> org.apache.oozie.service.HadoopAccessorService.createFileSystem(HadoopAccessorService.java:420)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2435) TestCoordChangeXCommand is flakey

2016-01-14 Thread Ferenc Denes (JIRA) 

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

Ferenc Denes commented on OOZIE-2435:
-

Thanks Robert, added the new patch.

> TestCoordChangeXCommand is flakey
> -
>
> Key: OOZIE-2435
> URL: https://issues.apache.org/jira/browse/OOZIE-2435
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Affects Versions: trunk
>Reporter: Ferenc Denes
>Assignee: Ferenc Denes
>  Labels: test
> Fix For: trunk
>
> Attachments: OOZIE-2435-1.patch, OOZIE-2435-2.patch
>
>
> TestCoordChangeXCommand's subtests fail time to time in our test harness, and 
> also in apache jenkins.
> The issue is, that the CallableQueueService modifies some actions, while we 
> are observing the behaviour.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2435) TestCoordChangeXCommand is flakey

2016-01-14 Thread Ferenc Denes (JIRA) 

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

Ferenc Denes updated OOZIE-2435:

Attachment: OOZIE-2435-2.patch

> TestCoordChangeXCommand is flakey
> -
>
> Key: OOZIE-2435
> URL: https://issues.apache.org/jira/browse/OOZIE-2435
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Affects Versions: trunk
>Reporter: Ferenc Denes
>Assignee: Ferenc Denes
>  Labels: test
> Fix For: trunk
>
> Attachments: OOZIE-2435-1.patch, OOZIE-2435-2.patch
>
>
> TestCoordChangeXCommand's subtests fail time to time in our test harness, and 
> also in apache jenkins.
> The issue is, that the CallableQueueService modifies some actions, while we 
> are observing the behaviour.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2433) oozie restart required if oozie metrics to graphing tool broken

2016-01-14 Thread Narayan Periwal (JIRA) 

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

Narayan Periwal updated OOZIE-2433:
---
Attachment: OOZIE-2433.patch

> oozie restart required if oozie metrics to graphing tool broken
> ---
>
> Key: OOZIE-2433
> URL: https://issues.apache.org/jira/browse/OOZIE-2433
> Project: Oozie
>  Issue Type: Bug
>Reporter: Sanjeev T
>Assignee: Narayan Periwal
> Attachments: OOZIE-2433.patch
>
>
> When we start oozie service it starts emitting oozie metrics,  expose to the 
> host
> * oozie.external_monitoring.address
> If we have issue on the external host or service disruption for a while, the 
> metrics are not exposed, it requires oozie restart
> * Can we avoid oozie restart, let oozie do health check and expose metrics
> * Enable logging for the oozie metrics emitting to external host



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2435) TestCoordChangeXCommand is flakey

2016-01-14 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2435:
--

Testing JIRA OOZIE-2435

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 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: 1704
.Tests failed: 4
.Tests errors: 0

.The patch failed the following testcases:

.  testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
.  testPurgeXCommandFailed(org.apache.oozie.command.TestPurgeXCommand)
.  testPurgeWFWithSubWF1(org.apache.oozie.command.TestPurgeXCommand)
.  testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)

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

> TestCoordChangeXCommand is flakey
> -
>
> Key: OOZIE-2435
> URL: https://issues.apache.org/jira/browse/OOZIE-2435
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Affects Versions: trunk
>Reporter: Ferenc Denes
>Assignee: Ferenc Denes
>  Labels: test
> Fix For: trunk
>
> Attachments: OOZIE-2435-1.patch, OOZIE-2435-2.patch
>
>
> TestCoordChangeXCommand's subtests fail time to time in our test harness, and 
> also in apache jenkins.
> The issue is, that the CallableQueueService modifies some actions, while we 
> are observing the behaviour.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OOZIE-2433) oozie restart required if oozie metrics to graphing tool broken

2016-01-14 Thread Narayan Periwal (JIRA) 

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

Narayan Periwal reassigned OOZIE-2433:
--

Assignee: Narayan Periwal

> oozie restart required if oozie metrics to graphing tool broken
> ---
>
> Key: OOZIE-2433
> URL: https://issues.apache.org/jira/browse/OOZIE-2433
> Project: Oozie
>  Issue Type: Bug
>Reporter: Sanjeev T
>Assignee: Narayan Periwal
>
> When we start oozie service it starts emitting oozie metrics,  expose to the 
> host
> * oozie.external_monitoring.address
> If we have issue on the external host or service disruption for a while, the 
> metrics are not exposed, it requires oozie restart
> * Can we avoid oozie restart, let oozie do health check and expose metrics
> * Enable logging for the oozie metrics emitting to external host



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2433) oozie restart required if oozie metrics to graphing tool broken

2016-01-14 Thread Narayan Periwal (JIRA) 

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

Narayan Periwal commented on OOZIE-2433:


The issue is because of not having the latest version of the dropwizard metrics 
dependency.
I verified that after upgrading it to 3.1.2, the above issue get resolved.

> oozie restart required if oozie metrics to graphing tool broken
> ---
>
> Key: OOZIE-2433
> URL: https://issues.apache.org/jira/browse/OOZIE-2433
> Project: Oozie
>  Issue Type: Bug
>Reporter: Sanjeev T
>Assignee: Narayan Periwal
>
> When we start oozie service it starts emitting oozie metrics,  expose to the 
> host
> * oozie.external_monitoring.address
> If we have issue on the external host or service disruption for a while, the 
> metrics are not exposed, it requires oozie restart
> * Can we avoid oozie restart, let oozie do health check and expose metrics
> * Enable logging for the oozie metrics emitting to external host



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-01-14 Thread Apache Jenkins Server 
See 

Changes:

[rkanter] OOZIE-2437 Exclude additional Hadoop dependencies from Spark Sharelib

[rkanter] OOZIE-2428 TestSLAService, TestSLAEventGeneration flakey tests (fdenes

--
[...truncated 8420 lines...]
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor

[jira] [Commented] (OOZIE-2433) oozie restart required if oozie metrics to graphing tool broken

2016-01-14 Thread Jaydeep Vishwakarma (JIRA) 

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

Jaydeep Vishwakarma commented on OOZIE-2433:


Verified it , It was the issue in 3.1.0 version. With 3.1.2  it is working 
fine. 
more detail can be find in :
https://github.com/dropwizard/metrics/issues/669
https://github.com/dropwizard/metrics/issues/814

+1


> oozie restart required if oozie metrics to graphing tool broken
> ---
>
> Key: OOZIE-2433
> URL: https://issues.apache.org/jira/browse/OOZIE-2433
> Project: Oozie
>  Issue Type: Bug
>Reporter: Sanjeev T
>Assignee: Narayan Periwal
> Attachments: OOZIE-2433.patch
>
>
> When we start oozie service it starts emitting oozie metrics,  expose to the 
> host
> * oozie.external_monitoring.address
> If we have issue on the external host or service disruption for a while, the 
> metrics are not exposed, it requires oozie restart
> * Can we avoid oozie restart, let oozie do health check and expose metrics
> * Enable logging for the oozie metrics emitting to external host



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2439) FS Action no longer uses name-node

2016-01-14 Thread Robert Kanter (JIRA) 

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

Robert Kanter updated OOZIE-2439:
-
Description: 
As reported by [~olch...@gmail.com] in [this 
comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
 of OOZIE-2187, the FS Action no longer uses the {{}} in either the 
global section or the default NN in oozie-site.  

This is a regression.

  was:
As reported by [~olch...@gmail.com] in [this 
comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
 of OOZIE-2187, the FS Action no longer uses the {{}} in either the 
action itself, the global section, or the default NN in oozie-site.  

This is a regression.


> FS Action no longer uses name-node
> --
>
> Key: OOZIE-2439
> URL: https://issues.apache.org/jira/browse/OOZIE-2439
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: trunk
>
> Attachments: OOZIE-2439.001.patch
>
>
> As reported by [~olch...@gmail.com] in [this 
> comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
>  of OOZIE-2187, the FS Action no longer uses the {{}} in either 
> the global section or the default NN in oozie-site.  
> This is a regression.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2439) FS Action no longer uses name-node from global section or default NN

2016-01-14 Thread Robert Kanter (JIRA) 

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

Robert Kanter updated OOZIE-2439:
-
Summary: FS Action no longer uses name-node from global section or default 
NN  (was: FS Action no longer uses name-node)

> FS Action no longer uses name-node from global section or default NN
> 
>
> Key: OOZIE-2439
> URL: https://issues.apache.org/jira/browse/OOZIE-2439
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: trunk
>
> Attachments: OOZIE-2439.001.patch
>
>
> As reported by [~olch...@gmail.com] in [this 
> comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
>  of OOZIE-2187, the FS Action no longer uses the {{}} in either 
> the global section or the default NN in oozie-site.  
> This is a regression.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 42335: OOZIE-2439: FS Action no longer uses name-node from global section or default NN

2016-01-14 Thread Robert Kanter 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42335/
---

(Updated Jan. 15, 2016, 2:17 a.m.)


Review request for oozie.


Summary (updated)
-

OOZIE-2439: FS Action no longer uses name-node from global section or default NN


Bugs: OOZIE-2439
https://issues.apache.org/jira/browse/OOZIE-2439


Repository: oozie-git


Description
---

https://issues.apache.org/jira/browse/OOZIE-2439


Diffs
-

  core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java 
b8649ac 
  core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java 
03c84f1 
  
core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
 1fc1736 
  core/src/test/resources/wf-schema-fs-no-namenode-global.xml PRE-CREATION 
  core/src/test/resources/wf-schema-fs-no-namenode.xml PRE-CREATION 

Diff: https://reviews.apache.org/r/42335/diff/


Testing
---


Thanks,

Robert Kanter

[jira] [Updated] (OOZIE-2439) FS Action no longer uses name-node

2016-01-14 Thread Robert Kanter (JIRA) 

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

Robert Kanter updated OOZIE-2439:
-
Attachment: OOZIE-2439.001.patch

The patch restores the original behavior by modifying the if statements in 
{{LiteWorkflowAppParser}} and comments explaining what's happening in that part 
of the code.  It also adds some unit tests.

> FS Action no longer uses name-node
> --
>
> Key: OOZIE-2439
> URL: https://issues.apache.org/jira/browse/OOZIE-2439
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: trunk
>
> Attachments: OOZIE-2439.001.patch
>
>
> As reported by [~olch...@gmail.com] in [this 
> comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
>  of OOZIE-2187, the FS Action no longer uses the {{}} in either 
> the action itself, the global section, or the default NN in oozie-site.  
> This is a regression.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2436) Fork/join workflow fails with "oozie.action.yarn.tag must not be null"

2016-01-14 Thread abhishek bafna (JIRA) 

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

abhishek bafna commented on OOZIE-2436:
---

Can you add more information about the issue?

> Fork/join workflow fails with "oozie.action.yarn.tag must not be null"
> --
>
> Key: OOZIE-2436
> URL: https://issues.apache.org/jira/browse/OOZIE-2436
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2439) FS Action no longer uses name-node from global section or default NN

2016-01-14 Thread Rohini Palaniswamy (JIRA) 

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

Rohini Palaniswamy commented on OOZIE-2439:
---

+1 Pending jenkins

> FS Action no longer uses name-node from global section or default NN
> 
>
> Key: OOZIE-2439
> URL: https://issues.apache.org/jira/browse/OOZIE-2439
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: trunk
>
> Attachments: OOZIE-2439.001.patch
>
>
> As reported by [~olch...@gmail.com] in [this 
> comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
>  of OOZIE-2187, the FS Action no longer uses the {{}} in either 
> the global section or the default NN in oozie-site.  
> This is a regression.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 42335: OOZIE-2439: FS Action no longer uses name-node from global section or default NN

2016-01-14 Thread Rohini Palaniswamy 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42335/#review114642
---

Ship it!


Ship It!

- Rohini Palaniswamy


On Jan. 15, 2016, 2:17 a.m., Robert Kanter wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42335/
> ---
> 
> (Updated Jan. 15, 2016, 2:17 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2439
> https://issues.apache.org/jira/browse/OOZIE-2439
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2439
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java 
> b8649ac 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java 
> 03c84f1 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  1fc1736 
>   core/src/test/resources/wf-schema-fs-no-namenode-global.xml PRE-CREATION 
>   core/src/test/resources/wf-schema-fs-no-namenode.xml PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/42335/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Robert Kanter
> 
>

Review Request 42335: OOZIE-2439: FS Action no longer uses name-node

2016-01-14 Thread Robert Kanter 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42335/
---

Review request for oozie.


Bugs: OOZIE-2439
https://issues.apache.org/jira/browse/OOZIE-2439


Repository: oozie-git


Description
---

https://issues.apache.org/jira/browse/OOZIE-2439


Diffs
-

  core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java 
b8649ac 
  core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java 
03c84f1 
  
core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
 1fc1736 
  core/src/test/resources/wf-schema-fs-no-namenode-global.xml PRE-CREATION 
  core/src/test/resources/wf-schema-fs-no-namenode.xml PRE-CREATION 

Diff: https://reviews.apache.org/r/42335/diff/


Testing
---


Thanks,

Robert Kanter

[jira] [Commented] (OOZIE-2439) FS Action no longer uses name-node

2016-01-14 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-2439:
--

The tricky thing here is that we can't make {{FsActionExecutor}} set  
{{requiresNameNodeJobTracker()}} to {{true}} because
# the NN is actually optional for the FS Action (as long as you specify it for 
each path)
# The JT isn't even optional (the XSD doesn't allow it)

So we can't simply set it to {{true}} or it would have other side effects.  I 
don't think we should change the semantics of {{requiresNameNodeJobTracker()}} 
at this point either.  We'll have to do something custom, similar to what was 
done in OOZIE-2030 for the SubWorkflow Action.

> FS Action no longer uses name-node
> --
>
> Key: OOZIE-2439
> URL: https://issues.apache.org/jira/browse/OOZIE-2439
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: trunk
>
>
> As reported by [~olch...@gmail.com] in [this 
> comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
>  of OOZIE-2187, the FS Action no longer uses the {{}} in either 
> the action itself, the global section, or the default NN in oozie-site.  
> This is a regression.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OOZIE-2439) FS Action no longer uses name-node

2016-01-14 Thread Robert Kanter (JIRA) 
Robert Kanter created OOZIE-2439:


 Summary: FS Action no longer uses name-node
 Key: OOZIE-2439
 URL: https://issues.apache.org/jira/browse/OOZIE-2439
 Project: Oozie
  Issue Type: Bug
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
Priority: Blocker
 Fix For: trunk


As reported by [~olch...@gmail.com] in [this 
comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
 of OOZIE-2187, the FS Action no longer uses the {{}} in either the 
action itself, the global section, or the default NN in oozie-site.  

This is a regression.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2438) Oozie client "jobs -filter" diagnostic message clarification

2016-01-14 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2438:
--

Testing JIRA OOZIE-2438

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: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 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: 1704
.Tests failed: 6
.Tests errors: 0

.The patch failed the following testcases:

.  testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)
.  
testBundleStatusCoordSubmitFails(org.apache.oozie.service.TestStatusTransitService)
.  
testbulkWfKillSuccess(org.apache.oozie.command.wf.TestBulkWorkflowXCommand)
.  testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
.  testPurgeWFWithSubWF1(org.apache.oozie.command.TestPurgeXCommand)
.  testPurgeXCommandFailed(org.apache.oozie.command.TestPurgeXCommand)

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

> Oozie client "jobs -filter" diagnostic message clarification
> 
>
> Key: OOZIE-2438
> URL: https://issues.apache.org/jira/browse/OOZIE-2438
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2438-1.patch
>
>
> Oozie client "jobs -filter" diagnostic message clarification
> $ oozie jobs -filter 'status=RUNNING,user=udb_grid'
> Error: E0420 : E0420: Invalid jobs filter [status=RUNNING,user=udb_grid], 
> elements must be name=value pairs
> The diagnostic wording should be "elements must be semicolon-separated 
> name=value pairs".
> The documentation might note that because a semicolon is used (in place, say 
> of a comma), the entire filter string must be quoted or escaped to prevent 
> the shell from stopping at the semicolon.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2187) Add a way to specify a default JT/RM and NN

2016-01-14 Thread Jeffrey Olchovy (JIRA) 

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

Jeffrey Olchovy commented on OOZIE-2187:


>> The global section parsing code used to add the , , 
>> , and  from  to every action, even if they 
>> didn't want it (e.g. email action). While not necessarily harmful, this 
>> could be problematic in the future and results in larger database usage. It 
>> now only adds a  and  if 
>> requiresNameNodeJobTracker() is true and only adds a  and 
>>  if a new supportsConfigurationJobXML() is true.

This caused a regression when we upgraded our cluster from CDH 5.4.x to CDH 
5.5.x. The {{fs}} action does not require NN/JT yet the documentation states 
that:
"As of schema 0.4, if a name-node element is specified, then it is not 
necessary for any of the paths to start with the file system URI as it is taken 
from the name-node element. This is also true if the name-node is specified in 
the global section (see Global Configurations)"

We were relying on global configuration to infer the scheme for paths that we 
were passed to the {{fs}} action. After the upgrade, the global configuration 
is no longer applicable to the {{fs}} action resulting in errors such as the 
following:
{noformat}
FS001: Missing scheme in path 
[/com/tapad/devicegraph/v4/graphs/2016/01/08/device-graph]
{noformat}

> Add a way to specify a default JT/RM and NN
> ---
>
> Key: OOZIE-2187
> URL: https://issues.apache.org/jira/browse/OOZIE-2187
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: trunk
>
> Attachments: OOZIE-2187.002.patch, OOZIE-2187.003.patch, 
> OOZIE-2187.patch, OOZIE-2187.patch, OOZIE-2187.patch, OOZIE-2187.patch
>
>
> Oozie is cluster agnostic, which is why we require an RM/JT and NN per action 
> in your workflow (or once via the  section).  In practice, many users 
> use one Oozie server per cluster, so it's an extra burden for them to have to 
> specify this all the time.  It would be convenient if we added configuration 
> properties to oozie-site that would let you specify a default RM/JT and NN to 
> use.  
> This way, these users could completely omit the {{}} and 
> {{}} fields from their workflows; as an added benefit, they can 
> easily update these values if they ever rename/move their RM/JT or NN.  We'd 
> of course still allow specifying  {{}} and {{}} in 
> each action and {{}} to allow individual workflows or actions to 
> override the default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-01-14 Thread Apache Jenkins Server 
See 

Changes:

[rkanter] OOZIE-2435 TestCoordChangeXCommand is flakey (fdenes via rkanter)

--
[...truncated 8446 lines...]
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:

[jira] [Updated] (OOZIE-2438) Oozie client "jobs -filter" diagnostic message clarification

2016-01-14 Thread Satish Subhashrao Saley (JIRA) 

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

Satish Subhashrao Saley updated OOZIE-2438:
---
Attachment: OOZIE-2438-1.patch

> Oozie client "jobs -filter" diagnostic message clarification
> 
>
> Key: OOZIE-2438
> URL: https://issues.apache.org/jira/browse/OOZIE-2438
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2438-1.patch
>
>
> Oozie client "jobs -filter" diagnostic message clarification
> $ oozie jobs -filter 'status=RUNNING,user=udb_grid'
> Error: E0420 : E0420: Invalid jobs filter [status=RUNNING,user=udb_grid], 
> elements must be name=value pairs
> The diagnostic wording should be "elements must be semicolon-separated 
> name=value pairs".
> The documentation might note that because a semicolon is used (in place, say 
> of a comma), the entire filter string must be quoted or escaped to prevent 
> the shell from stopping at the semicolon.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2439) FS Action no longer uses name-node from global section or default NN

2016-01-14 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2439:
--

Testing JIRA OOZIE-2439

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 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: 1707
.Tests failed: 6
.Tests errors: 0

.The patch failed the following testcases:

.  
testBundleRerunInPausedWithError(org.apache.oozie.command.bundle.TestBundleRerunXCommand)
.  testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)
.  testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
.  
testCoordStatus_Failed(org.apache.oozie.command.coord.TestCoordChangeXCommand)
.  testPurgeWFWithSubWF1(org.apache.oozie.command.TestPurgeXCommand)
.  testPurgeXCommandFailed(org.apache.oozie.command.TestPurgeXCommand)

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

> FS Action no longer uses name-node from global section or default NN
> 
>
> Key: OOZIE-2439
> URL: https://issues.apache.org/jira/browse/OOZIE-2439
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: trunk
>
> Attachments: OOZIE-2439.001.patch
>
>
> As reported by [~olch...@gmail.com] in [this 
> comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135]
>  of OOZIE-2187, the FS Action no longer uses the {{}} in either 
> the global section or the default NN in oozie-site.  
> This is a regression.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] Subscription: Oozie Patch Available

2016-01-14 Thread jira 
Issue Subscription
Filter: Oozie Patch Available (65 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2439  FS Action no longer uses name-node from global section or default NN
https://issues.apache.org/jira/browse/OOZIE-2439
OOZIE-2438  Oozie client "jobs -filter" diagnostic message clarification
https://issues.apache.org/jira/browse/OOZIE-2438
OOZIE-2434  inconsistent coord action status and workflow job status
https://issues.apache.org/jira/browse/OOZIE-2434
OOZIE-2433  oozie restart required if oozie metrics to graphing tool broken
https://issues.apache.org/jira/browse/OOZIE-2433
OOZIE-2432  TestPurgeXCommand fails
https://issues.apache.org/jira/browse/OOZIE-2432
OOZIE-2431  Support hive.metastore.uris as alias for hcat.metastore.uri
https://issues.apache.org/jira/browse/OOZIE-2431
OOZIE-2430  Add root logger for hive,sqoop action
https://issues.apache.org/jira/browse/OOZIE-2430
OOZIE-2429  TestEventGeneration test is flakey
https://issues.apache.org/jira/browse/OOZIE-2429
OOZIE-2427  With Kerberos enabled, the authentication failure for the 
javascript resources under /ext-2.2 
https://issues.apache.org/jira/browse/OOZIE-2427
OOZIE-2409  hive2 action with hive 1.2.1 failed
https://issues.apache.org/jira/browse/OOZIE-2409
OOZIE-2400  Workflow xml configuration parser cannot deal with namespace prefix
https://issues.apache.org/jira/browse/OOZIE-2400
OOZIE-2396  oozie compile with hadoop 2.7.1 failed
https://issues.apache.org/jira/browse/OOZIE-2396
OOZIE-2394  Oozie can execute command without holding lock
https://issues.apache.org/jira/browse/OOZIE-2394
OOZIE-2390  Rerun with failed option removing completed output data
https://issues.apache.org/jira/browse/OOZIE-2390
OOZIE-2362  SQL injection in BulkJPAExecutor
https://issues.apache.org/jira/browse/OOZIE-2362
OOZIE-2349  Method getCoordJobInfo(String jobId, String filter, int offset, int 
length, boolean desc) is not present in LocalOozieClientCoord
https://issues.apache.org/jira/browse/OOZIE-2349
OOZIE-2338  Invalid configuration defined reported for some valid configs
https://issues.apache.org/jira/browse/OOZIE-2338
OOZIE-2312  oozie doesn't purge audit and error log
https://issues.apache.org/jira/browse/OOZIE-2312
OOZIE-2273  MiniOozie does not work outside of Oozie
https://issues.apache.org/jira/browse/OOZIE-2273
OOZIE-2259  Create a callback action 
https://issues.apache.org/jira/browse/OOZIE-2259
OOZIE-2258  Introducing a new counter in the instrumentation log to distinguish 
between the reasons for launcher failure
https://issues.apache.org/jira/browse/OOZIE-2258
OOZIE-2253  Spark Job is failing when it is running in standalone server
https://issues.apache.org/jira/browse/OOZIE-2253
OOZIE-2244  Oozie should mask passwords in the logs when logging command 
arguments
https://issues.apache.org/jira/browse/OOZIE-2244
OOZIE-2243  Kill Command does not kill the child job for java action
https://issues.apache.org/jira/browse/OOZIE-2243
OOZIE-2203  Fix the login example
https://issues.apache.org/jira/browse/OOZIE-2203
OOZIE-2196  Create Local Client for Bundle
https://issues.apache.org/jira/browse/OOZIE-2196
OOZIE-2172  ZooKeeper Security Tests failed with JVM IBM JAVA
https://issues.apache.org/jira/browse/OOZIE-2172
OOZIE-2165  Job log fetching can fail in Oozie HA mode when using doAs 
impersonation
https://issues.apache.org/jira/browse/OOZIE-2165
OOZIE-2134  Remove references to Services.get().getConf() in code
https://issues.apache.org/jira/browse/OOZIE-2134
OOZIE-2106  Make tomcat download url configurable in the pom file
https://issues.apache.org/jira/browse/OOZIE-2106
OOZIE-2105  Make version of submodules configurable with parent version 
https://issues.apache.org/jira/browse/OOZIE-2105
OOZIE-2099  Add test-patch support for patches generated without --no-prefix
https://issues.apache.org/jira/browse/OOZIE-2099
OOZIE-2081  WorkflowJob notification to include coordinator action id 
https://issues.apache.org/jira/browse/OOZIE-2081
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
OOZIE-2044  ssh action succeed with a not exists command which should be fail.
https://issues.apache.org/jira/browse/OOZIE-2044
OOZIE-2020  Rerun all Failed/killed/timedout coordinator actions rather than 
specifying action numbers
https://issues.apache.org/jira/browse/OOZIE-2020
OOZIE-1980  Sql error should not fail coord job
https://issues.apache.org/jira/browse/OOZIE-1980
OOZIE-1977  Display patch analysis issues

[jira] [Commented] (OOZIE-2187) Add a way to specify a default JT/RM and NN

2016-01-14 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-2187:
--

You're right.  It looks like we missed that because {{FsActionExecutor}} is one 
of the few that doesn't inherit from {{JavaActionExecutor}}, plus it has some 
unique behavior with {{}} and {{}} that none of the 
other action types have.  I've created OOZIE-2439 to fix this.

> Add a way to specify a default JT/RM and NN
> ---
>
> Key: OOZIE-2187
> URL: https://issues.apache.org/jira/browse/OOZIE-2187
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: trunk
>
> Attachments: OOZIE-2187.002.patch, OOZIE-2187.003.patch, 
> OOZIE-2187.patch, OOZIE-2187.patch, OOZIE-2187.patch, OOZIE-2187.patch
>
>
> Oozie is cluster agnostic, which is why we require an RM/JT and NN per action 
> in your workflow (or once via the  section).  In practice, many users 
> use one Oozie server per cluster, so it's an extra burden for them to have to 
> specify this all the time.  It would be convenient if we added configuration 
> properties to oozie-site that would let you specify a default RM/JT and NN to 
> use.  
> This way, these users could completely omit the {{}} and 
> {{}} fields from their workflows; as an added benefit, they can 
> easily update these values if they ever rename/move their RM/JT or NN.  We'd 
> of course still allow specifying  {{}} and {{}} in 
> each action and {{}} to allow individual workflows or actions to 
> override the default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2435) TestCoordChangeXCommand is flakey

2016-01-14 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-2435:
--

+1

> TestCoordChangeXCommand is flakey
> -
>
> Key: OOZIE-2435
> URL: https://issues.apache.org/jira/browse/OOZIE-2435
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Affects Versions: trunk
>Reporter: Ferenc Denes
>Assignee: Ferenc Denes
>  Labels: test
> Fix For: trunk
>
> Attachments: OOZIE-2435-1.patch, OOZIE-2435-2.patch
>
>
> TestCoordChangeXCommand's subtests fail time to time in our test harness, and 
> also in apache jenkins.
> The issue is, that the CallableQueueService modifies some actions, while we 
> are observing the behaviour.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2433) oozie restart required if oozie metrics to graphing tool broken

2016-01-14 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2433:
--

Testing JIRA OOZIE-2433

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: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 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: 1704
.Tests failed: 4
.Tests errors: 0

.The patch failed the following testcases:

.  testPurgeXCommandFailed(org.apache.oozie.command.TestPurgeXCommand)
.  testPurgeWFWithSubWF1(org.apache.oozie.command.TestPurgeXCommand)
.  testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
.  testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)

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

> oozie restart required if oozie metrics to graphing tool broken
> ---
>
> Key: OOZIE-2433
> URL: https://issues.apache.org/jira/browse/OOZIE-2433
> Project: Oozie
>  Issue Type: Bug
>Reporter: Sanjeev T
>Assignee: Narayan Periwal
> Attachments: OOZIE-2433.patch
>
>
> When we start oozie service it starts emitting oozie metrics,  expose to the 
> host
> * oozie.external_monitoring.address
> If we have issue on the external host or service disruption for a while, the 
> metrics are not exposed, it requires oozie restart
> * Can we avoid oozie restart, let oozie do health check and expose metrics
> * Enable logging for the oozie metrics emitting to external host



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-01-14 Thread Apache Jenkins Server 
See 

--
[...truncated 8442 lines...]
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 

  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz
  [get] To: