[jira] [Commented] (OOZIE-1803) Improvement in Purge service

2014-11-10 Thread Shwetha G S (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14204697#comment-14204697
 ] 

Shwetha G S commented on OOZIE-1803:


+1, will commit with minor changes

 Improvement in Purge service
 

 Key: OOZIE-1803
 URL: https://issues.apache.org/jira/browse/OOZIE-1803
 Project: Oozie
  Issue Type: Improvement
  Components: core
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma
 Attachments: OOZIE-1803-v1.patch, OOZIE-1803-v2.patch, 
 OOZIE-1803-v3.patch, OOZIE-1803-v4.patch, OOZIE-1803-v6.patch, 
 OOZIE-1803.patch, purgeservice-1.patch, purgeservice.patch


 Current purge service of oozie have some performance issues and it might help 
 to look at the queries and indexes to improve the the purge service.



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


[jira] [Created] (OOZIE-2059) Patch from OOZIE-1586 is not getting applied cleanly on Oozie-4.0.1 branch

2014-11-10 Thread Peeyush Bishnoi (JIRA)
Peeyush Bishnoi created OOZIE-2059:
--

 Summary: Patch from OOZIE-1586 is not getting applied cleanly on 
Oozie-4.0.1 branch
 Key: OOZIE-2059
 URL: https://issues.apache.org/jira/browse/OOZIE-2059
 Project: Oozie
  Issue Type: Bug
Reporter: Peeyush Bishnoi
Priority: Critical


I am tying to apply the v4 patch from OOZIE-1586 but it is not getting applied 
cleanly on Oozie-4.0.1 . Do I need to put extra patch before this patch.



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


[jira] [Created] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Ben Roling (JIRA)
Ben Roling created OOZIE-2060:
-

 Summary: Incorrect documentation of Java action config XML filename
 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: 4.0.1, 4.0.0, 3.3.2
Reporter: Ben Roling
Priority: Minor


