[jira] [Commented] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-3071:
--

Testing JIRA OOZIE-3071

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 77 Javadoc warning(s)
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{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/PreCommit-OOZIE-Build/57/

> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than 
> Spark 2.2.0
> 
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
>  Labels: patch
> Attachments: OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5. 
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at 
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

Failed: OOZIE-3071 PreCommit Build #57

2017-09-28 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/OOZIE-3071
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/57/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.00 MB...]
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
-1 COMPILE
+1 HEAD compiles
-1 patch does not compile
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS - patch does not compile, cannot run testcases
-1 DISTRO
-1 distro tarball fails with the patch


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/57/

  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 3706k0 130320 0  22125  0  0:02:51 --:--:--  0:02:51 
22125100 3706k  100 3706k0 0  4856k  0 --:--:-- --:--:-- --:--:-- 
20.7M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3071
Archiving artifacts
[Fast Archiver] Compressed 1.16 MB of artifacts by 48.6% relative to #54
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Ran Gu (JIRA) 

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

Ran Gu commented on OOZIE-3071:
---

Not sure why "patch failed to apply to head of branch". Recreated patch against 
Oozie branch-4.3

> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than 
> Spark 2.2.0
> 
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
>  Labels: patch
> Attachments: OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5. 
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at 
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

[jira] [Updated] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Ran Gu (JIRA) 

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

Ran Gu updated OOZIE-3071:
--
Attachment: (was: OOZIE-3071.patch)

> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than 
> Spark 2.2.0
> 
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
>  Labels: patch
> Attachments: OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5. 
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at 
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

[jira] [Updated] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Ran Gu (JIRA) 

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

Ran Gu updated OOZIE-3071:
--
Attachment: OOZIE-3071.patch

> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than 
> Spark 2.2.0
> 
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
>  Labels: patch
> Attachments: OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5. 
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at 
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

[jira] [Commented] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-3071:
--

Testing JIRA OOZIE-3071

Cleaning local git workspace



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



> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than 
> Spark 2.2.0
> 
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
>  Labels: patch
> Attachments: OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5. 
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at 
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

Failed: OOZIE-3071 PreCommit Build #56

2017-09-28 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/OOZIE-3071
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/56/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 674.90 KB...]
[INFO] Apache Oozie Docs .. SUCCESS [  4.898 s]
[INFO] Apache Oozie WebApp  SUCCESS [  3.409 s]
[INFO] Apache Oozie Tools . SUCCESS [ 17.641 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  2.817 s]
[INFO] Apache Oozie Server  SUCCESS [ 14.131 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.282 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  4.405 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 04:41 min
[INFO] Finished at: 2017-09-28T21:08:09Z
[INFO] Final Memory: 620M/1729M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch a/pom.xml => b/pom.xml...
error: a/pom.xml: No such file or directory
Checking patch a/sharelib/hive2/pom.xml => b/sharelib/hive2/pom.xml...
error: a/sharelib/hive2/pom.xml: No such file or directory
Checking patch a/sharelib/spark/pom.xml => b/sharelib/spark/pom.xml...
error: a/sharelib/spark/pom.xml: No such file or directory
Checking patch pom.xml...
Checking patch sharelib/hive2/pom.xml...
error: while searching for:

org.apache.commons
commons-lang3


jline 

error: patch failed: sharelib/hive2/pom.xml:214
error: sharelib/hive2/pom.xml: patch does not apply
Checking patch sharelib/spark/pom.xml...
Patch failed to apply to head of branch

  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  4429k  0 --:--:-- --:--:-- --:--:-- 8952k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3071
Archiving artifacts
[Fast Archiver] Compressed 839.46 KB of artifacts by 68.6% relative to #54
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Ran Gu (JIRA) 

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

Ran Gu commented on OOZIE-3071:
---

[~dbist13] Updating commons-lang3 to 3.5 in Oozie top level pom.xml breaks 
hive2 (mvn clean install would fail). Seems to me Hive2 is using commons-lang3 
version 3.3.2 where Spark is using commons-lang3 version 3.5.

> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than 
> Spark 2.2.0
> 
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
> Attachments: OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5. 
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at 
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

[jira] [Commented] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Artem Ervits (JIRA) 

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

Artem Ervits commented on OOZIE-3071:
-

[~rangu] why not just bump commons-lang3 to 3.5 and not add a second one in 
hive sharelib? In case it does need it, why not just remove the version all 
together from sharelib pom and leave it only in main?

> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than 
> Spark 2.2.0
> 
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
> Attachments: OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5. 
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at 
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

[jira] [Updated] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Ran Gu (JIRA) 

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

Ran Gu updated OOZIE-3071:
--
Attachment: OOZIE-3071.patch

Attached patch for fixing this issue

> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than 
> Spark 2.2.0
> 
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
> Attachments: OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5. 
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at 
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at 
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at 
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at 
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

[jira] [Created] (OOZIE-3071) Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0

2017-09-28 Thread Ran Gu (JIRA) 
Ran Gu created OOZIE-3071:
-

 Summary: Oozie 4.3 Spark sharelib ueses a different version of 
commons-lang3 than Spark 2.2.0
 Key: OOZIE-3071
 URL: https://issues.apache.org/jira/browse/OOZIE-3071
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.0
Reporter: Ran Gu


Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
Spark 2.2.0 uses commons-lang3 version 3.5. 
This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.

Error message:
17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: 
java.lang.IllegalArgumentException: Illegal pattern component: XXX
java.lang.IllegalArgumentException: Illegal pattern component: XXX
at 
org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
at org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
at 
org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
at org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
at org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
at 
org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
at 
org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) 



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

