date:20170703

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

2017-07-03 Thread Apache Jenkins Server

See 


--
[...truncated 359.94 KB...]
[INFO] Copying javax.annotation-api-1.2.jar to 

[INFO] Copying commons-compiler-2.7.6.jar to 

[INFO] Copying ant-1.9.1.jar to 

[INFO] Copying hadoop-annotations-2.6.0.jar to 

[INFO] Copying janino-2.7.6.jar to 

[INFO] Copying activemq-client-5.13.3.jar to 

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

[INFO] Copying oozie-client-5.0.0-SNAPSHOT.jar to 

[INFO] Copying hadoop-mapreduce-client-common-2.6.0.jar to 

[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

[INFO] Copying jackson-core-2.4.2.jar to 

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying netty-3.7.0.Final.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

[INFO] Copying jetty-io-9.2.19.v20160908.jar to 

[INFO] Copying commons-beanutils-core-1.8.0.jar to 

[INFO] Copying antlr-2.7.7.jar to 

[INFO] Copying slf4j-log4j12-1.6.6.jar to 

[INFO] Copying datanucleus-api-jdo-3.2.6.jar to 

[INFO] Copying jung-api-2.0.1.jar to 

[INFO] Copying jta-1.1.jar to 

[INFO] Copying apacheds-kerberos-codec-2.0.0-M15.jar to 

[INFO] Copying kryo-2.22.jar to 

[INFO] Copying jackson-databind-2.4.2.jar to 

[INFO] Copying hive-serde-1.2.0.jar to 

[INFO] Copying jetty-client-9.2.19.v20160908.jar to 

[INFO] Copying hadoop-yarn-server-web-proxy-2.6.0.jar to

[jira] [Commented] (OOZIE-2977) error: self-closing element not allowed

2017-07-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2977:
--

Testing JIRA OOZIE-2977

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:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 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: 1968
.Tests failed: 6
.Tests errors: 2

.The patch failed the following testcases:

.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testLoadDump(org.apache.oozie.tools.TestDBLoadDump)

.Tests failing with errors:
.  testAddXIncludeFromReader(org.apache.oozie.util.TestXConfiguration)
.  testAddXIncludeFromStream(org.apache.oozie.util.TestXConfiguration)

{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}

{color:red}. There is at least one warning, please check{color}

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

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

> error: self-closing element not allowed
> ---
>
> Key: OOZIE-2977
> URL: https://issues.apache.org/jira/browse/OOZIE-2977
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2977-0.patch
>
>
> compiling with Java 1.8, javadoc throws the following errors
> {noformat}
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

2017-07-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2969:
--

Testing JIRA OOZIE-2969

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:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:red}-1{color} patch does not compile
.{color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{color:green}+1{color} There are no new bugs found in total.
{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} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch


{color:red}*-1 Overall result, please check the reported -1(s)*{color}

{color:red}. There is at least one warning, please check{color}

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

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

> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2969-0.patch, OOZIE-2969-0.patch
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-07-03 Thread Apache Jenkins Server

See 


--
[...truncated 99.40 KB...]
[INFO] Skipping Apache Oozie Share Lib Hive 2
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Share Lib Sqoop
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Examples
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Share Lib Spark
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Share Lib
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Docs
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie WebApp
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Tools
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie MiniOozie
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Server
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Distro
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie ZooKeeper Security Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. FAILURE [  0.374 s]
[INFO] Apache Oozie Client  SKIPPED
[INFO] Apache Oozie Share Lib Oozie ... SKIPPED
[INFO] Apache Oozie Share Lib HCatalog  SKIPPED
[INFO] Apache Oozie Share Lib Distcp .. SKIPPED
[INFO] Apache Oozie Core .. SKIPPED
[INFO] Apache Oozie Share Lib Streaming ... SKIPPED
[INFO] Apache Oozie Share Lib Pig . SKIPPED
[INFO] Apache Oozie Share Lib Hive  SKIPPED
[INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
[INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
[INFO] Apache Oozie Examples .. SKIPPED
[INFO] Apache Oozie Share Lib Spark ... SKIPPED
[INFO] Apache Oozie Share Lib . SKIPPED
[INFO] Apache Oozie Docs .. SKIPPED
[INFO] Apache Oozie WebApp  SKIPPED
[INFO] Apache Oozie Tools . SKIPPED
[INFO] Apache Oozie MiniOozie . SKIPPED
[INFO] Apache Oozie Server  SKIPPED
[INFO] Apache Oozie Distro  SKIPPED
[INFO] Apache Oozie

[jira] [Commented] (OOZIE-2854) Oozie should handle transient database problems

2017-07-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2854:
--

Testing JIRA OOZIE-2854

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 6 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 12 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}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:red}-1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:red}-1{color} the patch modifies 1 JPA file(s), persistence.xml or 
*-orm.xml
{color:green}+1 TESTS{color}
.Tests run: 1603
.Tests rerun: 3
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestHdfsOperations,
{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}