The [documentation of Java 
action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
 suggests there Java action configuration is available in a file named 
oozie-action.conf.xml.

This does not seem to me to be true.  My experience is that this configuration 
is available in action.xml.



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


[jira] [Updated] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Ben Roling (JIRA)

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

Ben Roling updated OOZIE-2060:
--
Description: 
The [documentation of Java 
action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
 suggests that Java action configuration is available in a file named 
oozie-action.conf.xml.

This does not seem to me to be true.  My experience is that this configuration 
is available in action.xml.

  was:
The [documentation of Java 
action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
 suggests there Java action configuration is available in a file named 
oozie-action.conf.xml.

This does not seem to me to be true.  My experience is that this configuration 
is available in action.xml.


 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor

 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


4.1 release candidate

2014-11-10 Thread bowen zhang
Hi folks,
Based on this 
link:https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%204.1.0%20AND%20project%20%3D%20OOZIE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC,
 we don't really have any other issues except for publishing artifacts. I think 
we are ready to make the release candidate for testing. Can anyone with 
concerns reply to this thread by noon? Otherwise, I will proceed on making the 
RC.
thanks,
Bowen

[jira] [Commented] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Robert Kanter (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205120#comment-14205120
 ] 

Robert Kanter commented on OOZIE-2060:
--

Good catch.  It should say that it's available in a file is given by an 
environment variable named oozie.action.conf.xml.  
For example:
{code:java}
Configuration actionConf = new Configuration(false);
actionConf.addResource(new Path(file:///, 
System.getProperty(oozie.action.conf.xml)));
{code}

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Bug
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor

 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


[jira] [Commented] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Ben Roling (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205122#comment-14205122
 ] 

Ben Roling commented on OOZIE-2060:
---

I was going to submit a patch but then realized this is already fixed by 
OOZIE-1696.

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Bug
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor

 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


[jira] [Updated] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Robert Kanter (JIRA)

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

Robert Kanter updated OOZIE-2060:
-
Issue Type: Sub-task  (was: Bug)
Parent: OOZIE-1881

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Sub-task
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor

 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


[jira] [Commented] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Ben Roling (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205129#comment-14205129
 ] 

Ben Roling commented on OOZIE-2060:
---

Alternatively I have found that the action configuration can be added with 
-conf action.xml on the command line of a main class of a standard Hadoop 
Tool that uses GenericOptionsParser.  That may be worthwhile to note as it 
doesn't require special Oozie-aware code in the main class.

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Sub-task
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor

 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


[jira] [Commented] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Robert Kanter (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205176#comment-14205176
 ] 

Robert Kanter commented on OOZIE-2060:
--

That sounds useful.  Let's repurpose this JIRA for documenting that.

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Sub-task
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor

 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


[jira] [Updated] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Ben Roling (JIRA)

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

Ben Roling updated OOZIE-2060:
--
Attachment: OOZIE-2060.patch

I'm attaching a potential patch.  Perhaps most notable is the fact that I 
removed mention of the 'oozie-action.conf.xml' system property in favor of 
simply referencing the filename 'action.xml'.

Since I was going around the system property with the '-conf' solution I 
figured there wasn't much sense in using it when using the 'addResource()' 
strategy instead.

I'm not sure how to view the rendered wiki documentation to 'test' this change. 
 Perhaps you can help suggest how I would do that.  I suppose I probably just 
need to do a site build but I am too lazy at the moment to try that out.  
Before bothering it's probably worth knowing if the change generally looks good.

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Sub-task
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor
 Attachments: OOZIE-2060.patch


 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


[jira] [Commented] (OOZIE-2045) Symlink support for sharelib

2014-11-10 Thread Rohini Palaniswamy (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205222#comment-14205222
 ] 

Rohini Palaniswamy commented on OOZIE-2045:
---

+1

 Symlink support for sharelib
 

 Key: OOZIE-2045
 URL: https://issues.apache.org/jira/browse/OOZIE-2045
 Project: Oozie
  Issue Type: Bug
Reporter: Purshotam Shah
Assignee: Purshotam Shah
 Attachments: OOZIE-2045-V2.patch, OOZIE-2045-V3.patch, 
 OOZIE-2045-V4.patch


 With metafile configuration, one can configure sharelib (eg. pig_latest) to 
 latest version available.
 If new version is available, admin will just change the pig_latest sysmlink 
 to new version. 
 There will be no change to Oozie or metafile configuration.
 Oozie should be able to detect symlink change and reloads the sharelib.
 metafile configuration can look like
 oozie.pig_latest=hdfs:///tmp/pig_latest
 where /tmp/pig_latest is a symlink pointing to latest available version.



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


[jira] [Commented] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205349#comment-14205349
 ] 

Hadoop QA commented on OOZIE-2060:
--

Testing JIRA OOZIE-2060

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:red}-1{color} the patch contains 2 line(s) with trailing spaces
.{color:red}-1{color} the patch contains 2 line(s) longer than 132 
characters
.{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: 1551
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testActionKillCommandDate(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)

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

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Sub-task
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor
 Attachments: OOZIE-2060.patch


 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


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

2014-11-10 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2083/

--
[...truncated 10865 lines...]
[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: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
[WARNING] Assembly file: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
 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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar
[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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin/apache-tomcat-6.0.41.tar.gz
  [get] To: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads/tomcat-6.0.41.tar.gz

[jira] [Updated] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Ben Roling (JIRA)

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

Ben Roling updated OOZIE-2060:
--
Attachment: OOZIE-2060.patch

New version of the patch fixing trailing spaces and lines longer than 132 
characters.

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Sub-task
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor
 Attachments: OOZIE-2060.patch, OOZIE-2060.patch


 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


[jira] [Assigned] (OOZIE-2055) PauseTransitService does not proceed forward if any job has issue

2014-11-10 Thread Purshotam Shah (JIRA)

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

Purshotam Shah reassigned OOZIE-2055:
-

Assignee: Purshotam Shah

 PauseTransitService does not proceed forward if any job has issue 
 --

 Key: OOZIE-2055
 URL: https://issues.apache.org/jira/browse/OOZIE-2055
 Project: Oozie
  Issue Type: Bug
Reporter: Purshotam Shah
Assignee: Purshotam Shah
 Attachments: OOZIE-2055-V1.patch


 {code}
  // start bundles as needed;
 try {
 jobList = jpaService.execute(new 
 BundleJobsGetNeedStartJPAExecutor(d));
 if (jobList != null) {
 for (BundleJobBean bundleJob : jobList) {
 bundleJob.setKickoffTime(d);
 new BundleStartXCommand(bundleJob.getId()).call();
 LOG.debug(Calling BundleStartXCommand for bundle job 
 =  + bundleJob.getId());
 }
 }
 }
 catch (Exception ex) {
 LOG.warn(Exception happened when pausing/unpausing/starting 
 Bundle jobs, ex);
 }
 {code}
 If any of job has issue, then exception will be thrown and 
 PauseTransitService will ignore all other jobs.



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


[jira] [Updated] (OOZIE-2055) PauseTransitService does not proceed forward if any job has issue

2014-11-10 Thread Purshotam Shah (JIRA)

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

Purshotam Shah updated OOZIE-2055:
--
Attachment: OOZIE-2055-V1.patch

 PauseTransitService does not proceed forward if any job has issue 
 --

 Key: OOZIE-2055
 URL: https://issues.apache.org/jira/browse/OOZIE-2055
 Project: Oozie
  Issue Type: Bug
Reporter: Purshotam Shah
 Attachments: OOZIE-2055-V1.patch


 {code}
  // start bundles as needed;
 try {
 jobList = jpaService.execute(new 
 BundleJobsGetNeedStartJPAExecutor(d));
 if (jobList != null) {
 for (BundleJobBean bundleJob : jobList) {
 bundleJob.setKickoffTime(d);
 new BundleStartXCommand(bundleJob.getId()).call();
 LOG.debug(Calling BundleStartXCommand for bundle job 
 =  + bundleJob.getId());
 }
 }
 }
 catch (Exception ex) {
 LOG.warn(Exception happened when pausing/unpausing/starting 
 Bundle jobs, ex);
 }
 {code}
 If any of job has issue, then exception will be thrown and 
 PauseTransitService will ignore all other jobs.



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


[jira] [Updated] (OOZIE-2043) Misc test failures against JDK8

2014-11-10 Thread Robert Kanter (JIRA)

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

Robert Kanter updated OOZIE-2043:
-
Attachment: OOZIE-2043.patch

The new patch fixes the output order.  Though after reading the documentation, 
in hindsight, I'm not sure this really matters because this is supposed to be a 
list of {{key=value}} pairs, whose order doesn't appear to matter as far as I 
can tell.  Anyway, this makes the test more consistent.

[~rohini], can you take another look?

 Misc test failures against JDK8
 ---

 Key: OOZIE-2043
 URL: https://issues.apache.org/jira/browse/OOZIE-2043
 Project: Oozie
  Issue Type: Bug
  Components: tests
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
 Fix For: trunk

 Attachments: OOZIE-2043.patch, OOZIE-2043.patch


 Using the below procedure, I built Oozie with Java 7 and then built and ran 
 the tests with Java 8:
 - set java 7
 - {{mvn clean test -DskipTests}}
 - {{find . -name test-classes | grep target/test-classes | xargs rm -rf}} 
   // Delete test classes
 - set java 8
 - {{mvn test -DtargetJavaVersion=1.8}}
 There were 3 test failures:
 - org.apache.oozie.coord.TestHCatELFunctions.testDataOutPartitions
 -- it was expecting {{'region=euro,datastamp=20130230'}} but now got 
 {{'datastamp=20130230,region=euro'}}
 - org.apache.oozie.util.TestELConstantsFunctions.testAppendAll
 -- Java 8 changes the behavior of the String.split method to not include a 
 leading empty String if the pattern matches the front of the String.  To 
 remain backwards compatible, the solution here was to emulate this behavior 
 so the appendAll method behaves the same as it did with Java 6 and 7.
 - 
 org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser.testForkJoinMismatch
 -- it was checking a parameterized error message where the order of the 
 parameters switched



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


[jira] [Commented] (OOZIE-2043) Misc test failures against JDK8

2014-11-10 Thread Rohini Palaniswamy (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205381#comment-14205381
 ] 

Rohini Palaniswamy commented on OOZIE-2043:
---

+1

 Misc test failures against JDK8
 ---

 Key: OOZIE-2043
 URL: https://issues.apache.org/jira/browse/OOZIE-2043
 Project: Oozie
  Issue Type: Bug
  Components: tests
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
 Fix For: trunk

 Attachments: OOZIE-2043.patch, OOZIE-2043.patch


 Using the below procedure, I built Oozie with Java 7 and then built and ran 
 the tests with Java 8:
 - set java 7
 - {{mvn clean test -DskipTests}}
 - {{find . -name test-classes | grep target/test-classes | xargs rm -rf}} 
   // Delete test classes
 - set java 8
 - {{mvn test -DtargetJavaVersion=1.8}}
 There were 3 test failures:
 - org.apache.oozie.coord.TestHCatELFunctions.testDataOutPartitions
 -- it was expecting {{'region=euro,datastamp=20130230'}} but now got 
 {{'datastamp=20130230,region=euro'}}
 - org.apache.oozie.util.TestELConstantsFunctions.testAppendAll
 -- Java 8 changes the behavior of the String.split method to not include a 
 leading empty String if the pattern matches the front of the String.  To 
 remain backwards compatible, the solution here was to emulate this behavior 
 so the appendAll method behaves the same as it did with Java 6 and 7.
 - 
 org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser.testForkJoinMismatch
 -- it was checking a parameterized error message where the order of the 
 parameters switched



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


[jira] [Commented] (OOZIE-2045) Symlink support for sharelib

2014-11-10 Thread Purshotam Shah (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205456#comment-14205456
 ] 

Purshotam Shah commented on OOZIE-2045:
---

Thanks for review. Committed to trunk.

 Symlink support for sharelib
 

 Key: OOZIE-2045
 URL: https://issues.apache.org/jira/browse/OOZIE-2045
 Project: Oozie
  Issue Type: Bug
Reporter: Purshotam Shah
Assignee: Purshotam Shah
 Attachments: OOZIE-2045-V2.patch, OOZIE-2045-V3.patch, 
 OOZIE-2045-V4.patch


 With metafile configuration, one can configure sharelib (eg. pig_latest) to 
 latest version available.
 If new version is available, admin will just change the pig_latest sysmlink 
 to new version. 
 There will be no change to Oozie or metafile configuration.
 Oozie should be able to detect symlink change and reloads the sharelib.
 metafile configuration can look like
 oozie.pig_latest=hdfs:///tmp/pig_latest
 where /tmp/pig_latest is a symlink pointing to latest available version.



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


Re: 4.1 release candidate

2014-11-10 Thread Robert Kanter
I don't have any concerns.
Though the list has another JIRA set for 4.1: OOZIE-1636.  Any idea what
that is?

On Mon, Nov 10, 2014 at 10:23 AM, bowen zhang 
bowenzhang...@yahoo.com.invalid wrote:

 Hi folks,
 Based on this link:
 https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%204.1.0%20AND%20project%20%3D%20OOZIE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC,
 we don't really have any other issues except for publishing artifacts. I
 think we are ready to make the release candidate for testing. Can anyone
 with concerns reply to this thread by noon? Otherwise, I will proceed on
 making the RC.
 thanks,
 Bowen


[jira] [Commented] (OOZIE-2055) PauseTransitService does not proceed forward if any job has issue

2014-11-10 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205533#comment-14205533
 ] 

Hadoop QA commented on OOZIE-2055:
--

Testing JIRA OOZIE-2055

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:green}+1 TESTS{color}
.Tests run: 1551
{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/2084/

 PauseTransitService does not proceed forward if any job has issue 
 --

 Key: OOZIE-2055
 URL: https://issues.apache.org/jira/browse/OOZIE-2055
 Project: Oozie
  Issue Type: Bug
Reporter: Purshotam Shah
Assignee: Purshotam Shah
 Attachments: OOZIE-2055-V1.patch


 {code}
  // start bundles as needed;
 try {
 jobList = jpaService.execute(new 
 BundleJobsGetNeedStartJPAExecutor(d));
 if (jobList != null) {
 for (BundleJobBean bundleJob : jobList) {
 bundleJob.setKickoffTime(d);
 new BundleStartXCommand(bundleJob.getId()).call();
 LOG.debug(Calling BundleStartXCommand for bundle job 
 =  + bundleJob.getId());
 }
 }
 }
 catch (Exception ex) {
 LOG.warn(Exception happened when pausing/unpausing/starting 
 Bundle jobs, ex);
 }
 {code}
 If any of job has issue, then exception will be thrown and 
 PauseTransitService will ignore all other jobs.



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


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

2014-11-10 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2084/changes

Changes:

[rkanter] OOZIE-1385 Make Uber Mode the default (rkanter)

--
[...truncated 10858 lines...]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-tools ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[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: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
[WARNING] Assembly file: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
 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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar
[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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

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

[jira] [Commented] (OOZIE-2060) Incorrect documentation of Java action config XML filename

2014-11-10 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205541#comment-14205541
 ] 

Hadoop QA commented on OOZIE-2060:
--

Testing JIRA OOZIE-2060

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:red}-1{color} the patch contains 2 line(s) with trailing spaces
.{color:red}-1{color} the patch contains 2 line(s) longer than 132 
characters
.{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: 1551
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testMemoryUsageAndSpeed(org.apache.oozie.service.TestPartitionDependencyManagerService)

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

 Incorrect documentation of Java action config XML filename
 --

 Key: OOZIE-2060
 URL: https://issues.apache.org/jira/browse/OOZIE-2060
 Project: Oozie
  Issue Type: Sub-task
  Components: docs
Affects Versions: 3.3.2, 4.0.0, 4.0.1
Reporter: Ben Roling
Priority: Minor
 Attachments: OOZIE-2060.patch, OOZIE-2060.patch


 The [documentation of Java 
 action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
  suggests that Java action configuration is available in a file named 
 oozie-action.conf.xml.
 This does not seem to me to be true.  My experience is that this 
 configuration is available in action.xml.



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


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

2014-11-10 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2085/

--
[...truncated 11129 lines...]

[INFO] Copying files to 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
[WARNING] Assembly file: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
 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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar
[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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin/apache-tomcat-6.0.41.tar.gz
  [get] To: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads/tomcat-6.0.41.tar.gz
..
[mkdir] Created dir: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/tomcat
   [gunzip] Expanding 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads/tomcat-6.0.41.tar.gz
 to 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/tomcat/tomcat-6.0.41.tar
[untar] Expanding: 

Build failed in Jenkins: oozie-trunk-find-patches-available #81065

2014-11-10 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-find-patches-available/81065/

--
Started by timer
Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace 
https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/
  git rev-parse --is-inside-work-tree
Fetching changes from the remote Git repository
  git config remote.origin.url 
  https://git-wip-us.apache.org/repos/asf/oozie.git
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
  git --version
  git fetch --tags --progress 
  https://git-wip-us.apache.org/repos/asf/oozie.git 
  +refs/heads/*:refs/remotes/origin/*
FATAL: Failed to fetch from https://git-wip-us.apache.org/repos/asf/oozie.git
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/oozie.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:623)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:855)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524)
at hudson.model.Run.execute(Run.java:1706)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Caused by: hudson.plugins.git.GitException: Command git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/oozie.git 
+refs/heads/*:refs/remotes/origin/* returned status code 128:
stdout: 
stderr: fatal: unable to access 
'https://git-wip-us.apache.org/repos/asf/oozie.git/': GnuTLS recv error (-9): A 
TLS packet with unexpected length was received.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1301)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1163)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:87)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:257)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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:745)


Jenkins build is back to normal : oozie-trunk-find-patches-available #81066

2014-11-10 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-find-patches-available/81066/



[jira] [Commented] (OOZIE-2043) Misc test failures against JDK8

2014-11-10 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205734#comment-14205734
 ] 

Hadoop QA commented on OOZIE-2043:
--

Testing JIRA OOZIE-2043

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 2 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: 1552
.Tests failed: 3
.Tests errors: 0

.The patch failed the following testcases:

.  
testBundleStatusNotTransitionFromKilled(org.apache.oozie.service.TestStatusTransitService)
.  
testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService)
.  
testMaxMatThrottleNotPicked(org.apache.oozie.service.TestCoordMaterializeTriggerService)

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

 Misc test failures against JDK8
 ---

 Key: OOZIE-2043
 URL: https://issues.apache.org/jira/browse/OOZIE-2043
 Project: Oozie
  Issue Type: Bug
  Components: tests
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
 Fix For: trunk

 Attachments: OOZIE-2043.patch, OOZIE-2043.patch


 Using the below procedure, I built Oozie with Java 7 and then built and ran 
 the tests with Java 8:
 - set java 7
 - {{mvn clean test -DskipTests}}
 - {{find . -name test-classes | grep target/test-classes | xargs rm -rf}} 
   // Delete test classes
 - set java 8
 - {{mvn test -DtargetJavaVersion=1.8}}
 There were 3 test failures:
 - org.apache.oozie.coord.TestHCatELFunctions.testDataOutPartitions
 -- it was expecting {{'region=euro,datastamp=20130230'}} but now got 
 {{'datastamp=20130230,region=euro'}}
 - org.apache.oozie.util.TestELConstantsFunctions.testAppendAll
 -- Java 8 changes the behavior of the String.split method to not include a 
 leading empty String if the pattern matches the front of the String.  To 
 remain backwards compatible, the solution here was to emulate this behavior 
 so the appendAll method behaves the same as it did with Java 6 and 7.
 - 
 org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser.testForkJoinMismatch
 -- it was checking a parameterized error message where the order of the 
 parameters switched



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


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

2014-11-10 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2086/changes

Changes:

[purushah] OOZIE-2045 Symlink support for sharelib

--
[...truncated 18285 lines...]
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
[WARNING] Assembly file: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
 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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar
[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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin/apache-tomcat-6.0.41.tar.gz
  [get] To: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads/tomcat-6.0.41.tar.gz

[jira] [Commented] (OOZIE-2043) Misc test failures against JDK8

2014-11-10 Thread Robert Kanter (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14205803#comment-14205803
 ] 

Robert Kanter commented on OOZIE-2043:
--

Test failures unrelated.

 Misc test failures against JDK8
 ---

 Key: OOZIE-2043
 URL: https://issues.apache.org/jira/browse/OOZIE-2043
 Project: Oozie
  Issue Type: Bug
  Components: tests
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
 Fix For: trunk

 Attachments: OOZIE-2043.patch, OOZIE-2043.patch


 Using the below procedure, I built Oozie with Java 7 and then built and ran 
 the tests with Java 8:
 - set java 7
 - {{mvn clean test -DskipTests}}
 - {{find . -name test-classes | grep target/test-classes | xargs rm -rf}} 
   // Delete test classes
 - set java 8
 - {{mvn test -DtargetJavaVersion=1.8}}
 There were 3 test failures:
 - org.apache.oozie.coord.TestHCatELFunctions.testDataOutPartitions
 -- it was expecting {{'region=euro,datastamp=20130230'}} but now got 
 {{'datastamp=20130230,region=euro'}}
 - org.apache.oozie.util.TestELConstantsFunctions.testAppendAll
 -- Java 8 changes the behavior of the String.split method to not include a 
 leading empty String if the pattern matches the front of the String.  To 
 remain backwards compatible, the solution here was to emulate this behavior 
 so the appendAll method behaves the same as it did with Java 6 and 7.
 - 
 org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser.testForkJoinMismatch
 -- it was checking a parameterized error message where the order of the 
 parameters switched



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


[jira] [Created] (OOZIE-2061) Remove CoordJobDeleteJPAExecutor

2014-11-10 Thread Shwetha G S (JIRA)
Shwetha G S created OOZIE-2061:
--

 Summary: Remove CoordJobDeleteJPAExecutor
 Key: OOZIE-2061
 URL: https://issues.apache.org/jira/browse/OOZIE-2061
 Project: Oozie
  Issue Type: Bug
Reporter: Shwetha G S
Priority: Trivial


Looks like CoordJobDeleteJPAExecutor is not used anywhere. Remove if not 
required



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


[jira] [Updated] (OOZIE-2061) Remove CoordJobDeleteJPAExecutor

2014-11-10 Thread Shwetha G S (JIRA)

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

Shwetha G S updated OOZIE-2061:
---
Issue Type: Task  (was: Bug)

 Remove CoordJobDeleteJPAExecutor
 

 Key: OOZIE-2061
 URL: https://issues.apache.org/jira/browse/OOZIE-2061
 Project: Oozie
  Issue Type: Task
Reporter: Shwetha G S
Priority: Trivial

 Looks like CoordJobDeleteJPAExecutor is not used anywhere. Remove if not 
 required



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


[jira] [Updated] (OOZIE-1803) Improvement in Purge service

2014-11-10 Thread Shwetha G S (JIRA)

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

Shwetha G S updated OOZIE-1803:
---
Attachment: OOZIE-1803-v7.patch

 Improvement in Purge service
 

 Key: OOZIE-1803
 URL: https://issues.apache.org/jira/browse/OOZIE-1803
 Project: Oozie
  Issue Type: Improvement
  Components: core
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma
 Attachments: OOZIE-1803-v1.patch, OOZIE-1803-v2.patch, 
 OOZIE-1803-v3.patch, OOZIE-1803-v4.patch, OOZIE-1803-v6.patch, 
 OOZIE-1803-v7.patch, OOZIE-1803.patch, purgeservice-1.patch, 
 purgeservice.patch


 Current purge service of oozie have some performance issues and it might help 
 to look at the queries and indexes to improve the the purge service.



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


[jira] [Created] (OOZIE-2062) Provide alternate purging logic

2014-11-10 Thread Shwetha G S (JIRA)
Shwetha G S created OOZIE-2062:
--

 Summary: Provide alternate purging logic
 Key: OOZIE-2062
 URL: https://issues.apache.org/jira/browse/OOZIE-2062
 Project: Oozie
  Issue Type: Improvement
Reporter: Shwetha G S


Currently, purge service deletes a workflow only if all its children are 
complete, coord action only if the corresponding workflow and its sub-workflows 
are complete. This logic is complicated and takes longer to run. Instead, 
provide an alternative purging logic that deleted all workflows whose end time 
is older than configured time, delete coord actions whose end time is older 
than configured time and so on. The purging logic to be used can be configured 
from oozie-site (by default can default to the current logic for backward 
compatbility)



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


[jira] [Assigned] (OOZIE-2062) Provide alternate purging logic

2014-11-10 Thread Jaydeep Vishwakarma (JIRA)

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

Jaydeep Vishwakarma reassigned OOZIE-2062:
--

Assignee: Jaydeep Vishwakarma

 Provide alternate purging logic
 ---

 Key: OOZIE-2062
 URL: https://issues.apache.org/jira/browse/OOZIE-2062
 Project: Oozie
  Issue Type: Improvement
Reporter: Shwetha G S
Assignee: Jaydeep Vishwakarma

 Currently, purge service deletes a workflow only if all its children are 
 complete, coord action only if the corresponding workflow and its 
 sub-workflows are complete. This logic is complicated and takes longer to 
 run. Instead, provide an alternative purging logic that deleted all workflows 
 whose end time is older than configured time, delete coord actions whose end 
 time is older than configured time and so on. The purging logic to be used 
 can be configured from oozie-site (by default can default to the current 
 logic for backward compatbility)



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


Re: Review Request 27614: OOZIE-1983 Add spark action executor in oozie

2014-11-10 Thread pavan kumar kolamuri

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

(Updated Nov. 11, 2014, 6:35 a.m.)


Review request for oozie and shwethags.


Summary (updated)
-

OOZIE-1983 Add spark action executor in oozie


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


Repository: oozie-git


Description
---

Add spark action executor in oozie. Spark jobs can be run using oozie 


Diffs
-

  client/src/main/java/org/apache/oozie/cli/OozieCLI.java 9c2d14b 
  client/src/main/resources/spark-action-0.1.xsd PRE-CREATION 
  core/src/main/java/org/apache/oozie/action/hadoop/DistcpActionExecutor.java 
42f2965 
  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
7349d3f 
  core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
PRE-CREATION 
  core/src/main/resources/oozie-default.xml 17155a1 
  pom.xml 1e79186 
  sharelib/pom.xml aa479a8 
  sharelib/spark/pom.xml PRE-CREATION 
  sharelib/spark/src/main/java/org.apache.oozie.action.hadoop/SparkMain.java 
PRE-CREATION 
  
sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkActionExecutor.java
 PRE-CREATION 
  
sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkMain.java 
PRE-CREATION 
  src/main/assemblies/sharelib.xml 4a46b90 
  webapp/pom.xml 35776c5 

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


Testing
---

Both unit testing and end to end testing done


Thanks,

pavan kumar kolamuri



[jira] [Updated] (OOZIE-1983) Add spark action executor

2014-11-10 Thread pavan kumar kolamuri (JIRA)

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

pavan kumar kolamuri updated OOZIE-1983:

Attachment: spark-actionv1.patch

 Add spark action executor
 -

 Key: OOZIE-1983
 URL: https://issues.apache.org/jira/browse/OOZIE-1983
 Project: Oozie
  Issue Type: New Feature
Reporter: Shwetha G S
Assignee: pavan kumar kolamuri
  Labels: spark
 Fix For: trunk

 Attachments: spark-actionv1.patch






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


[jira] [Commented] (OOZIE-1983) Add spark action executor

2014-11-10 Thread Shwetha G S (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206033#comment-14206033
 ] 

Shwetha G S commented on OOZIE-1983:


+1, looks good to me. Does anyone  else want to review?

 Add spark action executor
 -

 Key: OOZIE-1983
 URL: https://issues.apache.org/jira/browse/OOZIE-1983
 Project: Oozie
  Issue Type: New Feature
Reporter: Shwetha G S
Assignee: pavan kumar kolamuri
  Labels: spark
 Fix For: trunk

 Attachments: spark-actionv1.patch






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


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

2014-11-10 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2088/changes

Changes:

[shwetha.gs] OOZIE-1803 Improvement in Purge service (jaydeepvishwakarma via 
shwethags)

--
[...truncated 3442 lines...]
[WARNING] 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/workflowgenerator/src/main/java/org/apache/oozie/tools/workflowgenerator/client/property/action/ShellPropertyTable.java:[184,11]
 [deprecation] setChecked(boolean) in com.google.gwt.user.client.ui.CheckBox 
has been deprecated
[INFO] 
[INFO] --- maven-war-plugin:2.1.1:exploded (default) @ oozie-workflowgenerator 
---
[INFO] Exploding webapp
[INFO] Assembling webapp [oozie-workflowgenerator] in 
[https://builds.apache.org/job/oozie-trunk-precommit-build/ws/workflowgenerator/target/oozie-wfgen]
[INFO] Processing war project
[INFO] Copying webapp resources 
[https://builds.apache.org/job/oozie-trunk-precommit-build/ws/workflowgenerator/src/main/webapp]
[INFO] Webapp assembled in [296 msecs]
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-workflowgenerator ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/workflowgenerator/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-workflowgenerator ---
[INFO] Compiling 1 source file to 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/workflowgenerator/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ 
oozie-workflowgenerator ---
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oozie-distro ---
[INFO] Deleting 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/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] 
[INFO] Building Apache Oozie ZooKeeper Security Tests 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
oozie-zookeeper-security-tests ---
[INFO] Deleting 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/zookeeper-security-tests/target
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/zookeeper-security-tests/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
oozie-zookeeper-security-tests ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-zookeeper-security-tests ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/zookeeper-security-tests/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Compiling 2 source files to 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/zookeeper-security-tests/target/test-classes
[WARNING] 

[jira] [Commented] (OOZIE-1983) Add spark action executor

2014-11-10 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206037#comment-14206037
 ] 

Hadoop QA commented on OOZIE-1983:
--

Testing JIRA OOZIE-1983

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



 Add spark action executor
 -

 Key: OOZIE-1983
 URL: https://issues.apache.org/jira/browse/OOZIE-1983
 Project: Oozie
  Issue Type: New Feature
Reporter: Shwetha G S
Assignee: pavan kumar kolamuri
  Labels: spark
 Fix For: trunk

 Attachments: spark-actionv1.patch






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


[jira] [Updated] (OOZIE-1983) Add spark action executor

2014-11-10 Thread pavan kumar kolamuri (JIRA)

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

pavan kumar kolamuri updated OOZIE-1983:

Attachment: OOZIE-1983v2.patch

 Add spark action executor
 -

 Key: OOZIE-1983
 URL: https://issues.apache.org/jira/browse/OOZIE-1983
 Project: Oozie
  Issue Type: New Feature
Reporter: Shwetha G S
Assignee: pavan kumar kolamuri
  Labels: spark
 Fix For: trunk

 Attachments: OOZIE-1983v2.patch, spark-actionv1.patch






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


[jira] Subscription: Oozie Patch Available

2014-11-10 Thread jira
Issue Subscription
Filter: Oozie Patch Available (42 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
OOZIE-2055  PauseTransitService does not proceed forward if any job has issue 
https://issues.apache.org/jira/browse/OOZIE-2055
OOZIE-2053  Change old HCatalog API
https://issues.apache.org/jira/browse/OOZIE-2053
OOZIE-2051  Allows multiple default action configuration files per action
https://issues.apache.org/jira/browse/OOZIE-2051
OOZIE-2044  ssh action succeed with a not exists command which should be fail.
https://issues.apache.org/jira/browse/OOZIE-2044
OOZIE-2035  NotificationXCommand should support proxy
https://issues.apache.org/jira/browse/OOZIE-2035
OOZIE-2024  Confusing message when a job can't be looked up by 
JavaActionExecutor
https://issues.apache.org/jira/browse/OOZIE-2024
OOZIE-1983  Add spark action executor
https://issues.apache.org/jira/browse/OOZIE-1983
OOZIE-1980  Sql error should not fail coord job
https://issues.apache.org/jira/browse/OOZIE-1980
OOZIE-1977  Display patch analysis issues
https://issues.apache.org/jira/browse/OOZIE-1977
OOZIE-1936  Queuedump command should display queue information for all server.
https://issues.apache.org/jira/browse/OOZIE-1936
OOZIE-1931  Admin command to print all locks held by server(s)
https://issues.apache.org/jira/browse/OOZIE-1931
OOZIE-1927  Use StoreStatusFilter for WorkflowsJobGetJPAExecutor 
https://issues.apache.org/jira/browse/OOZIE-1927
OOZIE-1922  MemoryLocksService fails if lock is acquired multiple times in same 
thread and released
https://issues.apache.org/jira/browse/OOZIE-1922
OOZIE-1918  ActionXCommand refactoring for code reuse
https://issues.apache.org/jira/browse/OOZIE-1918
OOZIE-1889  Convert NamedNativeQueries to JPQL
https://issues.apache.org/jira/browse/OOZIE-1889
OOZIE-1884  ZKJobsConcurrencyService.checkJobIdForServer fails if jobs length  
7
https://issues.apache.org/jira/browse/OOZIE-1884
OOZIE-1876  use pom properties rather than specific version numbers in the pom 
files of hbaselibs, hcataloglibs, sharelib, etc 
https://issues.apache.org/jira/browse/OOZIE-1876
OOZIE-1860  Oozie job mapper launch fails due to null value returned from 
action file
https://issues.apache.org/jira/browse/OOZIE-1860
OOZIE-1855  TestPriorityDelayQueue#testPoll failed intermittently in Jenkins
https://issues.apache.org/jira/browse/OOZIE-1855
OOZIE-1829  URIHandlerService doesn't support URI schemes with query strings 
but no path segment
https://issues.apache.org/jira/browse/OOZIE-1829
OOZIE-1816  LogInfo uses action name instead of id
https://issues.apache.org/jira/browse/OOZIE-1816
OOZIE-1810  Workflow cannot get into Failed state when kill control node cannot 
resolve variable in message 
https://issues.apache.org/jira/browse/OOZIE-1810
OOZIE-1802  Support workflow action log
https://issues.apache.org/jira/browse/OOZIE-1802
OOZIE-1793  Improve find bugs reporting for Oozie
https://issues.apache.org/jira/browse/OOZIE-1793
OOZIE-1782  Workflow path not found is thrown as SC_UNAUTHORIZED
https://issues.apache.org/jira/browse/OOZIE-1782
OOZIE-1779  Add parent-id as a filter option
https://issues.apache.org/jira/browse/OOZIE-1779
OOZIE-1705  Enable gc logs and print thread id in logs
https://issues.apache.org/jira/browse/OOZIE-1705
OOZIE-1688  New configuration to specify server-server authentication type.
https://issues.apache.org/jira/browse/OOZIE-1688
OOZIE-1676  Instrumentation and Configuration over the REST API and Web UI 
should include all Oozie servers
https://issues.apache.org/jira/browse/OOZIE-1676
OOZIE-1654  Fix typo (inteval to interval)
https://issues.apache.org/jira/browse/OOZIE-1654
OOZIE-1638  Action retry does not use default retry max count.
https://issues.apache.org/jira/browse/OOZIE-1638
OOZIE-1636  OOZIE_SYS table engine should be innodb
https://issues.apache.org/jira/browse/OOZIE-1636
OOZIE-1624  Exclusion pattern for sharelib.
https://issues.apache.org/jira/browse/OOZIE-1624
OOZIE-1599  Cache the list of available timezones from the admin servlet
https://issues.apache.org/jira/browse/OOZIE-1599
OOZIE-1579  Add basic HTTP auth to Oozie CLI
https://issues.apache.org/jira/browse/OOZIE-1579
OOZIE-1376  Extending Oozie ACLs like admin groups and proxy users to support 
both groups and users
https://issues.apache.org/jira/browse/OOZIE-1376
OOZIE-1369  OozieDBCLI code should not hardcode the Oozie table filenames

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

2014-11-10 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2087/changes

Changes:

[rkanter] OOZIE-2043 Misc test failures against JDK8 (rkanter)

--
[...truncated 10890 lines...]
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
[WARNING] Assembly file: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools
 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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar
[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.2.0-SNAPSHOT
[INFO] 
[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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/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 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin/apache-tomcat-6.0.41.tar.gz
  [get] To: 
https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads/tomcat-6.0.41.tar.gz

[jira] [Commented] (OOZIE-1803) Improvement in Purge service

2014-11-10 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/OOZIE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206071#comment-14206071
 ] 

Hadoop QA commented on OOZIE-1803:
--

Testing JIRA OOZIE-1803

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 4 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:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{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: 1554
.Tests failed: 3
.Tests errors: 0

.The patch failed the following testcases:

.  
testGetCoordinatorParent(org.apache.oozie.executor.jpa.TestWorkflowJobsBasicInfoFromCoordParentIdJPAExecutor)
.  
testMessage_withMixedStatus(org.apache.oozie.command.coord.TestAbandonedCoordChecker)
.  
testCoordActionGetFIFO(org.apache.oozie.executor.jpa.TestCoordJobGetReadyActionsJPAExecutor)

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

 Improvement in Purge service
 

 Key: OOZIE-1803
 URL: https://issues.apache.org/jira/browse/OOZIE-1803
 Project: Oozie
  Issue Type: Improvement
  Components: core
Reporter: Jaydeep Vishwakarma
Assignee: Jaydeep Vishwakarma
 Fix For: trunk

 Attachments: OOZIE-1803-v1.patch, OOZIE-1803-v2.patch, 
 OOZIE-1803-v3.patch, OOZIE-1803-v4.patch, OOZIE-1803-v6.patch, 
 OOZIE-1803-v7.patch, OOZIE-1803.patch, purgeservice-1.patch, 
 purgeservice.patch


 Current purge service of oozie have some performance issues and it might help 
 to look at the queries and indexes to improve the the purge service.



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