[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (91 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3567  Oozie ShellAction should support absolute bash file path
https://issues.apache.org/jira/browse/OOZIE-3567
OOZIE-3566  Wrong numbers provided by Oozie monitoring webservices.requests 
sampler
https://issues.apache.org/jira/browse/OOZIE-3566
OOZIE-3560  IDEA shows have some error  in index.jsp
https://issues.apache.org/jira/browse/OOZIE-3560
OOZIE-3482  Fix bug in CoordSubmitXCommand#validateCoordinatorJob
https://issues.apache.org/jira/browse/OOZIE-3482
OOZIE-3480  Add windowactionstatus metrics in DBLiteWorkflowStoreService
https://issues.apache.org/jira/browse/OOZIE-3480
OOZIE-3461  CoordMaterializeTriggerService code cleanup
https://issues.apache.org/jira/browse/OOZIE-3461
OOZIE-3449  Make spark-2 as the default profile
https://issues.apache.org/jira/browse/OOZIE-3449
OOZIE-3447  Run test case in local : It shows oozie-hsqldb-orm.xml exception
https://issues.apache.org/jira/browse/OOZIE-3447
OOZIE-3418  Upgrade to Guava 27
https://issues.apache.org/jira/browse/OOZIE-3418
OOZIE-3404  The env variable of SPARK_HOME needs to be set when running pySpark
https://issues.apache.org/jira/browse/OOZIE-3404
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-3335  Cleanup parseFilter methods
https://issues.apache.org/jira/browse/OOZIE-3335
OOZIE-3328  Create Hive compatibility action executor to run hive actions using 
beeline
https://issues.apache.org/jira/browse/OOZIE-3328
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-3256  refactor OozieCLI class
https://issues.apache.org/jira/browse/OOZIE-3256
OOZIE-3254  [coordinator] LAST_ONLY and NONE execution modes: possible 
OutOfMemoryError when there are too many coordinator actions to materialize
https://issues.apache.org/jira/browse/OOZIE-3254
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-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-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
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
OOZIE-2779  Mask Hive2 action Beeline JDBC password

Re: [ANNOUNCE] Apache Oozie 5.2.0 released

[Peter Cseh]

Thanks Andras for coordinating and pushing the release on!
Also, thanks everyone for their contribution in the release!

On Fri, Dec 6, 2019 at 5:32 PM Andras Salamon  wrote:

> Hello,
>
> Apache Oozie is a workflow scheduler system to manage Apache Hadoop jobs.
>
> The Apache Oozie team is pleased to announce the release of Oozie 5.2.0.
> Oozie 5.2.0 includes new features, bug fixes, and minor improvements.
>
> The details of the release and download location can be found at
> https://oozie.apache.org
>
> The full release notes can be found at the download location, but some
> highlights of this release include:
>
> - Improved Java 11 compatibility ( OOZIE-3459 )
> - Improved S3 support ( OOZIE-3529 )
> - Escape quotes whitespaces in Sqoop  field ( OOZIE-2949 )
> - Exclusion pattern for sharelib JARs ( OOZIE-1624 )
> - Submitting users home directory permissions bugfix ( OOZIE-3478 )
> - Coordinator/bundle libpath bugfix ( OOZIE-3415 )
> - Reducing Guava usage ( OOZIE-3521 )
> - Migrate from obsolete third party libraries (joda, commons-lang 2.x,
> commons-codec)
> - Third party dependency revamp
>
> Thanks to all developers, QA's, users, and committers for making this
> release happen.
>
> Regards,
> Sala
>


-- 
*Peter Cseh* | Software Engineer, Cloudera Search
cloudera.com 
[image: Cloudera] 
[image: Cloudera on Twitter]  [image:
Cloudera on Facebook]  [image: Cloudera
on LinkedIn] 

--

[jira] [Commented] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Hadoop QA (Jira)]

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

Hadoop QA commented on OOZIE-3567:
--


Testing JIRA OOZIE-3567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:red}-1{color} the patch contains 1 line(s) with 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: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 [4] 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 [docs].
.{color:red}-1{color} There are [4] new bugs found below threshold in 
[core] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones): 
core/findbugs-new.html
.The most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of 
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
 can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.java/io/File.init(Ljava/lang/String;Ljava/lang/String;)V reads a 