{color:red}. There is at least one warning, please check{color}

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

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

> Oozie should handle transient database problems
> ---
>
> Key: OOZIE-2854
> URL: https://issues.apache.org/jira/browse/OOZIE-2854
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Piros
> Attachments: OOZIE-2854-001.patch, OOZIE-2854-002.patch, 
> OOZIE-2854-003.patch, OOZIE-2854-004.patch, OOZIE-2854-005.patch, 
> OOZIE-2854.006.patch, OOZIE-2854.007.patch, OOZIE-2854-POC-001.patch
>
>
> There can be problems when Oozie cannot update the database properly. 
> Recently, we have experienced erratic behavior with two setups:
> * MySQL with the Galera cluster manager. Galera uses cluster-wide optimistic 
> locking which might cause a transaction to rollback if there are two or more 
> parallel transaction running and one of them cannot complete because of a 
> conflict.
> * MySQL with Percona XtraDB Cluster. If one of the MySQL instances is killed, 
> Oozie might get "Communications link failure" exception during the failover.
> The problem is that failed DB transactions later might cause a workflow 
> (which are started/re-started by RecoveryService) to get stuck. It's not 
> clear to us how this happens but it has to do with the fact that certain DB 
> updates are not executed.
> The solution is to use some sort of retry logic with exponential backoff if 
> the DB update fails. We could start with a 100ms wait time which is doubled 
> at every retry. The operation can be considered a failure if it still fails 
> after 10 attempts. These values could be configurable. We should discuss 
> initial values in the scope of this JIRA.
> Note that this solution is to handle *transient* failures. If the DB is down 
> for a longer period of time, we have to accept that the internal state of 
> Oozie is corrupted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-07-03 Thread Apache Jenkins Server

See 


--
[...truncated 329.28 KB...]
[INFO] Copying ivy-2.4.0.jar to 

[INFO] Copying jackson-core-asl-1.9.13.jar to 

[INFO] Copying commons-jexl-2.1.1.jar to 

[INFO] Copying oozie-sharelib-hcatalog-5.0.0-SNAPSHOT.jar to 

[INFO] Copying hadoop-mapreduce-client-jobclient-2.6.0.jar to 

[INFO] Copying gson-2.7.jar to 

[INFO] Copying oozie-core-5.0.0-SNAPSHOT.jar to 

[INFO] Copying commons-pool-1.5.4.jar to 

[INFO] Copying htrace-core-3.0.4.jar to 

[INFO] Copying jaxb-impl-2.2.3-1.jar to 

[INFO] Copying jets3t-0.9.0.jar to 

[INFO] Copying datanucleus-rdbms-3.2.9.jar to 

[INFO] Copying hive-common-1.2.0.jar to 

[INFO] Copying snappy-java-1.0.4.1.jar to 

