[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (94 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3432  When use configuration oozie.service.ProxyUserService.root.hosts, 
oozie-error.log shows Invalid configuration defined
https://issues.apache.org/jira/browse/OOZIE-3432
OOZIE-3418  Upgrade to Guava 27
https://issues.apache.org/jira/browse/OOZIE-3418
OOZIE-3409  Oozie Server : Memory leak in EL evaluation
https://issues.apache.org/jira/browse/OOZIE-3409
OOZIE-3404  The env variable of SPARK_HOME needs to be set when running pySpark
https://issues.apache.org/jira/browse/OOZIE-3404
OOZIE-3395  Findbugs is no longer maintained
https://issues.apache.org/jira/browse/OOZIE-3395
OOZIE-3375  Can't use empty  in coordinator
https://issues.apache.org/jira/browse/OOZIE-3375
OOZIE-3367  Using && in EL expressions in oozie bundle.xml files generates 
parse errors
https://issues.apache.org/jira/browse/OOZIE-3367
OOZIE-3366  Update workflow status and subworkflow status on suspend command
https://issues.apache.org/jira/browse/OOZIE-3366
OOZIE-3364  Rerunning Oozie bundle jobs starts the coordinators in 
indeterminate order
https://issues.apache.org/jira/browse/OOZIE-3364
OOZIE-3362  When killed, SSH action should kill the spawned processes on target 
host
https://issues.apache.org/jira/browse/OOZIE-3362
OOZIE-3326  Sqoop Action should support tez delegation tokens for hive-import
https://issues.apache.org/jira/browse/OOZIE-3326
OOZIE-3320  Oozie ShellAction should support absolute bash file path
https://issues.apache.org/jira/browse/OOZIE-3320
OOZIE-3319  Log SSH action callback error output
https://issues.apache.org/jira/browse/OOZIE-3319
OOZIE-3301  Update NOTICE file
https://issues.apache.org/jira/browse/OOZIE-3301
OOZIE-3274  Remove slf4j
https://issues.apache.org/jira/browse/OOZIE-3274
OOZIE-3266  Coord action rerun support RERUN_SKIP_NODES option
https://issues.apache.org/jira/browse/OOZIE-3266
OOZIE-3265  properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to 
appear together
https://issues.apache.org/jira/browse/OOZIE-3265
OOZIE-3261  [build] Set up mvn clean to delete the "build" directory as well
https://issues.apache.org/jira/browse/OOZIE-3261
OOZIE-3256  refactor OozieCLI class
https://issues.apache.org/jira/browse/OOZIE-3256
OOZIE-3249  [tools] Instrumentation log parser
https://issues.apache.org/jira/browse/OOZIE-3249
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
OOZIE-3196  Authorization: restrict world readability by user
https://issues.apache.org/jira/browse/OOZIE-3196
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3137  Add support for log4j2 in HiveMain
https://issues.apache.org/jira/browse/OOZIE-3137
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
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-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
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-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-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784

[jira] [Commented] (OOZIE-3326) Sqoop Action should support tez delegation tokens for hive-import

[Denes Bodo (JIRA)]

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

Denes Bodo commented on OOZIE-3326:
---

Thanks [~asalamon74] for your comments and help.

> Sqoop Action should support tez delegation tokens for hive-import
> -
>
> Key: OOZIE-3326
> URL: https://issues.apache.org/jira/browse/OOZIE-3326
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Brian Goerlitz
>Assignee: Brian Goerlitz
>Priority: Major
> Attachments: OOZIE-3326_003.patch, OOZIE-3326_004.patch, 
> OOZIE-3326_005.patch, OOZIE-3326_006.patch, OOZIE-3326_007.patch, 
> OZIE-3326_001.patch, OZIE-3326_002.patch
>
>
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> At present, hive-import will fail to start a tez session in secure 
> environment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 68317: Sqoop Action should support tez delegation tokens for hive-import

[Peter Bacsko via Review Board]

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




sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java
Lines 94-96 (patched)


I think we already support Java8, so it can be a good practice to use 
lambdas. 

I recently faced a similar problem with System.getEnv(), I think this 
solution should be considered because it's more compact:

```
import java.util.function.Function;
...
private static Function envProvider = System::getenv;
...
@VisibleForTesting
static void setEnvProvider(Function envProvider) {
LauncherAM.envProvider = envProvider;
}
...
String envValue = envProvider.apply(key);
```

Then in the test code, you can just override like that:

```
LauncherAM.setEnvProvider(s -> { return dummyEnv.get(s); });
```

So we don't need that tiny helper class, just replace the method reference 
with a new one.



sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/SystemEnvironment.java
Lines 25 (patched)


See my comment at LauncherAM.java - this can be eliminated.


- Peter Bacsko


On febr. 15, 2019, 11:33 de, Denes Bodo wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68317/
> ---
> 
> (Updated febr. 15, 2019, 11:33 de)
> 
> 
> Review request for oozie and Andras Salamon.
> 
> 
> Bugs: OOZIE-3326
> https://issues.apache.org/jira/browse/OOZIE-3326
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> 
> At present, hive-import will fail to start a tez session in secure 
> environment.
> 
> 
> Diffs
> -
> 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
> 63afd91d3 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
> b6599f7f3 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/SystemEnvironment.java
>  PRE-CREATION 
>   sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java 
> 27f9306a0 
>   
> sharelib/sqoop/src/test/java/org/apache/oozie/action/hadoop/TestSqoopMain.java
>  d6f96d546 
> 
> 
> Diff: https://reviews.apache.org/r/68317/diff/6/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Denes Bodo
> 
>

[jira] [Commented] (OOZIE-3326) Sqoop Action should support tez delegation tokens for hive-import

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3326:
--


Testing JIRA OOZIE-3326

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 star imports
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 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 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [tools].
. {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/streaming].
. {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/pig].
. {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/git].
. {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/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 [webapp].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3136
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{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/1010/



> Sqoop Action should support tez delegation tokens for hive-import
> -
>
> Key: OOZIE-3326
> URL: https://issues.apache.org/jira/browse/OOZIE-3326
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Brian Goerlitz
>Assignee: Brian Goerlitz
>Priority: Major
> Attachments: OOZIE-3326_003.patch, OOZIE-3326_004.patch, 
> OOZIE-3326_005.patch, OOZIE-3326_006.patch, OOZIE-3326_007.patch, 
> OZIE-3326_001.patch, OZIE-3326_002.patch
>
>
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> At present, hive-import will fail to start a tez session in secure 
> environment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3326 PreCommit Build #1010

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3326
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1010/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.91 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive2].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [core].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2560 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3326

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any star imports
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+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 [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [examples].
 +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 [webapp].
+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: 3136
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s

 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/1010/

Adding comment to JIRA
  % 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{"self":"https://issues.apache.org/jira/rest/api/2/issue/13178293/comment/16771235","id":"16771235","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop

[jira] [Commented] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3261:
--


Testing JIRA OOZIE-3261

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 star imports
.{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 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 
[fluent-job/fluent-job-api].
. {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 [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {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/streaming].
. {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/hive].
. {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/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3135
{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/1007/



> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch, oozie-3261-002.patch, 
> oozie-3261-amend-01.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> 

[jira] [Commented] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3261:
--


Testing JIRA OOZIE-3261

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 star imports
.{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 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 [sharelib/hive2].
. {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/oozie].
. {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/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/distcp].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {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 [tools].
. {color:green}+1{color} There are no new bugs found in 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [core].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3135
{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/1006/



> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch, oozie-3261-002.patch, 
> oozie-3261-amend-01.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> 

Failed: OOZIE-3261 PreCommit Build #1006

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3261
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1006/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.91 MB...]
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [fluent-job/fluent-job-api].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [core].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2561 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3261

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any star imports
+1 the patch does not introduce any line longer than 132
-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 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+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 [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +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/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/git].
 +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 [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
+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: 3135
+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/1006/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  32820 0  100  3282  0   3043  0:00:01  0:00:01 --:--:--  
3044{"self":"https://issues.apache.org/jira/rest/api/2/issue/13162382/comment/16771173","id":"16771173","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 

[jira] [Commented] (OOZIE-3326) Sqoop Action should support tez delegation tokens for hive-import

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3326:
--

PreCommit-OOZIE-Build started


> Sqoop Action should support tez delegation tokens for hive-import
> -
>
> Key: OOZIE-3326
> URL: https://issues.apache.org/jira/browse/OOZIE-3326
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Brian Goerlitz
>Assignee: Brian Goerlitz
>Priority: Major
> Attachments: OOZIE-3326_003.patch, OOZIE-3326_004.patch, 
> OOZIE-3326_005.patch, OOZIE-3326_006.patch, OOZIE-3326_007.patch, 
> OZIE-3326_001.patch, OZIE-3326_002.patch
>
>
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> At present, hive-import will fail to start a tez session in secure 
> environment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2833) when using uber mode the regex pattern used in the extractHeapSizeMB method does not allow heap sizes specified in bytes.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2833:
--


Testing JIRA OOZIE-2833

Cleaning local git workspace



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




> when using uber mode the regex pattern used in the extractHeapSizeMB method 
> does not allow heap sizes specified in bytes.
> -
>
> Key: OOZIE-2833
> URL: https://issues.apache.org/jira/browse/OOZIE-2833
> Project: Oozie
>  Issue Type: Bug
>Reporter: Thomas Scott
>Assignee: Attila Sasvari
>Priority: Minor
> Attachments: OOZIE-2833.01.patch, OOZIE-2833.02.patch
>
>
> The extractHeapSizeMB method used here:
> https://github.com/apache/oozie/blob/9c0516608bdd0787b1fac3a69ccfe9d36cbb2d15/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L401
> Uses the following pattern:
> -Xmx(([0-9]+)[mMgG])
> This requires that the -Xmx configuration option end in "m" or "g". However, 
> it is valid to configure this option in bytes without the "m" or "g" and this 
> will not be picked up. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2833 PreCommit Build #1009

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2833
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1009/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 791.20 KB...]
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary for Apache Oozie Main 5.2.0-SNAPSHOT:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  2.341 s]
[INFO] Apache Oozie Fluent Job  SUCCESS [  0.062 s]
[INFO] Apache Oozie Fluent Job API  SUCCESS [ 25.620 s]
[INFO] Apache Oozie Client  SUCCESS [ 15.897 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 12.136 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  6.279 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  5.311 s]
[INFO] Apache Oozie Core .. SUCCESS [01:23 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.694 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.870 s]
[INFO] Apache Oozie Share Lib Git . SUCCESS [ 10.667 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  8.148 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  9.105 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  6.002 s]
[INFO] Apache Oozie Examples .. SUCCESS [  9.524 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 10.949 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.022 s]
[INFO] Apache Oozie Docs .. SUCCESS [  2.870 s]
[INFO] Apache Oozie WebApp  SUCCESS [  8.455 s]
[INFO] Apache Oozie Tools . SUCCESS [ 13.527 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.694 s]
[INFO] Apache Oozie Fluent Job Client . SUCCESS [  0.496 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.587 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.248 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.053 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  04:25 min
[INFO] Finished at: 2019-02-18T15:18:43Z
[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 
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java...
error: while searching for:
import java.util.Map.Entry;
import java.util.Properties;
import java.util.Set;
import java.util.regex.Matcher;
import java.util.regex.Pattern;

import org.apache.hadoop.conf.Configuration;
import org.apache.hadoop.filecache.DistributedCache;

error: patch failed: 
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java:37
error: 
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java: 
patch does not apply
Checking patch 
core/src/main/java/org/apache/oozie/util/LauncherConfUtils.java...
Checking patch 
core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java...
error: while searching for:
import org.apache.oozie.service.WorkflowStoreService;
import org.apache.oozie.service.UserGroupInformationService;
import org.apache.oozie.util.IOUtils;
import org.apache.oozie.util.XConfiguration;
import org.apache.oozie.util.XmlUtils;
import org.apache.oozie.workflow.WorkflowApp;

error: patch failed: 
core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java:70
error: 
core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java: 
patch does not apply
Checking patch 

[jira] [Commented] (OOZIE-2833) when using uber mode the regex pattern used in the extractHeapSizeMB method does not allow heap sizes specified in bytes.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2833:
--

PreCommit-OOZIE-Build started


> when using uber mode the regex pattern used in the extractHeapSizeMB method 
> does not allow heap sizes specified in bytes.
> -
>
> Key: OOZIE-2833
> URL: https://issues.apache.org/jira/browse/OOZIE-2833
> Project: Oozie
>  Issue Type: Bug
>Reporter: Thomas Scott
>Assignee: Attila Sasvari
>Priority: Minor
> Attachments: OOZIE-2833.01.patch, OOZIE-2833.02.patch
>
>
> The extractHeapSizeMB method used here:
> https://github.com/apache/oozie/blob/9c0516608bdd0787b1fac3a69ccfe9d36cbb2d15/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L401
> Uses the following pattern:
> -Xmx(([0-9]+)[mMgG])
> This requires that the -Xmx configuration option end in "m" or "g". However, 
> it is valid to configure this option in bytes without the "m" or "g" and this 
> will not be picked up. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2833) when using uber mode the regex pattern used in the extractHeapSizeMB method does not allow heap sizes specified in bytes.

[Andras Salamon (JIRA)]

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

Andras Salamon commented on OOZIE-2833:
---

I think OOZIE-3307 already solved this problem.

> when using uber mode the regex pattern used in the extractHeapSizeMB method 
> does not allow heap sizes specified in bytes.
> -
>
> Key: OOZIE-2833
> URL: https://issues.apache.org/jira/browse/OOZIE-2833
> Project: Oozie
>  Issue Type: Bug
>Reporter: Thomas Scott
>Assignee: Attila Sasvari
>Priority: Minor
> Attachments: OOZIE-2833.01.patch, OOZIE-2833.02.patch
>
>
> The extractHeapSizeMB method used here:
> https://github.com/apache/oozie/blob/9c0516608bdd0787b1fac3a69ccfe9d36cbb2d15/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L401
> Uses the following pattern:
> -Xmx(([0-9]+)[mMgG])
> This requires that the -Xmx configuration option end in "m" or "g". However, 
> it is valid to configure this option in bytes without the "m" or "g" and this 
> will not be picked up. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2461) Workflow, Coordinator and Bundle job querying should have last modified filter

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2461:
--


Testing JIRA OOZIE-2461

Cleaning local git workspace



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




> Workflow, Coordinator and Bundle job querying should have last modified filter
> --
>
> Key: OOZIE-2461
> URL: https://issues.apache.org/jira/browse/OOZIE-2461
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2461-1.patch, OOZIE-2461-10.patch, 
> OOZIE-2461-11.patch, OOZIE-2461-6.patch, OOZIE-2461-7.patch, 
> OOZIE-2461-8.patch, OOZIE-2461-9.patch
>
>
> To get currently running coordinator and id, one user had to do
> http://localhost:11000/oozie/v1/jobs?jobtype=coord=user%3satish_1.0%3B=1=3000
> They could not use name in the filter as they include a version and keep 
> changing. For eg:
> urs_satish_filter-0.1-daily-coord
> urs_puru_service-0.4-hourly-coord
> It would be good to have last modified filter to get recently active 
> coordinators.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2461 PreCommit Build #1008

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2461
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1008/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 802.38 KB...]
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobInfoGetJPAExecutor.java...
error: while searching for:
package org.apache.oozie.executor.jpa;

import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;

import org.apache.oozie.BundleJobBean;
import org.apache.oozie.BundleJobInfo;
import org.apache.oozie.client.Job;
import org.apache.oozie.client.OozieClient;
import org.apache.oozie.service.JPAService;
import org.apache.oozie.service.Services;
import org.apache.oozie.test.XDataTestCase;

error: patch failed: 
core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobInfoGetJPAExecutor.java:19
error: 
core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobInfoGetJPAExecutor.java:
 patch does not apply
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobQueryExecutor.java...
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobInfoGetJPAExecutor.java...
error: while searching for:
package org.apache.oozie.executor.jpa;

import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;

import org.apache.oozie.CoordinatorJobBean;
import org.apache.oozie.CoordinatorJobInfo;
import org.apache.oozie.client.CoordinatorJob;
import org.apache.oozie.client.OozieClient;
import org.apache.oozie.service.JPAService;
import org.apache.oozie.service.Services;
import org.apache.oozie.test.XDataTestCase;

error: patch failed: 
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobInfoGetJPAExecutor.java:19
error: 
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobInfoGetJPAExecutor.java:
 patch does not apply
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestWorkflowsJobGetJPAExecutor.java...
Hunk #1 succeeded at 430 (offset 92 lines).
Checking patch docs/src/site/twiki/DG_CommandLineTool.twiki...
error: docs/src/site/twiki/DG_CommandLineTool.twiki: No such file or directory
Checking patch docs/src/site/twiki/WebServicesAPI.twiki...
error: docs/src/site/twiki/WebServicesAPI.twiki: No such file or directory
Checking patch src/main/java/org/apache/oozie/cli/OozieCLI.java...
error: src/main/java/org/apache/oozie/cli/OozieCLI.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/client/OozieClient.java...
error: src/main/java/org/apache/oozie/client/OozieClient.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/BundleJobBean.java...
error: src/main/java/org/apache/oozie/BundleJobBean.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/CoordinatorEngine.java...
error: src/main/java/org/apache/oozie/CoordinatorEngine.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/CoordinatorJobBean.java...
error: src/main/java/org/apache/oozie/CoordinatorJobBean.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/DagEngine.java...
error: src/main/java/org/apache/oozie/DagEngine.java: No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/BundleJobInfoGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/BundleJobInfoGetJPAExecutor.java: 
No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/BundleJobQueryExecutor.java...
error: src/main/java/org/apache/oozie/executor/jpa/BundleJobQueryExecutor.java: 
No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/CoordJobInfoGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/CoordJobInfoGetJPAExecutor.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/WorkflowsJobGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/WorkflowsJobGetJPAExecutor.java: No 
such file or directory
Checking patch src/main/java/org/apache/oozie/store/StoreStatusFilter.java...
error: src/main/java/org/apache/oozie/store/StoreStatusFilter.java: No such 
file or directory
Checking patch src/main/java/org/apache/oozie/util/JobsFilterUtils.java...
error: src/main/java/org/apache/oozie/util/JobsFilterUtils.java: No such file 
or directory
Checking patch src/test/java/org/apache/oozie/client/TestOozieCLI.java...
error: src/test/java/org/apache/oozie/client/TestOozieCLI.java: No such file or 
directory
Checking patch 
src/test/java/org/apache/oozie/executor/jpa/TestBundleJobInfoGetJPAExecutor.java...
error: 
src/test/java/org/apache/oozie/executor/jpa/TestBundleJobInfoGetJPAExecutor.java:
 No such file or directory
Checking patch 

[jira] [Commented] (OOZIE-2461) Workflow, Coordinator and Bundle job querying should have last modified filter

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2461:
--

PreCommit-OOZIE-Build started


> Workflow, Coordinator and Bundle job querying should have last modified filter
> --
>
> Key: OOZIE-2461
> URL: https://issues.apache.org/jira/browse/OOZIE-2461
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2461-1.patch, OOZIE-2461-10.patch, 
> OOZIE-2461-11.patch, OOZIE-2461-6.patch, OOZIE-2461-7.patch, 
> OOZIE-2461-8.patch, OOZIE-2461-9.patch
>
>
> To get currently running coordinator and id, one user had to do
> http://localhost:11000/oozie/v1/jobs?jobtype=coord=user%3satish_1.0%3B=1=3000
> They could not use name in the filter as they include a version and keep 
> changing. For eg:
> urs_satish_filter-0.1-daily-coord
> urs_puru_service-0.4-hourly-coord
> It would be good to have last modified filter to get recently active 
> coordinators.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3326) Sqoop Action should support tez delegation tokens for hive-import

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3326:
--


Testing JIRA OOZIE-3326

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 star imports
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 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:red}-1{color} There are [1] new bugs found below threshold in total that 
must be fixed.
. {color:green}+1{color} There are no new bugs found in 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:red}-1{color} There are [1] new bugs found below threshold in 
[sharelib/oozie] that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones): 
sharelib/oozie/findbugs-new.html
. The most important FindBugs errors are:
. At LauncherAM.java:[line 95]: 
org.apache.oozie.action.hadoop.LauncherAM.sysenv isn't final but should be
. {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/spark].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {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/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 [webapp].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3136
.{color:orange}Tests failed at first run:{color}
TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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/1005/



> Sqoop Action should support tez delegation tokens for hive-import
> -
>
> Key: OOZIE-3326
> URL: https://issues.apache.org/jira/browse/OOZIE-3326
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Brian Goerlitz
>Assignee: Brian Goerlitz
>Priority: Major
> Attachments: OOZIE-3326_003.patch, OOZIE-3326_004.patch, 
> OOZIE-3326_005.patch, OOZIE-3326_006.patch, OZIE-3326_001.patch, 
> OZIE-3326_002.patch
>
>
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> At present, hive-import will fail to start a tez session in secure 
> environment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3326 PreCommit Build #1005

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3326
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1005/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 2.51 MB...]
[DEBUG] There are no new bugs found in [core].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[ERROR] There are [1] new bugs found below threshold in total that must be 
fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2884 bytes
[TRACE] Full summary file size is 1795 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3326

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any star imports
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
-1 There are [1] new bugs found below threshold in total that must be fixed.
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [tools].
 -1 There are [1] new bugs found below threshold in [sharelib/oozie] that must 
be fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
sharelib/oozie/findbugs-new.html
 The most important FindBugs errors are:
 At LauncherAM.java:[line 95]: org.apache.oozie.action.hadoop.LauncherAM.sysenv 
isn't final but should be
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [examples].
 +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 [webapp].
+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: 3136
Tests failed at first run:
TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+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/1005/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  38060 0  100  3806  0   3778  0:00:01  0:00:01 --:--:--  

[jira] [Updated] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[duan xiong (JIRA)]

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

duan xiong updated OOZIE-3261:
--
Attachment: oozie-3261-amend-01.patch

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch, oozie-3261-002.patch, 
> oozie-3261-amend-01.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3261:
--

PreCommit-OOZIE-Build started


> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch, oozie-3261-002.patch, 
> oozie-3261-amend-01.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton commented on OOZIE-3261:
---

[~nobigo] please rename the amend patch in the following way: 
-amend-.patch. This way we will now later as well, 
that this was an amend patch.

You can find an example here: https://issues.apache.org/jira/browse/OOZIE-3419

 

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch, oozie-3261-002.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[duan xiong (JIRA)]

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

duan xiong updated OOZIE-3261:
--
Attachment: oozie-3261-002.patch

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch, oozie-3261-002.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[duan xiong (JIRA)]

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

duan xiong reopened OOZIE-3261:
---

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 68317: Sqoop Action should support tez delegation tokens for hive-import

[Andras Salamon]

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


Ship it!




Ship It!

- Andras Salamon


On Feb. 15, 2019, 11:33 a.m., Denes Bodo wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68317/
> ---
> 
> (Updated Feb. 15, 2019, 11:33 a.m.)
> 
> 
> Review request for oozie and Andras Salamon.
> 
> 
> Bugs: OOZIE-3326
> https://issues.apache.org/jira/browse/OOZIE-3326
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> 
> At present, hive-import will fail to start a tez session in secure 
> environment.
> 
> 
> Diffs
> -
> 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
> 63afd91d3 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
> b6599f7f3 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/SystemEnvironment.java
>  PRE-CREATION 
>   sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java 
> 27f9306a0 
>   
> sharelib/sqoop/src/test/java/org/apache/oozie/action/hadoop/TestSqoopMain.java
>  d6f96d546 
> 
> 
> Diff: https://reviews.apache.org/r/68317/diff/6/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Denes Bodo
> 
>

[jira] [Commented] (OOZIE-3326) Sqoop Action should support tez delegation tokens for hive-import

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3326:
--

PreCommit-OOZIE-Build started


> Sqoop Action should support tez delegation tokens for hive-import
> -
>
> Key: OOZIE-3326
> URL: https://issues.apache.org/jira/browse/OOZIE-3326
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Brian Goerlitz
>Assignee: Brian Goerlitz
>Priority: Major
> Attachments: OOZIE-3326_003.patch, OOZIE-3326_004.patch, 
> OOZIE-3326_005.patch, OOZIE-3326_006.patch, OZIE-3326_001.patch, 
> OZIE-3326_002.patch
>
>
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> At present, hive-import will fail to start a tez session in secure 
> environment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OOZIE-3302) Broken link in documentation: Dependencies Report, Licenses section

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton resolved OOZIE-3302.
---
Resolution: Duplicate

>  Broken link in documentation: Dependencies Report, Licenses section 
> -
>
> Key: OOZIE-3302
> URL: https://issues.apache.org/jira/browse/OOZIE-3302
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Priority: Major
>
> In the documentation there is a reference to Dependencies report page, which 
> page does not exist:
> [https://oozie.apache.org/docs/5.0.0/index.html#Licensing_Information]
> [https://oozie.apache.org/docs/5.0.0/dependencies.html#Licenses]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3302) Broken link in documentation: Dependencies Report, Licenses section

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton commented on OOZIE-3302:
---

Thank you [~asalamon74] for pointing this out! Closing this issue as Duplicate 
and let's fix it in OOZIE-1098

 

>  Broken link in documentation: Dependencies Report, Licenses section 
> -
>
> Key: OOZIE-3302
> URL: https://issues.apache.org/jira/browse/OOZIE-3302
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Priority: Major
>
> In the documentation there is a reference to Dependencies report page, which 
> page does not exist:
> [https://oozie.apache.org/docs/5.0.0/index.html#Licensing_Information]
> [https://oozie.apache.org/docs/5.0.0/dependencies.html#Licenses]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3326) Sqoop Action should support tez delegation tokens for hive-import

[Denes Bodo (JIRA)]

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

Denes Bodo updated OOZIE-3326:
--
Attachment: OOZIE-3326_006.patch

> Sqoop Action should support tez delegation tokens for hive-import
> -
>
> Key: OOZIE-3326
> URL: https://issues.apache.org/jira/browse/OOZIE-3326
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Brian Goerlitz
>Assignee: Brian Goerlitz
>Priority: Major
> Attachments: OOZIE-3326_003.patch, OOZIE-3326_004.patch, 
> OOZIE-3326_005.patch, OOZIE-3326_006.patch, OZIE-3326_001.patch, 
> OZIE-3326_002.patch
>
>
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> At present, hive-import will fail to start a tez session in secure 
> environment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3302) Broken link in documentation: Dependencies Report, Licenses section

[Andras Salamon (JIRA)]

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

Andras Salamon commented on OOZIE-3302:
---

I think this is a duplicate of OOZIE-1098


>  Broken link in documentation: Dependencies Report, Licenses section 
> -
>
> Key: OOZIE-3302
> URL: https://issues.apache.org/jira/browse/OOZIE-3302
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Priority: Major
>
> In the documentation there is a reference to Dependencies report page, which 
> page does not exist:
> [https://oozie.apache.org/docs/5.0.0/index.html#Licensing_Information]
> [https://oozie.apache.org/docs/5.0.0/dependencies.html#Licenses]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OOZIE-3418) Upgrade to Guava 27

[Andras Salamon (JIRA)]

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

Andras Salamon edited comment on OOZIE-3418 at 2/18/19 11:40 AM:
-

Lots of test failures shows the following error:

{noformat}
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.oozie.action.hadoop.TestMapReduceActionExecutor
[ERROR] Tests run: 22, Failures: 0, Errors: 22, Skipped: 0, Time elapsed: 7.419 
s <<< FAILURE! - in org.apache.oozie.action.hadoop.TestMapReduceActionExecutor
[ERROR] 
testDefaultShareLibName(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
  Time elapsed: 0.326 s  <<< ERROR!
java.lang.NoSuchMethodError: 
com.google.common.base.Objects.toStringHelper(Ljava/lang/Object;)Lcom/google/common/base/Objects$ToStringHelper;
        at 
org.apache.hadoop.metrics2.lib.MetricsRegistry.toString(MetricsRegistry.java:392)
        at java.lang.String.valueOf(String.java:2994)
...
{noformat}

This class has been 
[removed|https://google.github.io/guava/releases/20.0/api/docs/com/google/common/base/Objects.ToStringHelper.html]
 from Guava 21. 

Hadoop 2 requires older Guava and it won't work with the latest one. We should 
probably shade an older version of Guava for hadoop.


was (Author: asalamon74):
Lots of test failures shows the following error:

{noformat}
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.oozie.action.hadoop.TestMapReduceActionExecutor
[ERROR] Tests run: 22, Failures: 0, Errors: 22, Skipped: 0, Time elapsed: 7.419 
s <<< FAILURE! - in org.apache.oozie.action.hadoop.TestMapReduceActionExecutor
[ERROR] 
testDefaultShareLibName(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
  Time elapsed: 0.326 s  <<< ERROR!
java.lang.NoSuchMethodError: 
com.google.common.base.Objects.toStringHelper(Ljava/lang/Object;)Lcom/google/common/base/Objects$ToStringHelper;
        at 
org.apache.hadoop.metrics2.lib.MetricsRegistry.toString(MetricsRegistry.java:392)
        at java.lang.String.valueOf(String.java:2994){noformat}
...
{noformat}

This class has been 
[removed|https://google.github.io/guava/releases/20.0/api/docs/com/google/common/base/Objects.ToStringHelper.html]
 from Guava 21. 

Hadoop 2 requires older Guava and it won't work with the latest one. We should 
probably shade an older version of Guava for hadoop.

> Upgrade to Guava 27
> ---
>
> Key: OOZIE-3418
> URL: https://issues.apache.org/jira/browse/OOZIE-3418
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3418-01-WIP.patch
>
>
> There is a guava security issue: 
> [CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237]
> Currently we use Guava 11.0.2 which is affected. We need to upgrade to at 
> least guava 24.1.1. Probably the best would be to use Guava 27.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3418) Upgrade to Guava 27

[Andras Salamon (JIRA)]

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

Andras Salamon commented on OOZIE-3418:
---

Lots of test failures shows the following error:

{noformat}
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.oozie.action.hadoop.TestMapReduceActionExecutor
[ERROR] Tests run: 22, Failures: 0, Errors: 22, Skipped: 0, Time elapsed: 7.419 
s <<< FAILURE! - in org.apache.oozie.action.hadoop.TestMapReduceActionExecutor
[ERROR] 
testDefaultShareLibName(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
  Time elapsed: 0.326 s  <<< ERROR!
java.lang.NoSuchMethodError: 
com.google.common.base.Objects.toStringHelper(Ljava/lang/Object;)Lcom/google/common/base/Objects$ToStringHelper;
        at 
org.apache.hadoop.metrics2.lib.MetricsRegistry.toString(MetricsRegistry.java:392)
        at java.lang.String.valueOf(String.java:2994){noformat}
...
{noformat}

This class has been 
[removed|https://google.github.io/guava/releases/20.0/api/docs/com/google/common/base/Objects.ToStringHelper.html]
 from Guava 21. 

Hadoop 2 requires older Guava and it won't work with the latest one. We should 
probably shade an older version of Guava for hadoop.

> Upgrade to Guava 27
> ---
>
> Key: OOZIE-3418
> URL: https://issues.apache.org/jira/browse/OOZIE-3418
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3418-01-WIP.patch
>
>
> There is a guava security issue: 
> [CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237]
> Currently we use Guava 11.0.2 which is affected. We need to upgrade to at 
> least guava 24.1.1. Probably the best would be to use Guava 27.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OOZIE-3433) [build] Set up mvn clean to delete the "build" directory as well

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton resolved OOZIE-3433.
---
   Resolution: Duplicate
Fix Version/s: (was: 5.2.0)

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3433
> URL: https://issues.apache.org/jira/browse/OOZIE-3433
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean"：
> There's an extra number of 0 in front filesets：
> {code:java}
> 
>   org.apache.maven.plugins
>   maven-clean-plugin
>   3.0.0
>   
>   0 
>   
>   build
>   
>   
>   
> 
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (OOZIE-3433) [build] Set up mvn clean to delete the "build" directory as well

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton reopened OOZIE-3433:
---

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3433
> URL: https://issues.apache.org/jira/browse/OOZIE-3433
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean"：
> There's an extra number of 0 in front filesets：
> {code:java}
> 
>   org.apache.maven.plugins
>   maven-clean-plugin
>   3.0.0
>   
>   0 
>   
>   build
>   
>   
>   
> 
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OOZIE-3433) [build] Set up mvn clean to delete the "build" directory as well

[duan xiong (JIRA)]

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

duan xiong resolved OOZIE-3433.
---
   Resolution: Fixed
Fix Version/s: 5.2.0

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3433
> URL: https://issues.apache.org/jira/browse/OOZIE-3433
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean"：
> There's an extra number of 0 in front filesets：
> {code:java}
> 
>   org.apache.maven.plugins
>   maven-clean-plugin
>   3.0.0
>   
>   0 
>   
>   build
>   
>   
>   
> 
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3432) When use configuration oozie.service.ProxyUserService.root.hosts, oozie-error.log shows Invalid configuration defined

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton commented on OOZIE-3432:
---

[~nobigo], this issue seems to be a duplication of OOZIE-2338. Can you please 
ask if you can take over OOZIE-2338 and find a general solution for this 
warnings, instead of handling them separately?

> When use configuration oozie.service.ProxyUserService.root.hosts, 
> oozie-error.log shows Invalid configuration defined
> -
>
> Key: OOZIE-3432
> URL: https://issues.apache.org/jira/browse/OOZIE-3432
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Critical
> Attachments: oozie-3432-001.patch
>
>
> When use Oozie5.0.0, add configuration:
>  
> {code:java}
> oozie.service.ProxyUserService.proxyuser.root.hosts
> oozie.service.ProxyUserService.proxyuser.root.groups{code}
>  
> in  oozie-site,I start oozie service,Oozie log shows:
>  
> {code:java}
> SERVER[] Invalid configuration 
> defined,[oozie.service.ProxyUserService.proxyuser.root.hosts]
> SERVER[] Invalid configuration 
> defined,[oozie.service.ProxyUserService.proxyuser.root.groups]{code}
> It is not reasonable. Because It is oozie's configuration, not  user-defined 
> configuration，So  It should't shows WARN.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OOZIE-3413) Cannot start Oozie Web UI after deleting /tmp/embedded-jetty-jsp

[Andras Salamon (JIRA)]

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

Andras Salamon edited comment on OOZIE-3413 at 2/18/19 9:41 AM:


[~nobigo] Thanks for taking this over.

Yes, creating a new directory and configuring {{oozie.jsp.tmp.dir}} is a good 
workaround.

But I still think that it's a bug. A system should handle the deletion of the 
temp directory. And Oozie  + Jetty usually handles it well in most cases, it's 
only a problem in the edge case described above.


was (Author: asalamon74):
[~nobigo] Thanks for taking this over.

Yes, creating a new directory and configuring {{oozie.jsp.tmp.dir}} is a good 
workaround.

But I still think that it's a big. A system should handle the deletion of the 
temp directory. And Oozie  + Jetty usually handles it well in most cases, it's 
only a problem in the edge case described above.

> Cannot start Oozie Web UI after deleting /tmp/embedded-jetty-jsp
> 
>
> Key: OOZIE-3413
> URL: https://issues.apache.org/jira/browse/OOZIE-3413
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> After the following steps:
>  # Restart oozie server using {{oozied.sh}}
>  # {{rm -rf /tmp/embedded-jetty-jsp}}
>  # Open the Oozie Web UI in a browser: {{[http://localhost:11000/oozie/]}}
> Oozie Web UI does not start, it gives the following error message:
> {noformat}
> {
>   "errorMessage": "org.apache.jasper.JasperException: 
> java.lang.ClassNotFoundException: org.apache.jsp.index_jsp",
>   "httpStatusCode": 500
> }{noformat}
> jetty.log contains the following error message:
> {noformat}
> 2018-12-28 10:16:19,630  WARN ServletHandler:624 - 
> org.apache.jasper.JasperException: java.lang.ClassNotFoundException: 
> org.apache.jsp.index_jsp
> at 
> org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:176)
> at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
> at 
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)
> at 
> org.eclipse.jetty.jsp.JettyJspServlet.service(JettyJspServlet.java:112)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:566)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:199)
> at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:74)
> at 
> org.eclipse.jetty.servlet.DefaultServlet.sendWelcome(DefaultServlet.java:599)
> at 
> org.eclipse.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:484)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
> at 
> 

[jira] [Commented] (OOZIE-3326) Sqoop Action should support tez delegation tokens for hive-import

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3326:
--


Testing JIRA OOZIE-3326

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 star imports
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 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 [sharelib/hive2].
. {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/oozie].
. {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/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/distcp].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {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 [tools].
. {color:green}+1{color} There are no new bugs found in 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [core].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3136
.{color:orange}Tests failed at first run:{color}
TestPurgeXCommand#testPurgeableWorkflowOverTheLimitSucceededSubWorkflows
TestPurgeXCommand#testPurgeableWorkflowPurgeableSubWorkflowPurgeableSubSubWorkflow
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{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/1004/



> Sqoop Action should support tez delegation tokens for hive-import
> -
>
> Key: OOZIE-3326
> URL: https://issues.apache.org/jira/browse/OOZIE-3326
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Brian Goerlitz
>Assignee: Brian Goerlitz
>Priority: Major
> Attachments: OOZIE-3326_003.patch, OOZIE-3326_004.patch, 
> OOZIE-3326_005.patch, OZIE-3326_001.patch, OZIE-3326_002.patch
>
>
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> At present, hive-import will fail to start a tez session in secure 
> environment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3326 PreCommit Build #1004

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3326
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1004/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.92 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [fluent-job/fluent-job-api].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [core].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2560 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3326

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any star imports
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+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 [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +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/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/git].
 +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 [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
+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: 3136
Tests failed at first run:
TestPurgeXCommand#testPurgeableWorkflowOverTheLimitSucceededSubWorkflows
TestPurgeXCommand#testPurgeableWorkflowPurgeableSubWorkflowPurgeableSubSubWorkflow
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s

 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/1004/

Adding comment to JIRA
  % 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 --:--:-- --:--:-- --:--:-- 0100 
 35500 0  100  3550  0   2628  0:00:01  0:00:01 --:--:--  

[jira] [Commented] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton commented on OOZIE-3261:
---

[~nobigo], is strange that the build succeeded even with that extra character. 
Even the mvn clean worked. 

Please close  OOZIE-3433 and upload here an amend patch.

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3326) Sqoop Action should support tez delegation tokens for hive-import

[Andras Salamon (JIRA)]

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

Andras Salamon commented on OOZIE-3326:
---

[~dionusos] Ouch. forgot to press the button. Now I really sent a review. Sorry 
for the confusion.

> Sqoop Action should support tez delegation tokens for hive-import
> -
>
> Key: OOZIE-3326
> URL: https://issues.apache.org/jira/browse/OOZIE-3326
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Brian Goerlitz
>Assignee: Brian Goerlitz
>Priority: Major
> Attachments: OOZIE-3326_003.patch, OOZIE-3326_004.patch, 
> OOZIE-3326_005.patch, OZIE-3326_001.patch, OZIE-3326_002.patch
>
>
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> At present, hive-import will fail to start a tez session in secure 
> environment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3433) [build] Set up mvn clean to delete the "build" directory as well

[duan xiong (JIRA)]

duan xiong created OOZIE-3433:
-

 Summary: [build] Set up mvn clean to delete the "build" directory 
as well
 Key: OOZIE-3433
 URL: https://issues.apache.org/jira/browse/OOZIE-3433
 Project: Oozie
  Issue Type: Improvement
  Components: build
Affects Versions: 5.1.0
Reporter: duan xiong
Assignee: duan xiong


There are folders named build in every project we have. They are taking up a 
ton of space and not cleaned away when executing "mvn clean"：

There's an extra number of 0 in front filesets：
{code:java}

    org.apache.maven.plugins
    maven-clean-plugin
    3.0.0
    
    0 
    
    build
    
    
    

{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[duan xiong (JIRA)]

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

duan xiong commented on OOZIE-3261:
---

Hi, I have create another one OOZIE-3433. and I will repair this soon.

> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3261) [build] Set up mvn clean to delete the "build" directory as well

[duan xiong (JIRA)]

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

duan xiong commented on OOZIE-3261:
---

Hi [~kmarton],I find this patch file has some problem: There's an extra number 
of 0 in front filesets.  

```
||
| |org.apache.maven.plugins|
| |maven-clean-plugin|
| |3.0.0|
| ||
| |0 |
| ||
| |build|
| ||
| ||
| ||
| ||



> [build] Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Fix For: 5.2.0
>
> Attachments: oozie-3261-001.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3261) Set up mvn clean to delete the "build" directory as well

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton commented on OOZIE-3261:
---

Thank you [~nobigo] for the fix! +1

 

> Set up mvn clean to delete the "build" directory as well
> 
>
> Key: OOZIE-3261
> URL: https://issues.apache.org/jira/browse/OOZIE-3261
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Reporter: Peter Cseh
>Assignee: duan xiong
>Priority: Major
>  Labels: newbie
> Attachments: oozie-3261-001.patch
>
>
> There are folders named build in every project we have. They are taking up a 
> ton of space and not cleaned away when executing "mvn clean" 
> {noformat}
> >> [84] 13:52 : oozie (master) :: du -sh */*/build
> 6.9M  sharelib/distcp/build
> 174M  sharelib/hive/build
> 1.8G  sharelib/pig/build
> 665M  sharelib/spark/build
> 498M  sharelib/sqoop/build
> 7.3M  sharelib/streaming/build
> >> [85] 13:53 : oozie (master) :: du -sh */build
>  23M  core/build
> 7.8M  minitest/build
> 6.2M  tools/build
> {noformat}
> They are containing a bunch of files generated during executions in the 
> MiniCluster:
> {noformat}
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742879
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742863_2039.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073743029_2205.meta
> sharelib/spark/build/test/data/dfs//data/data1/current/BP-1306731421-172.30.65.43-1527256082477/current/finalized/subdir0/subdir4/blk_1073742975_2151.meta
> {noformat}
> "mvn clean" should be configured to clean these folders up as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 68317: Sqoop Action should support tez delegation tokens for hive-import

[Andras Salamon]

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




sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java
Lines 45 (patched)


Could we use LauncherAM.OOZIE_ACTION_CONF_XML instead?



sharelib/sqoop/src/test/java/org/apache/oozie/action/hadoop/TestSqoopMain.java
Lines 62-64 (patched)


Could use AssertNotNull


- Andras Salamon


On Feb. 15, 2019, 11:33 a.m., Denes Bodo wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68317/
> ---
> 
> (Updated Feb. 15, 2019, 11:33 a.m.)
> 
> 
> Review request for oozie and Andras Salamon.
> 
> 
> Bugs: OOZIE-3326
> https://issues.apache.org/jira/browse/OOZIE-3326
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> SqoopMain needs to support tez delegation tokens for hive-imports. 
> Implementation is similar to that of HiveMain and Hive2Main.
> 
> At present, hive-import will fail to start a tez session in secure 
> environment.
> 
> 
> Diffs
> -
> 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
> 63afd91d3 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
> b6599f7f3 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/SystemEnvironment.java
>  PRE-CREATION 
>   sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java 
> 27f9306a0 
>   
> sharelib/sqoop/src/test/java/org/apache/oozie/action/hadoop/TestSqoopMain.java
>  d6f96d546 
> 
> 
> Diff: https://reviews.apache.org/r/68317/diff/5/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Denes Bodo
> 
>

[jira] [Commented] (OOZIE-3413) Cannot start Oozie Web UI after deleting /tmp/embedded-jetty-jsp

[Andras Salamon (JIRA)]

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

Andras Salamon commented on OOZIE-3413:
---

[~nobigo] Thanks for taking this over.

Yes, creating a new directory and configuring {{oozie.jsp.tmp.dir}} is a good 
workaround.

But I still think that it's a big. A system should handle the deletion of the 
temp directory. And Oozie  + Jetty usually handles it well in most cases, it's 
only a problem in the edge case described above.

> Cannot start Oozie Web UI after deleting /tmp/embedded-jetty-jsp
> 
>
> Key: OOZIE-3413
> URL: https://issues.apache.org/jira/browse/OOZIE-3413
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> After the following steps:
>  # Restart oozie server using {{oozied.sh}}
>  # {{rm -rf /tmp/embedded-jetty-jsp}}
>  # Open the Oozie Web UI in a browser: {{[http://localhost:11000/oozie/]}}
> Oozie Web UI does not start, it gives the following error message:
> {noformat}
> {
>   "errorMessage": "org.apache.jasper.JasperException: 
> java.lang.ClassNotFoundException: org.apache.jsp.index_jsp",
>   "httpStatusCode": 500
> }{noformat}
> jetty.log contains the following error message:
> {noformat}
> 2018-12-28 10:16:19,630  WARN ServletHandler:624 - 
> org.apache.jasper.JasperException: java.lang.ClassNotFoundException: 
> org.apache.jsp.index_jsp
> at 
> org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:176)
> at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
> at 
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)
> at 
> org.eclipse.jetty.jsp.JettyJspServlet.service(JettyJspServlet.java:112)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:566)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:199)
> at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:74)
> at 
> org.eclipse.jetty.servlet.DefaultServlet.sendWelcome(DefaultServlet.java:599)
> at 
> org.eclipse.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:484)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
> at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at 
>