file whose location might be specified by user input: At 
BulkJPAExecutor.java:[line 206]
.At AuthorizationService.java:[line 189]: At 
AuthorizationService.java:[line 192]
.{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/sqoop].
.{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/oozie].
.{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 [tools].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [examples].
.{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: 3199
.{color:orange}Tests failed at first run:{color}
TestBlockingInputStream#testLimitedWritingBlockingInputStream
.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 MODERNIZER{color}


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


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

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



> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
>  Labels: patch-available
> Fix For: 5.3.0
>
> Attachments: 
> 0001-OOZIE-3567-Oozie-ShellAction-should-support-absolute.patch
>
>
> as related in OOZIE-3320 

Failed: OOZIE-3567 PreCommit Build #1265

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 2.15 MB...]
[TRACE] Summary file size is 3335 bytes
[TRACE] Full summary file size is 2951 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO
  Running test-patch task MODERNIZER
  Running modernizer op=report
[TRACE] grep -c '.*ERROR.*Prefer' 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-clean.txt
[TRACE] Modernizer errors before patch: 51
[TRACE] grep -c '.*ERROR.*Prefer' 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-patch.txt
[TRACE] Modernizer errors after patch: 51


Testing JIRA OOZIE-3567

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 contains 1 line(s) with 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)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
-1 There are [4] 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 [docs].
-1 There are [4] new bugs found below threshold in [core] that must be 
fixed.
You can find the SpotBugs diff here (look for the red and orange ones): 
core/findbugs-new.html
The most important SpotBugs errors are:
At BulkJPAExecutor.java:[line 206]: This use of 
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
 can be vulnerable to SQL/JPQL injection
At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
java/io/File.init(Ljava/lang/String;Ljava/lang/String;)V reads a 
file whose location might be specified by user input: At 
BulkJPAExecutor.java:[line 206]
At AuthorizationService.java:[line 189]: At AuthorizationService.java:[line 
192]
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [sharelib/git].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/oozie].
+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 [tools].
+1 There are no new bugs found in [server].
+1 There are no new bugs found in [client].
+1 There are no new bugs found in [examples].
+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: 3199
Tests failed at first run:
TestBlockingInputStream#testLimitedWritingBlockingInputStream
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 
+1 MODERNIZER


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  42220 0  100  4222  0   2837  0:00:01  0:00:01 --:--:--  

[ANNOUNCE] Apache Oozie 5.2.0 released

[Andras Salamon]

Hello,

Apache Oozie is a workflow scheduler system to manage Apache Hadoop jobs.

The Apache Oozie team is pleased to announce the release of Oozie 5.2.0.
Oozie 5.2.0 includes new features, bug fixes, and minor improvements.

The details of the release and download location can be found at
https://oozie.apache.org

The full release notes can be found at the download location, but some
highlights of this release include:

- Improved Java 11 compatibility ( OOZIE-3459 )
- Improved S3 support ( OOZIE-3529 )
- Escape quotes whitespaces in Sqoop  field ( OOZIE-2949 )
- Exclusion pattern for sharelib JARs ( OOZIE-1624 )
- Submitting users home directory permissions bugfix ( OOZIE-3478 )
- Coordinator/bundle libpath bugfix ( OOZIE-3415 )
- Reducing Guava usage ( OOZIE-3521 )
- Migrate from obsolete third party libraries (joda, commons-lang 2.x,
commons-codec)
- Third party dependency revamp

Thanks to all developers, QA's, users, and committers for making this
release happen.

Regards,
Sala

[jira] [Commented] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Hadoop QA (Jira)]

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

Hadoop QA commented on OOZIE-3567:
--

PreCommit-OOZIE-Build started


> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
>  Labels: patch-available
> Fix For: 5.3.0
>
> Attachments: 
> 0001-OOZIE-3567-Oozie-ShellAction-should-support-absolute.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov commented on OOZIE-3567:
--

[~asalamon74] can help here why patch is failing?