[INFO] Copying javax.annotation-api-1.2.jar to 

[INFO] Copying commons-compiler-2.7.6.jar to 

[INFO] Copying ant-1.9.1.jar to 

[INFO] Copying hadoop-annotations-2.6.0.jar to 

[INFO] Copying janino-2.7.6.jar to 

[INFO] Copying activemq-client-5.13.3.jar to 

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

[INFO] Copying oozie-client-5.0.0-SNAPSHOT.jar to 

[INFO] Copying hadoop-mapreduce-client-common-2.6.0.jar to 

[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

[INFO] Copying jackson-core-2.4.2.jar to 

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying netty-3.7.0.Final.jar to 

[INFO] Copying

[jira] [Updated] (OOZIE-2969) Drop support for Java 1.7

2017-07-03 Thread Artem Ervits (JIRA)


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

Artem Ervits updated OOZIE-2969:

Attachment: OOZIE-2969-0.patch

> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2969-0.patch, OOZIE-2969-0.patch
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

2017-07-03 Thread Artem Ervits (JIRA)


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

Artem Ervits commented on OOZIE-2969:
-

not sure why it failed to compile, it works fine on my local system

{code}
./bin/mkdistro.sh -DskipTests=true
{code}

> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2969-0.patch
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2975) code clean up in pig sharelib, replace Exception with more explicit, add try with resources, StringBuilder instead of StringBuffer

2017-07-03 Thread Artem Ervits (JIRA)


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

Artem Ervits commented on OOZIE-2975:
-

all tests pass locally
{noformat}
mvn clean 
-Dtest=org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.jms.TestJMSJobEventListener,org.apache.oozie.action.hadoop.TestLauncherAM,org.apache.oozie.action.hadoop.TestHdfsOperations,org.apache.oozie.event.TestEventGeneration,testMemoryUsageAndSpeedOverflowToDisk,org.apache.oozie.service.TestPartitionDependencyManagerEhcache
 test -DtargetJavaVersion=1.8 -DjavaVersion=1.8
{noformat}

> code clean up in pig sharelib, replace Exception with more explicit, add try 
> with resources, StringBuilder instead of StringBuffer
> --
>
> Key: OOZIE-2975
> URL: https://issues.apache.org/jira/browse/OOZIE-2975
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-2975-0.patch
>
>
> 1. Replaced StringBuffer with StringBuilder
> 2. Replaced Exception with IOException and ExecException
> 3. Replaced old Hashmap notation with diamond notation
> 4. Added try-with-resources notation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

2017-07-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2969:
--