[jira] [Commented] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Bacsko (JIRA) 

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

Peter Bacsko commented on OOZIE-3070:
-

Thanks - I'll commit this tomorrow.

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch, 
> OOZIE-3070-003.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

[jira] [Commented] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Cseh (JIRA) 

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

Peter Cseh commented on OOZIE-3070:
---

Test failure is due {code}  
testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation): 
java.lang.OutOfMemoryError: Java heap space
{code} which seems unrelated.
So +1

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch, 
> OOZIE-3070-003.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

Failed: OOZIE-3070 PreCommit Build #55

2017-09-28 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/OOZIE-3070
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/55/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.60 MB...]
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2032
Tests failed: 0
Tests errors: 1

The patch failed the following testcases:

  

Tests failing with errors:
  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/55/

  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  4107k  0 --:--:-- --:--:-- --:--:-- 5466k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3070
Archiving artifacts
[Fast Archiver] Compressed 1.80 MB of artifacts by 60.7% relative to #54
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation

Error Message:
java.lang.OutOfMemoryError: Java heap space

Stack Trace:
com.sun.tools.attach.AttachOperationFailedException: 
java.lang.OutOfMemoryError: Java heap space
at 
sun.tools.attach.LinuxVirtualMachine.execute(LinuxVirtualMachine.java:229)
at 
sun.tools.attach.HotSpotVirtualMachine.executeCommand(HotSpotVirtualMachine.java:261)
at 
sun.tools.attach.HotSpotVirtualMachine.getSystemProperties(HotSpotVirtualMachine.java:144)
at 
org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation(TestMetricsInstrumentation.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

[jira] [Commented] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-3070:
--

Testing JIRA OOZIE-3070

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 4 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 77 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{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
{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: 2032
.Tests failed: 0
.Tests errors: 1

.The patch failed the following testcases:

.  

.Tests failing with errors:
.  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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

{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/PreCommit-OOZIE-Build/55/

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch, 
> OOZIE-3070-003.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

Re: Review Request 62459: OOZIE-2296: Add an Oozie diagnostic bundle tool

2017-09-28 Thread Peter Cseh 

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




tools/src/main/java/org/apache/oozie/tools/diag/ArgParser.java
Lines 36 (patched)


Shouldn't this make the findbugs warnings go away?


- Peter Cseh


On Sept. 27, 2017, 2:12 p.m., Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62459/
> ---
> 
> (Updated Sept. 27, 2017, 2:12 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> A diagnostic tool that collects a bunch of job and other information from 
> Oozie in a zip file.
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 
> d4047671876dcc3279a2ec379bc1d003f5e6f1aa 
>   pom.xml efccc346932514ada578a3462eb3c3cfe519a323 
>   tools/pom.xml 7306a14e7b237977be00f8fe28e34573540fd508 
>   tools/src/main/bin/oozie-diag-bundle-collector.sh PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/AppInfoCollector.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/ArgParser.java PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleCollectorDriver.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleCompressor.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleEntryWriter.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/Client.java PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/MetricsCollector.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/ServerInfoCollector.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestAppInfoCollector.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestArgParser.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestMetricsCollector.java 
> PRE-CREATION 
>   
> tools/src/test/java/org/apache/oozie/tools/diag/TestServerInfoCollector.java 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62459/diff/7/
> 
> 
> Testing
> ---
> 
> - new unit tests: TestOozieDiagBundleCollector
> - started Oozie with a pseudo hadoop cluster, submitted a couple workflows, 
> and executed the following commands: 
> -- ``bin/oozie-diag-bundle-collector.sh`` (usage info printed),
> -- ``bin/oozie-diag-bundle-collector.sh  -numworkflows 2000 -oozie 
> http://localhost:11000/oozie -output /tmp``, 
> -- ``bin/oozie-diag-bundle-collector.sh  -jobs 
> 001-170918144116149-oozie-asas-W -oozie http://localhost:11000/oozie 
> -output .`` (verified zip the tool generated).
> 
> 
> Thanks,
> 
> Attila Sasvari
> 
>

Re: Review Request 62459: OOZIE-2296: Add an Oozie diagnostic bundle tool

2017-09-28 Thread Peter Cseh 

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




tools/src/test/java/org/apache/oozie/tools/diag/TestAppInfoCollector.java
Lines 1 (patched)


License



tools/src/test/java/org/apache/oozie/tools/diag/TestServerInfoCollector.java
Lines 1 (patched)


License


- Peter Cseh


On Sept. 27, 2017, 2:12 p.m., Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62459/
> ---
> 
> (Updated Sept. 27, 2017, 2:12 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> A diagnostic tool that collects a bunch of job and other information from 
> Oozie in a zip file.
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 
> d4047671876dcc3279a2ec379bc1d003f5e6f1aa 
>   pom.xml efccc346932514ada578a3462eb3c3cfe519a323 
>   tools/pom.xml 7306a14e7b237977be00f8fe28e34573540fd508 
>   tools/src/main/bin/oozie-diag-bundle-collector.sh PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/AppInfoCollector.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/ArgParser.java PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleCollectorDriver.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleCompressor.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleEntryWriter.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/Client.java PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/MetricsCollector.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/ServerInfoCollector.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestAppInfoCollector.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestArgParser.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestMetricsCollector.java 
> PRE-CREATION 
>   
> tools/src/test/java/org/apache/oozie/tools/diag/TestServerInfoCollector.java 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62459/diff/7/
> 
> 
> Testing
> ---
> 
> - new unit tests: TestOozieDiagBundleCollector
> - started Oozie with a pseudo hadoop cluster, submitted a couple workflows, 
> and executed the following commands: 
> -- ``bin/oozie-diag-bundle-collector.sh`` (usage info printed),
> -- ``bin/oozie-diag-bundle-collector.sh  -numworkflows 2000 -oozie 
> http://localhost:11000/oozie -output /tmp``, 
> -- ``bin/oozie-diag-bundle-collector.sh  -jobs 
> 001-170918144116149-oozie-asas-W -oozie http://localhost:11000/oozie 
> -output .`` (verified zip the tool generated).
> 
> 
> Thanks,
> 
> Attila Sasvari
> 
>

Re: Review Request 62459: OOZIE-2296: Add an Oozie diagnostic bundle tool

2017-09-28 Thread Peter Cseh 

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




tools/src/main/java/org/apache/oozie/tools/diag/AppInfoCollector.java
Lines 164 (patched)


Please log here that Launcher logs will be missing for this reason.


- Peter Cseh


On Sept. 27, 2017, 2:12 p.m., Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62459/
> ---
> 
> (Updated Sept. 27, 2017, 2:12 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> A diagnostic tool that collects a bunch of job and other information from 
> Oozie in a zip file.
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 
> d4047671876dcc3279a2ec379bc1d003f5e6f1aa 
>   pom.xml efccc346932514ada578a3462eb3c3cfe519a323 
>   tools/pom.xml 7306a14e7b237977be00f8fe28e34573540fd508 
>   tools/src/main/bin/oozie-diag-bundle-collector.sh PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/AppInfoCollector.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/ArgParser.java PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleCollectorDriver.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleCompressor.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/BundleEntryWriter.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/Client.java PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/MetricsCollector.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/diag/ServerInfoCollector.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestAppInfoCollector.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestArgParser.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/diag/TestMetricsCollector.java 
> PRE-CREATION 
>   
> tools/src/test/java/org/apache/oozie/tools/diag/TestServerInfoCollector.java 
> PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62459/diff/7/
> 
> 
> Testing
> ---
> 
> - new unit tests: TestOozieDiagBundleCollector
> - started Oozie with a pseudo hadoop cluster, submitted a couple workflows, 
> and executed the following commands: 
> -- ``bin/oozie-diag-bundle-collector.sh`` (usage info printed),
> -- ``bin/oozie-diag-bundle-collector.sh  -numworkflows 2000 -oozie 
> http://localhost:11000/oozie -output /tmp``, 
> -- ``bin/oozie-diag-bundle-collector.sh  -jobs 
> 001-170918144116149-oozie-asas-W -oozie http://localhost:11000/oozie 
> -output .`` (verified zip the tool generated).
> 
> 
> Thanks,
> 
> Attila Sasvari
> 
>

[jira] [Comment Edited] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Cseh (JIRA) 

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

Peter Cseh edited comment on OOZIE-3070 at 9/28/17 2:02 PM:


+1 (pending Jenkins)
Thanks for getting rid a of a 9 year old dependency! Jetty 6.1.14 was releases 
in late 2008.


was (Author: gezapeti):
+1 (pending Jenkins)

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch, 
> OOZIE-3070-003.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

[jira] [Commented] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Cseh (JIRA) 

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

Peter Cseh commented on OOZIE-3070:
---

+1 (pending Jenkins)

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch, 
> OOZIE-3070-003.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

[jira] [Commented] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Andras Piros (JIRA) 

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

Andras Piros commented on OOZIE-3070:
-

+1 (non-binding)

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch, 
> OOZIE-3070-003.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

Re: Review Request 62660: OOZIE-3070 Remove references to org.mortbay.jetty

2017-09-28 Thread András Piros 

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


Ship it!




Ship It!

- András Piros


On Sept. 28, 2017, 1:54 p.m., Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62660/
> ---
> 
> (Updated Sept. 28, 2017, 1:54 p.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-3070
> 
> 
> Diffs
> -
> 
>   core/pom.xml b0809546d 
>   core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
> eeb7717c9 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAMCallbackNotifier.java
>  1f7e5b221 
>   core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 6fcdf24bc 
>   
> core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
>  ef342a4e4 
>   pom.xml efccc3469 
>   sharelib/hive2/pom.xml b74e51a34 
>   sharelib/spark/pom.xml eb80439a4 
> 
> 
> Diff: https://reviews.apache.org/r/62660/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

[jira] [Updated] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Bacsko (JIRA) 

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

Peter Bacsko updated OOZIE-3070:

Attachment: OOZIE-3070-003.patch

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch, 
> OOZIE-3070-003.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

Re: Review Request 62660: OOZIE-3070 Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Bacsko 

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

(Updated szept. 28, 2017, 1:54 du)


Review request for oozie and András Piros.


Changes
---

Addressing comments


Repository: oozie-git


Description
---

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


Diffs (updated)
-

  core/pom.xml b0809546d 
  core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
eeb7717c9 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAMCallbackNotifier.java
 1f7e5b221 
  core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 6fcdf24bc 
  
core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
 ef342a4e4 
  pom.xml efccc3469 
  sharelib/hive2/pom.xml b74e51a34 
  sharelib/spark/pom.xml eb80439a4 


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

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


Testing
---


Thanks,

Peter Bacsko

Re: Review Request 62660: OOZIE-3070 Remove references to org.mortbay.jetty

2017-09-28 Thread András Piros 

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




core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
Lines 51-53 (patched)


If possible, I'm better off w/ a non-`static` solution.



core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
Lines 80 (patched)


If possible, I'm better off w/ a non-`static` solution.


- András Piros


On Sept. 28, 2017, 11:25 a.m., Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62660/
> ---
> 
> (Updated Sept. 28, 2017, 11:25 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-3070
> 
> 
> Diffs
> -
> 
>   core/pom.xml b0809546d 
>   core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
> eeb7717c9 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAMCallbackNotifier.java
>  1f7e5b221 
>   core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 6fcdf24bc 
>   
> core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
>  ef342a4e4 
>   pom.xml efccc3469 
>   sharelib/hive2/pom.xml b74e51a34 
>   sharelib/spark/pom.xml eb80439a4 
> 
> 
> Diff: https://reviews.apache.org/r/62660/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

[jira] [Commented] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Cseh (JIRA) 

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

Peter Cseh commented on OOZIE-3070:
---

+1

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

Re: Review Request 62660: OOZIE-3070 Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Cseh 

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


Ship it!




Ship It!

- Peter Cseh


On Sept. 28, 2017, 11:25 a.m., Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62660/
> ---
> 
> (Updated Sept. 28, 2017, 11:25 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-3070
> 
> 
> Diffs
> -
> 
>   core/pom.xml b0809546d 
>   core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
> eeb7717c9 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAMCallbackNotifier.java
>  1f7e5b221 
>   core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 6fcdf24bc 
>   
> core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
>  ef342a4e4 
>   pom.xml efccc3469 
>   sharelib/hive2/pom.xml b74e51a34 
>   sharelib/spark/pom.xml eb80439a4 
> 
> 
> Diff: https://reviews.apache.org/r/62660/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

Re: Review Request 62660: OOZIE-3070 Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Bacsko 


> On szept. 28, 2017, 12:49 du, Peter Cseh wrote:
> > core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java
> > Lines 1-6 (original), 1-6 (patched)
> > 
> >
> > Can we move this class to src/test? We could then make the 
> > jetty-servlet a test-time dependency only.

Needed by LocalOozie, which is also under src/main. LocalOozie is referenced in 
oozie-examples.


- Peter


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


On szept. 28, 2017, 11:25 de, Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62660/
> ---
> 
> (Updated szept. 28, 2017, 11:25 de)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-3070
> 
> 
> Diffs
> -
> 
>   core/pom.xml b0809546d 
>   core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
> eeb7717c9 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAMCallbackNotifier.java
>  1f7e5b221 
>   core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 6fcdf24bc 
>   
> core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
>  ef342a4e4 
>   pom.xml efccc3469 
>   sharelib/hive2/pom.xml b74e51a34 
>   sharelib/spark/pom.xml eb80439a4 
> 
> 
> Diff: https://reviews.apache.org/r/62660/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

Re: Review Request 62660: OOZIE-3070 Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Cseh 

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




core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java
Lines 1-6 (original), 1-6 (patched)


Can we move this class to src/test? We could then make the jetty-servlet a 
test-time dependency only.


- Peter Cseh


On Sept. 28, 2017, 11:25 a.m., Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62660/
> ---
> 
> (Updated Sept. 28, 2017, 11:25 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-3070
> 
> 
> Diffs
> -
> 
>   core/pom.xml b0809546d 
>   core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
> eeb7717c9 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAMCallbackNotifier.java
>  1f7e5b221 
>   core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 6fcdf24bc 
>   
> core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
>  ef342a4e4 
>   pom.xml efccc3469 
>   sharelib/hive2/pom.xml b74e51a34 
>   sharelib/spark/pom.xml eb80439a4 
> 
> 
> Diff: https://reviews.apache.org/r/62660/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

Re: Review Request 62660: OOZIE-3070 Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Bacsko 

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




core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
Lines 62-63 (original), 70-89 (patched)


There was a race condition in the test. Since the variables inside 
CallbackServlet are modified on a separate thread, the test failed randomly.



sharelib/hive2/pom.xml
Lines 47-50 (patched)


Note: I'm not sure we have to do this upstream, probably not - we 
definitely need to do this in CDH.



sharelib/spark/pom.xml
Lines 201-206 (patched)


Same as above


- Peter Bacsko


On szept. 28, 2017, 11:25 de, Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62660/
> ---
> 
> (Updated szept. 28, 2017, 11:25 de)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-3070
> 
> 
> Diffs
> -
> 
>   core/pom.xml b0809546d 
>   core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
> eeb7717c9 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAMCallbackNotifier.java
>  1f7e5b221 
>   core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 6fcdf24bc 
>   
> core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
>  ef342a4e4 
>   pom.xml efccc3469 
>   sharelib/hive2/pom.xml b74e51a34 
>   sharelib/spark/pom.xml eb80439a4 
> 
> 
> Diff: https://reviews.apache.org/r/62660/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

Review Request 62660: OOZIE-3070 Remove references to org.mortbay.jetty

2017-09-28 Thread Peter Bacsko 

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

Review request for oozie and András Piros.


Repository: oozie-git


Description
---

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


Diffs
-

  core/pom.xml b0809546d 
  core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
eeb7717c9 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAMCallbackNotifier.java
 1f7e5b221 
  core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 6fcdf24bc 
  
core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java
 ef342a4e4 
  pom.xml efccc3469 
  sharelib/hive2/pom.xml b74e51a34 
  sharelib/spark/pom.xml eb80439a4 


Diff: https://reviews.apache.org/r/62660/diff/1/


Testing
---


Thanks,

Peter Bacsko

[jira] [Commented] (OOZIE-3070) Remove references to org.mortbay.jetty

2017-09-28 Thread Andras Piros (JIRA) 

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

Andras Piros commented on OOZIE-3070:
-

[~pbacsko] thanks for the patch! Can you please put that to ReviewBoard?

> Remove references to org.mortbay.jetty
> --
>
> Key: OOZIE-3070
> URL: https://issues.apache.org/jira/browse/OOZIE-3070
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-3070-001.patch, OOZIE-3070-002.patch
>
>
> A couple of months ago we migrated from Tomcat to Jetty.
> However, Oozie as a production code uses {{org.eclipse.jetty}}, whereas 
> {{EmbeddedServletContainer}} still uses code from {{org.mortbay.jetty}}. We 
> don't need two Jettys, so all remaining code should use the newest Jetty.



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

[jira] Subscription: Oozie Patch Available

2017-09-28 Thread jira 
Issue Subscription
Filter: Oozie Patch Available (107 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3070  Remove references to org.mortbay.jetty
https://issues.apache.org/jira/browse/OOZIE-3070
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-3031  Coord job with only unresolved dependencies doesn't timeout
https://issues.apache.org/jira/browse/OOZIE-3031
OOZIE-3022  fix for warning has no file and won't be listed in dependency files 
details
https://issues.apache.org/jira/browse/OOZIE-3022
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-3001  core library has many instances of warnings with trailing spaces 
and lines longer than 132 chars
https://issues.apache.org/jira/browse/OOZIE-3001
OOZIE-2997  files contain trailing white spaces in client lib
https://issues.apache.org/jira/browse/OOZIE-2997
OOZIE-2996  add option for -UseGCOverheadLimit to maven opts as sometimes local 
testing fails
https://issues.apache.org/jira/browse/OOZIE-2996
OOZIE-2978  Remove code that handles Pig versions before 0.8 
https://issues.apache.org/jira/browse/OOZIE-2978
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-2969  Drop support for Java 1.7
https://issues.apache.org/jira/browse/OOZIE-2969
OOZIE-2964  Add -Xdoclint:none to javadoc opts to avoid warnings
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-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-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
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-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
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-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