i upload a new one.

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
>  Labels: patch-available
> Fix For: 5.3.0
>
> Attachments: 
> 0001-OOZIE-3567-Oozie-ShellAction-should-support-absolute.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov updated OOZIE-3567:
-
Attachment: 0001-OOZIE-3567-Oozie-ShellAction-should-support-absolute.patch

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
>  Labels: patch-available
> Fix For: 5.3.0
>
> Attachments: 
> 0001-OOZIE-3567-Oozie-ShellAction-should-support-absolute.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov updated OOZIE-3567:
-
Attachment: (was: 
[OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch)

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
>  Labels: patch-available
> Fix For: 5.3.0
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Hadoop QA (Jira)]

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

Hadoop QA commented on OOZIE-3567:
--


Testing JIRA OOZIE-3567

Cleaning local git workspace



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




> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
>  Labels: patch-available
> Fix For: 5.3.0
>
> Attachments: 
> [OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Failed: OOZIE-3567 PreCommit Build #1264

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 901.55 KB...]
[INFO] [ jar ]-
[INFO] 
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ 
oozie-zookeeper-security-tests ---
[INFO] Deleting 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/zookeeper-security-tests/target
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/zookeeper-security-tests/src/main/resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
oozie-zookeeper-security-tests ---
[INFO] No sources to compile
[INFO] 
[INFO] --- modernizer-maven-plugin:1.8.0:modernizer (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary for Apache Oozie Main 5.3.0-SNAPSHOT:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  0.917 s]
[INFO] Apache Oozie Fluent Job  SUCCESS [  0.074 s]
[INFO] Apache Oozie Fluent Job API  SUCCESS [  6.714 s]
[INFO] Apache Oozie Client  SUCCESS [  1.607 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  1.206 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  1.008 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  0.287 s]
[INFO] Apache Oozie Core .. SUCCESS [  8.477 s]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  1.850 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  1.388 s]
[INFO] Apache Oozie Share Lib Git . SUCCESS [  1.785 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  0.910 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  1.696 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  1.695 s]
[INFO] Apache Oozie Examples .. SUCCESS [  1.697 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [  2.063 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.018 s]
[INFO] Apache Oozie Docs .. SUCCESS [  0.036 s]
[INFO] Apache Oozie WebApp  SUCCESS [  1.773 s]
[INFO] Apache Oozie Tools . SUCCESS [  1.253 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.196 s]
[INFO] Apache Oozie Fluent Job Client . SUCCESS [  0.760 s]
[INFO] Apache Oozie Server  SUCCESS [  2.297 s]
[INFO] Apache Oozie Distro  SUCCESS [  1.607 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  1.684 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  45.649 s
[INFO] Finished at: 2019-12-06T14:39:18Z
[INFO] 
EXITVALUE 0
[TRACE] Modernizer output in HEAD verified and saved

Applying patch

Checking patch 
core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java...
error: while searching for:
Namespace ns = actionXml.getNamespace();?
?
String exec = actionXml.getChild("exec", ns).getTextTrim();?
String execName = new Path(exec).getName();?
actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);?
?
// Setting Shell command's arguments?

error: patch failed: 
core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java:54
error: 
core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java: 
patch does not apply
Checking patch docs/src/site/markdown/DG_ShellActionExtension.md...
error: while searching for:
properties that are passed to the Shell job.?
?
The `exec` element must contain the path of the Shell command to?
execute. The arguments of Shell command can then be specified?
using one or more `argument` element.?
?
The `argument` element, if present, contains argument to be passed to?

error: patch failed: docs/src/site/markdown/DG_ShellActionExtension.md:100
error: 

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

[Hadoop QA (Jira)]

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

Hadoop QA commented on OOZIE-3320:
--


Testing JIRA OOZIE-3320

Cleaning local git workspace



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




> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3320
> URL: https://issues.apache.org/jira/browse/OOZIE-3320
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Roey Shem Tov
>Assignee: Roey Shem Tov
>Priority: Major
>  Labels: patch
> Attachments: OOZIE-3086.patch, OOZIE-3320.patch
>
>
> bash files that saved on shared mount, cannot be execute by the ShellAction 
> in proper way.
> Example:
> Worker-1,Worker-2,Worker-3 have shared mount /mnt/hadoop
> on /mnt/hadoop there is a file script.sh
> Right now there is two options to submit it using ShellAction:
>  # Upload it to hdfs, add it as a file and submit script.sh
>  # use bash as exec and file location (/mnt/hadoop/script.sh) as argument 
> (e.g bash>/exec>/mnt/hadoop/script.sh
> Best option is that the  command will support shared mounted file :
> /mnt/hadoop/script.sh
>  
> This code is taking only the file name instead it full path:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); 
> String execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
> Best option to support shared mount file is to support file:// starting for 
> bash files that are local (or shared by mount), e.g:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); String execName; 
> String localFilePrefix = "file://";
>  // When exec starts with 'file://' refer it as local file. 
> if (exec.startsWith(localFilePrefix)) 
> execName = exec.substring(localFilePrefix.length()); 
> else execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Hadoop QA (Jira)]

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