Testing JIRA OOZIE-2969

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:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:red}-1{color} patch does not compile
.{color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{color:green}+1{color} There are no new bugs found in total.
{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} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch


{color:red}*-1 Overall result, please check the reported -1(s)*{color}

{color:red}. There is at least one warning, please check{color}

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

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

> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2969-0.patch
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-07-03 Thread Apache Jenkins Server

See 


--
[...truncated 99.93 KB...]
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Share Lib Sqoop
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Examples
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Share Lib Spark
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Share Lib
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Docs
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie WebApp
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Tools
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie MiniOozie
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Server
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie Distro
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Apache Oozie ZooKeeper Security Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. FAILURE [  0.330 s]
[INFO] Apache Oozie Client  SKIPPED
[INFO] Apache Oozie Share Lib Oozie ... SKIPPED
[INFO] Apache Oozie Share Lib HCatalog  SKIPPED
[INFO] Apache Oozie Share Lib Distcp .. SKIPPED
[INFO] Apache Oozie Core .. SKIPPED
[INFO] Apache Oozie Share Lib Streaming ... SKIPPED
[INFO] Apache Oozie Share Lib Pig . SKIPPED
[INFO] Apache Oozie Share Lib Hive  SKIPPED
[INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
[INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
[INFO] Apache Oozie Examples .. SKIPPED
[INFO] Apache Oozie Share Lib Spark ... SKIPPED
[INFO] Apache Oozie Share Lib . SKIPPED
[INFO] Apache Oozie Docs .. SKIPPED
[INFO] Apache Oozie WebApp  SKIPPED
[INFO] Apache Oozie Tools . SKIPPED
[INFO] Apache Oozie MiniOozie . SKIPPED
[INFO] Apache Oozie Server  SKIPPED
[INFO] Apache Oozie Distro  SKIPPED
[INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED

[jira] [Updated] (OOZIE-2969) Drop support for Java 1.7

2017-07-03 Thread Artem Ervits (JIRA)


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

Artem Ervits updated OOZIE-2969:

Attachment: OOZIE-2969-0.patch

[~rkanter] ready for review pending jenkins

> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2969-0.patch
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-2977) error: self-closing element not allowed

2017-07-03 Thread Artem Ervits (JIRA)


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

Artem Ervits updated OOZIE-2977:

Attachment: OOZIE-2977-0.patch

> error: self-closing element not allowed
> ---
>
> Key: OOZIE-2977
> URL: https://issues.apache.org/jira/browse/OOZIE-2977
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2977-0.patch
>
>
> compiling with Java 1.8, javadoc throws the following errors
> {noformat}
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OOZIE-2977) error: self-closing element not allowed

2017-07-03 Thread Artem Ervits (JIRA)

Artem Ervits created OOZIE-2977:
---

 Summary: error: self-closing element not allowed
 Key: OOZIE-2977
 URL: https://issues.apache.org/jira/browse/OOZIE-2977
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.3.0
Reporter: Artem Ervits
Assignee: Artem Ervits
Priority: Trivial
 Fix For: 5.0.0


compiling with Java 1.8, javadoc throws the following errors
{noformat}
/Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
 error: self-closing element not allowed
/Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
 error: self-closing element not allowed
/Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
 error: self-closing element not allowed
/Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
 error: self-closing element not allowed
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-2854) Oozie should handle transient database problems

2017-07-03 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2854:

Attachment: OOZIE-2854.007.patch

Addressing review comments as well as line length, and header issues.

> Oozie should handle transient database problems
> ---
>
> Key: OOZIE-2854
> URL: https://issues.apache.org/jira/browse/OOZIE-2854
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Piros
> Attachments: OOZIE-2854-001.patch, OOZIE-2854-002.patch, 
> OOZIE-2854-003.patch, OOZIE-2854-004.patch, OOZIE-2854-005.patch, 
> OOZIE-2854.006.patch, OOZIE-2854.007.patch, OOZIE-2854-POC-001.patch
>
>
> There can be problems when Oozie cannot update the database properly. 
> Recently, we have experienced erratic behavior with two setups:
> * MySQL with the Galera cluster manager. Galera uses cluster-wide optimistic 
> locking which might cause a transaction to rollback if there are two or more 
> parallel transaction running and one of them cannot complete because of a 
> conflict.
> * MySQL with Percona XtraDB Cluster. If one of the MySQL instances is killed, 
> Oozie might get "Communications link failure" exception during the failover.
> The problem is that failed DB transactions later might cause a workflow 
> (which are started/re-started by RecoveryService) to get stuck. It's not 
> clear to us how this happens but it has to do with the fact that certain DB 
> updates are not executed.
> The solution is to use some sort of retry logic with exponential backoff if 
> the DB update fails. We could start with a 100ms wait time which is doubled 
> at every retry. The operation can be considered a failure if it still fails 
> after 10 attempts. These values could be configurable. We should discuss 
> initial values in the scope of this JIRA.
> Note that this solution is to handle *transient* failures. If the DB is down 
> for a longer period of time, we have to accept that the internal state of 
> Oozie is corrupted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 60544: OOZIE-2854 Oozie should handle transient database problems

2017-07-03 Thread András Piros


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

(Updated July 3, 2017, 3:15 p.m.)


Review request for oozie, Attila Sasvari, Peter Cseh, and Peter Bacsko.


Changes
---

Updated diff to reflect to review comments.


Repository: oozie-git


Description
---

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


Diffs (updated)
-

  core/pom.xml acddf349a89cf09a7fc4f384ebcaec56dfd0ab48 
  
core/src/main/java/org/apache/oozie/executor/jpa/JsonBeanPersisterExecutor.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/executor/jpa/QueryExecutor.java 
8d94c23e40d1281864db40e141b200ca207a6324 
  core/src/main/java/org/apache/oozie/service/JPAService.java 
028381d3b72bcc3b8c2cd27cacb3e0ac6d48d146 
  core/src/main/java/org/apache/oozie/sla/SLASummaryBean.java 
cfe1522a4b1f89085eb29e7f1281c2abd631bdc2 
  core/src/main/java/org/apache/oozie/store/WorkflowStore.java 
c565e74893b863caef6c93015cfe38fe520d04ec 
  core/src/main/java/org/apache/oozie/util/db/BasicDataSourceWrapper.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/util/db/DatabaseRetryPredicate.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/util/db/FailingHSQLDBDriverWrapper.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/util/db/FailingMySQLDriverWrapper.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/util/db/OperationRetryHandler.java 
PRE-CREATION 
  
core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
 PRE-CREATION 
  core/src/main/java/org/apache/oozie/util/db/RetryAttemptCounter.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/util/db/RuntimeExceptionInjector.java 
PRE-CREATION 
  core/src/main/resources/META-INF/persistence.xml 
bad9278597fcd4f93b4cc482afae8af14beaa922 
  core/src/main/resources/oozie-default.xml 
c60a4581a84d4c67a1ac1cf3dfdc252b85ccd01c 
  core/src/main/resources/oozie-log4j.properties 
c065f3cd4c5a3df1308b69d7c16e8fcfa8796efc 
  core/src/test/java/org/apache/oozie/test/XTestCase.java 
161927ac8f1132b3080d2924844826fcc7b807a5 
  
core/src/test/java/org/apache/oozie/util/db/TestOozieDmlStatementPredicate.java 
PRE-CREATION 
  core/src/test/java/org/apache/oozie/util/db/TestOperationRetryHandler.java 
PRE-CREATION 
  
core/src/test/java/org/apache/oozie/util/db/TestPersistenceExceptionSubclassFilterRetryPredicate.java
 PRE-CREATION 
  core/src/test/java/org/apache/oozie/util/db/TestRetryAttemptCounter.java 
PRE-CREATION 
  minitest/pom.xml 9515284bb5f32c279a93161c10e6571680e4f9fc 
  
minitest/src/test/java/org/apache/oozie/test/TestParallelJPAOperationRetries.java
 PRE-CREATION 
  minitest/src/test/java/org/apache/oozie/test/TestWorkflowRetries.java 
PRE-CREATION 
  minitest/src/test/java/org/apache/oozie/test/WorkflowTest.java 
2845f0af6efb9ef75fdbfcb326115c62e6fb3bdd 
  minitest/src/test/resources/hsqldb-oozie-site.xml 
fa5fe9c3185e973e8247d7bf10b126119d9c02c9 
  minitest/src/test/resources/oozie-log4j.properties 
c142d725140930bfa89cd2b163d0768a4c3a750a 
  minitest/src/test/resources/parallel-fs-and-shell.xml PRE-CREATION 
  minitest/src/test/resources/wf-test.xml 
20c4946862039a65c76ed7f49991345e90a694de 
  pom.xml 16c5137d44d7db891da46f80adb51c85e4c1b214 


Diff: https://reviews.apache.org/r/60544/diff/2/

Changes: https://reviews.apache.org/r/60544/diff/1-2/


Testing (updated)
---

Tests covered in code:

Unit tests
==

* testing the retry handler, the retry predicate filter, and parallel calls to 
JPA `EntityManager` (mostly Oozie database reads and writes) when injecting 
failures

Integration tests
=

* using the `MiniOozieTestCase` framework
* fixing it so that also asynchronous workflow applications (the ones that use 
`CallableQueueService`) can be run
* following workflow scenarios:
* a very simple one consisting only of a `` and an `` node
* a more sophisticated one consisting of multiple synchronous `` nodes and 
a `` node
* the ultimate one consisting of a `` node, and two branches of an 
`` and an asynchronous `` nodes

Test cases run:
```
mvn clean test 
-Dtest=TestOperationRetryHandler,TestPersistenceExceptionSubclassFilterRetryPredicate,TestParallelJPAOperationRetries,TestWorkflow,TestWorkflowRetries,TestJPAService,TestRetryAttemptCounter
```

Functional and stress tests performed on a 4-node MySQL cluster. MySQL daemon 
has been stopped / killed / restarted several times. Also firewall rules have 
been modified temporarily to simulate network outages.


Thanks,

András Piros

Re: Review Request 60544: OOZIE-2854 Oozie should handle transient database problems

2017-07-03 Thread András Piros



> On June 30, 2017, 2:27 p.m., Peter Bacsko wrote:
> > core/src/main/java/org/apache/oozie/service/JPAService.java
> > Lines 267 (patched)
> > 
> >
> > Do we need this? Usually this is done only once, when Oozie starts. If 
> > there's a problem during startup IMO it's good to know about it and fail.
> > 
> > Let's see other people's opinion.

For the unit tests' sake, and when there is a DB outage just in the moment when 
Oozie server restart / is redeployed, it's a must. The usual retry policies and 
logging apply for those cases as well - we surely will know when there is a 
temporary problem the retry logic can solve, or a permanent one.


> On June 30, 2017, 2:27 p.m., Peter Bacsko wrote:
> > core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java
> > Lines 43 (patched)
> > 
> >
> > Can't we move this under src/test ?

`FailingMySQLDriverWrapper` uses it, and it is needed for on-the-fly failure 
injection runtime.


> On June 30, 2017, 2:27 p.m., Peter Bacsko wrote:
> > core/src/main/java/org/apache/oozie/util/db/NestedRetryUtil.java
> > Lines 26 (patched)
> > 
> >
> > Let's add comments here and explain *properly* what this class does & 
> > why.

Renamed class and methods, as well as created test class that covers the 
functionality. Hope that helps.


> On June 30, 2017, 2:27 p.m., Peter Bacsko wrote:
> > core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
> > Lines 29 (patched)
> > 
> >
> > Does this work properly? The exception that we receive is always 
> > JPAExecutorException so these exceptions has to be extracted from it. I 
> > don't see any logic (or calls to getAllExceptions()) to do that.

Reimplemented and created new test cases to be sure the blacklisting works 
properly.


> On June 30, 2017, 2:27 p.m., Peter Bacsko wrote:
> > core/src/main/java/org/apache/oozie/util/db/RuntimeExceptionInjector.java
> > Lines 28 (patched)
> > 
> >
> > Another test code - can we move this to src/test ?

We need this here because we want to inject `PersistenceException` instances 
also at runtime, for functional and stress test purposes.


> On June 30, 2017, 2:27 p.m., Peter Bacsko wrote:
> > core/src/main/java/org/apache/oozie/util/db/RuntimeExceptionInjector.java
> > Lines 43 (patched)
> > 
> >
> > I don't think we need such a generic logic to throw exceptions or do 
> > we? For testing purposes, it's more than enough to throw a specific 
> > exception I guess.

It's reusable and we may end up adding more `Exception` subclasses for 
functional testing purposes, e.g. for another DB type.


- András


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


On June 29, 2017, 4:35 p.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60544/
> ---
> 
> (Updated June 29, 2017, 4:35 p.m.)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Cseh, and Peter Bacsko.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2854
> 
> 
> Diffs
> -
> 
>   core/pom.xml acddf349a89cf09a7fc4f384ebcaec56dfd0ab48 
>   core/src/main/java/org/apache/oozie/ErrorCode.java 
> 662e1edc9c4b23b3606c751bf5ed4b531ee7ac62 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/JsonBeanPersisterExecutor.java
>  PRE-CREATION 
>   core/src/main/java/org/apache/oozie/executor/jpa/QueryExecutor.java 
> 8d94c23e40d1281864db40e141b200ca207a6324 
>   core/src/main/java/org/apache/oozie/service/JPAService.java 
> 028381d3b72bcc3b8c2cd27cacb3e0ac6d48d146 
>   core/src/main/java/org/apache/oozie/sla/SLASummaryBean.java 
> cfe1522a4b1f89085eb29e7f1281c2abd631bdc2 
>   core/src/main/java/org/apache/oozie/store/WorkflowStore.java 
> c565e74893b863caef6c93015cfe38fe520d04ec 
>   core/src/main/java/org/apache/oozie/util/db/BasicDataSourceWrapper.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/util/db/DBOperationRetryHandler.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/util/db/DatabaseRetryPredicate.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java 
> PRE-CREATION 
>

[jira] [Commented] (OOZIE-2956) Fix Findbugs warnings related to reliance on default encoding in oozie-core

2017-07-03 Thread Jan Hentschel (JIRA)


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

Jan Hentschel commented on OOZIE-2956:
--

Failing test passes locally. Maybe we can run the build again.

> Fix Findbugs warnings related to reliance on default encoding in oozie-core
> ---
>
> Key: OOZIE-2956
> URL: https://issues.apache.org/jira/browse/OOZIE-2956
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, core
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
> Attachments: OOZIE-2956-1.patch, OOZIE-2956-2.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-core* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.StringBlob.getRawBlob(): String.getBytes() 
> [org.apache.oozie.StringBlob] At StringBlob.java:[line 119]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ActionExecutor.registerError(String, 
> ActionExecutorException$ErrorType, String): 
> java.io.ByteArrayOutputStream.toString() 
> [org.apache.oozie.action.ActionExecutor] At ActionExecutor.java:[line 354]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ActionExecutor.registerError(String, 
> ActionExecutorException$ErrorType, String): new 
> java.io.PrintStream(OutputStream) [org.apache.oozie.action.ActionExecutor] At 
> ActionExecutor.java:[line 353]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper.getRecoveryId(Configuration, 
> Path, String): new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.hadoop.LauncherHelper] At LauncherHelper.java:[line 
> 69]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper.getTag(String): 
> String.getBytes() [org.apache.oozie.action.hadoop.LauncherHelper] At 
> LauncherHelper.java:[line 160]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper$1.run(): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1] At LauncherHelper.java:[line 
> 271]Another occurrence at LauncherHelper.java:[line 277]Another occurrence at 
> LauncherHelper.java:[line 285]Another occurrence at LauncherHelper.java:[line 
> 293]Another occurrence at LauncherHelper.java:[line 299]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.MapReduceActionExecutor.end(ActionExecutor$Context,
>  WorkflowAction): String.getBytes() 
> [org.apache.oozie.action.hadoop.MapReduceActionExecutor] At 
> MapReduceActionExecutor.java:[line 250]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.SqoopActionExecutor.end(ActionExecutor$Context,
>  WorkflowAction): String.getBytes() 
> [org.apache.oozie.action.hadoop.SqoopActionExecutor] At 
> SqoopActionExecutor.java:[line 186]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ssh.SshActionExecutor.drainBuffers(Process, 
> StringBuffer, StringBuffer, int): new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.ssh.SshActionExecutor, 
> org.apache.oozie.action.ssh.SshActionExecutor] At 
> SshActionExecutor.java:[line 684]Another occurrence at 
> SshActionExecutor.java:[line 685]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ssh.SshActionExecutor.initSshScripts(): new 
> java.io.FileWriter(String) [org.apache.oozie.action.ssh.SshActionExecutor, 
> org.apache.oozie.action.ssh.SshActionExecutor] At 
> SshActionExecutor.java:[line 502]Another occurrence at 
> SshActionExecutor.java:[line 504]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.bundle.BundleSubmitXCommand.readDefinition(String): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.command.bundle.BundleSubmitXCommand] At 
> BundleSubmitXCommand.java:[line 322]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.coord.CoordSubmitXCommand.readDefinition(String): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.command.coord.CoordSubmitXCommand] At 
> CoordSubmitXCommand.java:[line 1193]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.coord.CoordUpdateXCommand.getDiffinGitFormat(String, 
> String): java.io.ByteArrayOutputStream.toString() 
> [org.apache.oozie.command.coord.CoordUpdateXCommand] At 
> CoordUpdateXCommand.java:[line 203]
> [INFO] Found reliance on default encoding in 
>

[jira] Subscription: Oozie Patch Available

2017-07-03 Thread jira

Issue Subscription
Filter: Oozie Patch Available (107 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2974  Change TestLiteWorkflowAppParser so that it works with Hadoop 3
https://issues.apache.org/jira/browse/OOZIE-2974
OOZIE-2964  getting at 
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
https://issues.apache.org/jira/browse/OOZIE-2964
OOZIE-2963  getting error in build ArtifactNotFoundException: Could not find 
artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
https://issues.apache.org/jira/browse/OOZIE-2963
OOZIE-2962  bump maven-javadoc-plugin to 2.10.4
https://issues.apache.org/jira/browse/OOZIE-2962
OOZIE-2961  build contains multiple warnings for is not a parameter name
https://issues.apache.org/jira/browse/OOZIE-2961
OOZIE-2960  many warnings for @return tag has no arguments
https://issues.apache.org/jira/browse/OOZIE-2960
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2931  multiple warnings during build for "no @param for"
https://issues.apache.org/jira/browse/OOZIE-2931
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2918  Delete LauncherMapper and its test
https://issues.apache.org/jira/browse/OOZIE-2918
OOZIE-2916  Set a job name for the MR Action's child job
https://issues.apache.org/jira/browse/OOZIE-2916
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2911  Re-add test testWfActionKillChildJob and adapt it to OYA
https://issues.apache.org/jira/browse/OOZIE-2911
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2854  Oozie should handle transient database problems
https://issues.apache.org/jira/browse/OOZIE-2854
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues.apache.org/jira/browse/OOZIE-2829
OOZIE-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues.apache.org/jira/browse/OOZIE-2826
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password

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

[jira] [Commented] (OOZIE-2977) error: self-closing element not allowed

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

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

[jira] [Commented] (OOZIE-2854) Oozie should handle transient database problems

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

[jira] [Updated] (OOZIE-2969) Drop support for Java 1.7

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

[jira] [Commented] (OOZIE-2975) code clean up in pig sharelib, replace Exception with more explicit, add try with resources, StringBuilder instead of StringBuffer

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

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

[jira] [Updated] (OOZIE-2969) Drop support for Java 1.7

[jira] [Updated] (OOZIE-2977) error: self-closing element not allowed

[jira] [Created] (OOZIE-2977) error: self-closing element not allowed

[jira] [Updated] (OOZIE-2854) Oozie should handle transient database problems

Re: Review Request 60544: OOZIE-2854 Oozie should handle transient database problems

Re: Review Request 60544: OOZIE-2854 Oozie should handle transient database problems

[jira] [Commented] (OOZIE-2956) Fix Findbugs warnings related to reliance on default encoding in oozie-core

[jira] Subscription: Oozie Patch Available

19 matches

Site Navigation

Mail list logo

Footer information