Hadoop QA commented on OOZIE-3567:
--

PreCommit-OOZIE-Build started


> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
>  Labels: patch-available
> Fix For: 5.3.0
>
> Attachments: 
> [OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Failed: OOZIE-3320 PreCommit Build #1263

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 899.82 KB...]
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ oozie-distro ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
oozie-distro ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/distro/src/main/resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- modernizer-maven-plugin:1.8.0:modernizer (default-cli) @ 
oozie-distro ---
[INFO] 
[INFO] --< org.apache.oozie:oozie-zookeeper-security-tests >---
[INFO] Building Apache Oozie ZooKeeper Security Tests 5.3.0-SNAPSHOT[25/25]
[INFO] [ jar ]-
[INFO] 
[INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ 
oozie-zookeeper-security-tests ---
[INFO] Deleting 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/main/resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
oozie-zookeeper-security-tests ---
[INFO] No sources to compile
[INFO] 
[INFO] --- modernizer-maven-plugin:1.8.0:modernizer (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary for Apache Oozie Main 5.3.0-SNAPSHOT:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  0.916 s]
[INFO] Apache Oozie Fluent Job  SUCCESS [  0.074 s]
[INFO] Apache Oozie Fluent Job API  SUCCESS [  6.768 s]
[INFO] Apache Oozie Client  SUCCESS [  1.586 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  1.215 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  1.017 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  0.289 s]
[INFO] Apache Oozie Core .. SUCCESS [  7.449 s]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  1.461 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  1.246 s]
[INFO] Apache Oozie Share Lib Git . SUCCESS [  2.086 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  0.918 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  1.518 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  1.624 s]
[INFO] Apache Oozie Examples .. SUCCESS [  1.612 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [  2.115 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.016 s]
[INFO] Apache Oozie Docs .. SUCCESS [  0.035 s]
[INFO] Apache Oozie WebApp  SUCCESS [  1.821 s]
[INFO] Apache Oozie Tools . SUCCESS [  1.462 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.397 s]
[INFO] Apache Oozie Fluent Job Client . SUCCESS [  0.793 s]
[INFO] Apache Oozie Server  SUCCESS [  2.620 s]
[INFO] Apache Oozie Distro  SUCCESS [  1.963 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  1.743 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  45.307 s
[INFO] Finished at: 2019-12-06T14:31:07Z
[INFO] 
EXITVALUE 0
[TRACE] Modernizer output in HEAD verified and saved

Applying patch

Checking patch 
a/core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java => 
b/core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java...
error: 
a/core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java: 
No such file or directory
Checking 

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov commented on OOZIE-3320:
--

Can you close the issue since i open it at OOZIE-3567?

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3320
> URL: https://issues.apache.org/jira/browse/OOZIE-3320
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Roey Shem Tov
>Assignee: Roey Shem Tov
>Priority: Major
>  Labels: patch
> Attachments: OOZIE-3086.patch, OOZIE-3320.patch
>
>
> bash files that saved on shared mount, cannot be execute by the ShellAction 
> in proper way.
> Example:
> Worker-1,Worker-2,Worker-3 have shared mount /mnt/hadoop
> on /mnt/hadoop there is a file script.sh
> Right now there is two options to submit it using ShellAction:
>  # Upload it to hdfs, add it as a file and submit script.sh
>  # use bash as exec and file location (/mnt/hadoop/script.sh) as argument 
> (e.g bash>/exec>/mnt/hadoop/script.sh
> Best option is that the  command will support shared mounted file :
> /mnt/hadoop/script.sh
>  
> This code is taking only the file name instead it full path:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); 
> String execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
> Best option to support shared mount file is to support file:// starting for 
> bash files that are local (or shared by mount), e.g:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); String execName; 
> String localFilePrefix = "file://";
>  // When exec starts with 'file://' refer it as local file. 
> if (exec.startsWith(localFilePrefix)) 
> execName = exec.substring(localFilePrefix.length()); 
> else execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov updated OOZIE-3567:
-
 Flags: Patch  (was: Important)
Labels: patch-available  (was: )

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
>  Labels: patch-available
> Fix For: 5.3.0
>
> Attachments: 
> [OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov updated OOZIE-3567:
-
Attachment: (was: 
[OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch)

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: 
> [OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

[Hadoop QA (Jira)]

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

Hadoop QA commented on OOZIE-3320:
--

PreCommit-OOZIE-Build started


> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3320
> URL: https://issues.apache.org/jira/browse/OOZIE-3320
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Roey Shem Tov
>Assignee: Roey Shem Tov
>Priority: Major
>  Labels: patch
> Attachments: OOZIE-3086.patch, OOZIE-3320.patch
>
>
> bash files that saved on shared mount, cannot be execute by the ShellAction 
> in proper way.
> Example:
> Worker-1,Worker-2,Worker-3 have shared mount /mnt/hadoop
> on /mnt/hadoop there is a file script.sh
> Right now there is two options to submit it using ShellAction:
>  # Upload it to hdfs, add it as a file and submit script.sh
>  # use bash as exec and file location (/mnt/hadoop/script.sh) as argument 
> (e.g bash>/exec>/mnt/hadoop/script.sh
> Best option is that the  command will support shared mounted file :
> /mnt/hadoop/script.sh
>  
> This code is taking only the file name instead it full path:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); 
> String execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
> Best option to support shared mount file is to support file:// starting for 
> bash files that are local (or shared by mount), e.g:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); String execName; 
> String localFilePrefix = "file://";
>  // When exec starts with 'file://' refer it as local file. 
> if (exec.startsWith(localFilePrefix)) 
> execName = exec.substring(localFilePrefix.length()); 
> else execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov edited comment on OOZIE-3567 at 12/6/19 2:16 PM:
---

[~asalamon74] No different at all, I opened OOZIE-3320 a year ago(from another 
user) and saw right now it wasn`t resolved, so i prefer to resolve it from here 
(i changed my main user at jira+github).
  
  


was (Author: roeyshemtov):
[~asalamon74] No different at all, I opened OOZIE-3320 (from another user) and 
saw right now this wasn`t resolved, so i prefer to keep it from here (i changed 
main user at jira+github).
 
 

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: 
> [OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov commented on OOZIE-3567:
--

[~asalamon74] No different at all, I opened OOZIE-3320 (from another user) and 
saw right now this wasn`t resolved, so i prefer to keep it from here (i changed 
main user at jira+github).
 
 

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: 
> [OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

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

Roey Shem Tov updated OOZIE-3567:
-
Attachment: 
[OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch
External issue URL: https://github.com/apache/oozie/pull/47/files
   Description: 
as related in OOZIE-3320 im opening a new PR (me from different user), still 
can`t execute shell from mount at excpected.

 

File is not checked to be existed on resolveExecutable, because mount can be at 
the workers but not at the oozie servers (very common use).

  was:as related in OOZIE-3320 im opening a new PR (me from different user), 
still can`t execute shell from mount at excpected.


> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: 
> [OOZIE-3567]_Oozie_ShellAction_should_support_absolute_bash_file_path.patch
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.
>  
> File is not checked to be existed on resolveExecutable, because mount can be 
> at the workers but not at the oozie servers (very common use).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [oozie] roeyshemtov opened a new pull request #47: [OOZIE-3567] Oozie ShellAction should support absolute bash file path

[GitBox]

roeyshemtov opened a new pull request #47: [OOZIE-3567] Oozie ShellAction 
should support absolute bash file path
URL: https://github.com/apache/oozie/pull/47
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Andras Salamon (Jira)]

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

Andras Salamon commented on OOZIE-3567:
---

[~roeyshemtov] What is the difference between OOZIE-3320 and OOZIE-3567?

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3567
> URL: https://issues.apache.org/jira/browse/OOZIE-3567
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.2.0, 5.0.0, 5.1.0
>Reporter: Roey Shem Tov
>Priority: Major
> Fix For: 5.3.0
>
>
> as related in OOZIE-3320 im opening a new PR (me from different user), still 
> can`t execute shell from mount at excpected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (OOZIE-3567) Oozie ShellAction should support absolute bash file path

[Roey Shem Tov (Jira)]

Roey Shem Tov created OOZIE-3567:


 Summary: Oozie ShellAction should support absolute bash file path
 Key: OOZIE-3567
 URL: https://issues.apache.org/jira/browse/OOZIE-3567
 Project: Oozie
  Issue Type: Improvement
  Components: action
Affects Versions: 5.1.0, 5.0.0, 4.2.0
Reporter: Roey Shem Tov
 Fix For: 5.3.0


as related in OOZIE-3320 im opening a new PR (me from different user), still 
can`t execute shell from mount at excpected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (OOZIE-3557) [build] Update required minimum maven version

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on OOZIE-3557:


Commit 35bd1c95cb239751d7fa5af38595d2935567c507 in oozie's branch 
refs/heads/master from Kinga Marton
[ https://gitbox.apache.org/repos/asf?p=oozie.git;h=35bd1c9 ]

OOZIE-3557 [build] Update required minimum maven version (asalamon74 via 
kmarton)


> [build] Update required minimum maven version
> -
>
> Key: OOZIE-3557
> URL: https://issues.apache.org/jira/browse/OOZIE-3557
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0, 5.2.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3557-01.patch
>
>
> According to the Oozie [build 
> docs|https://github.com/apache/oozie/blob/master/docs/src/site/markdown/ENG_Building.md],
>  the minimum required maven version is 3.0.1.
> According to the pom.xml the minimum required version is 3.0.0
> According to the test of [~asasvari] Oozie cannot be compiled using maven 
> 3.3.9, which means we need to find the minimum required version and update 
> the documentation and the pom.xml
> The error message for maven 3.3.9:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.2:copy (copy-sharelib) 
> on project oozie-webapp: Unable to find/resolve artifact. 
> com.google.inject.ProvisionException: Unable to provision, see the following 
> errors:
> [ERROR] 
> [ERROR] 1) Error injecting: private org.eclipse.aether.spi.log.Logger 
> org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger
> [ERROR] while locating 
> org.apache.maven.repository.internal.DefaultVersionRangeResolver
> [ERROR] while locating java.lang.Object annotated with *
> [ERROR] at org.eclipse.sisu.wire.LocatorWiring
> [ERROR] while locating org.eclipse.aether.impl.VersionRangeResolver
> [ERROR] for parameter 2 at 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.(Unknown
>  Source)
> [ERROR] while locating 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector
> [ERROR] while locating java.lang.Object annotated with *
> [ERROR] at org.eclipse.sisu.wire.LocatorWiring {noformat}
>  
> According to my tests Oozie compiles using maven 3.5.3
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (OOZIE-3557) [build] Update required minimum maven version

[Kinga Marton (Jira)]

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

Kinga Marton commented on OOZIE-3557:
-

Thank you [~asalamon74] for the fix! +1, committed to master

> [build] Update required minimum maven version
> -
>
> Key: OOZIE-3557
> URL: https://issues.apache.org/jira/browse/OOZIE-3557
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0, 5.2.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3557-01.patch
>
>
> According to the Oozie [build 
> docs|https://github.com/apache/oozie/blob/master/docs/src/site/markdown/ENG_Building.md],
>  the minimum required maven version is 3.0.1.
> According to the pom.xml the minimum required version is 3.0.0
> According to the test of [~asasvari] Oozie cannot be compiled using maven 
> 3.3.9, which means we need to find the minimum required version and update 
> the documentation and the pom.xml
> The error message for maven 3.3.9:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.2:copy (copy-sharelib) 
> on project oozie-webapp: Unable to find/resolve artifact. 
> com.google.inject.ProvisionException: Unable to provision, see the following 
> errors:
> [ERROR] 
> [ERROR] 1) Error injecting: private org.eclipse.aether.spi.log.Logger 
> org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger
> [ERROR] while locating 
> org.apache.maven.repository.internal.DefaultVersionRangeResolver
> [ERROR] while locating java.lang.Object annotated with *
> [ERROR] at org.eclipse.sisu.wire.LocatorWiring
> [ERROR] while locating org.eclipse.aether.impl.VersionRangeResolver
> [ERROR] for parameter 2 at 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.(Unknown
>  Source)
> [ERROR] while locating 
> org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector
> [ERROR] while locating java.lang.Object annotated with *
> [ERROR] at org.eclipse.sisu.wire.LocatorWiring {noformat}
>  
> According to my tests Oozie compiles using maven 3.5.3
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Failed: OOZIE-3566 PreCommit Build #1262

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 2.15 MB...]
[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 [examples].
[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] SpotBugs diffs checked and reports created
[TRACE] Summary file size is 2536 bytes
[TRACE] Full summary file size is 1525 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO
  Running test-patch task MODERNIZER
  Running modernizer op=report
[TRACE] grep -c '.*ERROR.*Prefer' 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-clean.txt
[TRACE] Modernizer errors before patch: 51
[TRACE] grep -c '.*ERROR.*Prefer' 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-patch.txt
[TRACE] Modernizer errors after patch: 51


Testing JIRA OOZIE-3566

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)
+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 [docs].
+1 There are no new bugs found in [core].
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [sharelib/git].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/oozie].
+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 [tools].
+1 There are no new bugs found in [server].
+1 There are no new bugs found in [client].
+1 There are no new bugs found in [examples].
+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: 3199
Tests failed at first run:
TestBlockingInputStream#testLimitedWritingBlockingInputStream
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 
+1 MODERNIZER


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  34160 0  100  3416  0   2221  0:00:01  0:00:01 --:--:--  
{"self":"https://issues.apache.org/jira/rest/api/2/issue/13272512/comment/16989537","id":"16989537","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-3566) Wrong numbers provided by Oozie monitoring webservices.requests sampler

[Hadoop QA (Jira)]

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

Hadoop QA commented on OOZIE-3566:
--


Testing JIRA OOZIE-3566

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: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 [core].
.{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/sqoop].
.{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/oozie].
.{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 [tools].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [examples].
.{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: 3199
.{color:orange}Tests failed at first run:{color}
TestBlockingInputStream#testLimitedWritingBlockingInputStream
.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 MODERNIZER{color}


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


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

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



> Wrong numbers provided by Oozie monitoring webservices.requests sampler
> ---
>
> Key: OOZIE-3566
> URL: https://issues.apache.org/jira/browse/OOZIE-3566
> Project: Oozie
>  Issue Type: Bug
>Reporter: Maxim Kolesnikov
>Assignee: Maxim Kolesnikov
>Priority: Major
> Attachments: 
> [OOZIE-3566]_Wrong_numbers_provided_by_Oozie_monitoring_webservices_requests_sampler__org_.patch,
>  unnamed.png
>
>
> webservices.requests sampler based on 
> {code:java}
> org.apache.oozie.servlet.JsonRestServlet#TOTAL_REQUESTS_SAMPLER_COUNTER{code}
> may produce wrong results if
> {code:java}
> org.apache.oozie.servlet.JsonRestServlet#service{code}
> rises an Exception during request URL validation.
>  
> TOTAL_REQUESTS_SAMPLER_COUNTER is incremented in try block and decremented in 
> finally block right after that. But as validateRestUrl comes before the 
> counter is incremented it may lead to situation when counter is decremented 
> without being incremented before (in case of validation error).
>  
> Attached image is an example graph of webservices.requests being drawn in 
> Grafana via Graphite. Pay attention to Y-axis. While most nodes publish 
> positive numbers close to 0, some others seems to be shifted off by 1, with 
> results close to -1, util