date:20170405

[jira] Subscription: Oozie Patch Available

2017-04-05 Thread jira

Issue Subscription
Filter: Oozie Patch Available (98 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2851  spelling mistakes in examples
https://issues.apache.org/jira/browse/OOZIE-2851
OOZIE-2849  Fix build warnings when assembling directories
https://issues.apache.org/jira/browse/OOZIE-2849
OOZIE-2848  Override sharelib.tgz in distro when rebuilding Oozie
https://issues.apache.org/jira/browse/OOZIE-2848
OOZIE-2846  TestSSLServerConnectorFactory fails with Jetty 9.3 and 9.4
https://issues.apache.org/jira/browse/OOZIE-2846
OOZIE-2844  Increase stability of Oozie actions when log4j.properties is 
missing or not readable
https://issues.apache.org/jira/browse/OOZIE-2844
OOZIE-2843  Enhance logging inside ZKLocksService and MemoryLocksService
https://issues.apache.org/jira/browse/OOZIE-2843
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-2827  More directly view of the coordinator’s history from perspective of 
workflow action.
https://issues.apache.org/jira/browse/OOZIE-2827
OOZIE-2825  Custom Authentication doc page is not well formatted
https://issues.apache.org/jira/browse/OOZIE-2825
OOZIE-2824  Fix typos in documentation
https://issues.apache.org/jira/browse/OOZIE-2824
OOZIE-2818  Can't overwrite oozie.action.max.output.data on a per-workflow basis
https://issues.apache.org/jira/browse/OOZIE-2818
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2796  oozie.action.keep.action.dir not getting noticed
https://issues.apache.org/jira/browse/OOZIE-2796
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2785  Master is not compiling with hadoop-1 profile
https://issues.apache.org/jira/browse/OOZIE-2785
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2780  Upgrade hadoop-common version to 2.6.0
https://issues.apache.org/jira/browse/OOZIE-2780
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2769  Extend FS action to allow setrep on a file
https://issues.apache.org/jira/browse/OOZIE-2769
OOZIE-2751  LocalOozieClient is missing methods from OozieClient
https://issues.apache.org/jira/browse/OOZIE-2751
OOZIE-2746  Several tests failure in TestV2ValidateServlet.java
https://issues.apache.org/jira/browse/OOZIE-2746
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2733  change org.apache.hadoop.fs.permission.AccessControlException to 
org.apache.hadoop.security.AccessControlException
https://issues.apache.org/jira/browse/OOZIE-2733
OOZIE-2726  Flaky test due to daylight saving changes
https://issues.apache.org/jira/browse/OOZIE-2726
OOZIE-2718  Improve -dryrun for bundles
https://issues.apache.org/jira/browse/OOZIE-2718
OOZIE-2713  Provide an option to log out contents of the localized jar files
https://issues.apache.org/jira/browse/OOZIE-2713
OOZIE-2701  Oozie to support Multiple HCatalog URIs
https://issues.apache.org/jira/browse/OOZIE-2701
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693  SimpleHCatDependencyCache.removeMissingDependency can throw NPE
https://issues.apache.org/jira/browse/OOZIE-2693
OOZIE-2692  Oozie job submit doesn't report error message to user if there is 
any issue with job conf
https://issues.apache.org/jira/browse/OOZIE-2692
OOZIE-2684  Bad database schema error for WF_ACTIONS table
https://issues.apache.org/jira/browse/OOZIE-2684
OOZIE-2681  fix javadoc to compile on JDK8 again
https://issues.apache.org/jira/browse/OOZIE-2681
OOZIE-2670  Upgrade Hbase to 1.2
https://issues.apache.org/jira/browse/OOZIE-2670
OOZIE-2668  Status update and recovery problems when coord action and its 
children not in sync
https://issues.apache.org/jira/browse/OOZIE-2668
OOZIE-2662  DB migration fails if DB is too big
https://issues.apache.org/jira/browse/OOZIE-2662
OOZIE-2652  Skip trash while deleting hive table partition

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

2017-04-05 Thread Apache Jenkins Server

See

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

2017-04-05 Thread Apache Jenkins Server

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision ce7eb312b34d32841c85dde01cd24cf3e934fad4 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ce7eb312b34d32841c85dde01cd24cf3e934fad4
 > git rev-list ce7eb312b34d32841c85dde01cd24cf3e934fad4 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson6856562582710656911.sh
mkdir: cannot create directory 
':
 File exists
  % 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 
 120k0  120k0 0   134k  0 --:--:-- --:--:-- --:--:--  134k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

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

2017-04-05 Thread Steven Hancz (JIRA)


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

Steven Hancz commented on OOZIE-2854:
-

Peter,

I am glad that you found this issue. I just built two labs to test an HA 
solution for cluster metadata storage. It makes no sense to have a hadoop 
cluster and a single MySQL failure will bring it down.

So far I build a Galera MySQL cluster and Galera MariaDB cluster but I have not 
pointed hadoop to it just imported the data. NDB clustering will not work as it 
does not uses the InnoDB engine and the import will fail.

I also have a case opened with Cloudera on this matter that I am waiting on.
Galera cluster states that it is synchronous 
https://mariadb.com/kb/en/mariadb/about-galera-replication/ 
but your findings are different.

All I want to do is to have a metadata storage that is not prone to a single 
point of failure. Have you run similar test with Oracle RAC? 

Steven

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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

2017-04-05 Thread Apache Jenkins Server

See

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

2017-04-05 Thread Apache Jenkins Server

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision ce7eb312b34d32841c85dde01cd24cf3e934fad4 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ce7eb312b34d32841c85dde01cd24cf3e934fad4
 > git rev-list ce7eb312b34d32841c85dde01cd24cf3e934fad4 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson6298438327169818233.sh
mkdir: cannot create directory 
':
 File exists
  % 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 
 551k0  551k0 0   386k  0 --:--:--  0:00:01 --:--:--  386k100 
1295k0 1295k0 0   531k  0 --:--:--  0:00:02 --:--:--  531k100 
1815k0 1815k0 0   529k  0 --:--:--  0:00:03 --:--:--  529k100 
1887k0 1887k0 0   506k  0 --:--:--  0:00:03 --:--:--  506k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Commented] (OOZIE-2846) TestSSLServerConnectorFactory fails with Jetty 9.3 and 9.4

2017-04-05 Thread Attila Sasvari (JIRA)


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

Attila Sasvari commented on OOZIE-2846:
---

[~gezapeti] thanks a lot for the patch, +1 (non-binding)

> TestSSLServerConnectorFactory fails with Jetty 9.3 and 9.4
> --
>
> Key: OOZIE-2846
> URL: https://issues.apache.org/jira/browse/OOZIE-2846
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2846.001.patch, OOZIE-2846.002.patch
>
>
> We've tested using Oozie with different Jetty versions and found that the 
> test TestSSLServerConnectorFactory is failing for newer Jetty versions.
> Changing the @Mock to @Spy on the Server solves the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2860) Improve Jetty logging

2017-04-05 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2860:

Description: 
At the moment only Oozie server logs are written by Jetty, but not its own 
[*server 
logs*|https://www.eclipse.org/jetty/documentation/9.3.x/configuring-logging.html].

The Oozie 4.3.0 Tomcat logs are written to 
{{$\{OOZIE_DIR\}/logs/catalina--mm-dd.log}}. It's necessary to have the 
same log location and file pattern (rollover each day), but not necessary to 
have the same filename prefix. It's also a must to have the same log format 
like the Tomcat one. It's nice to have log levels per package configurable via 
{{oozie-default.xml}}.

  was:
At the moment only Oozie server logs are written by Jetty, but not its own 
[*server 
logs*|https://www.eclipse.org/jetty/documentation/9.3.x/configuring-logging.html].

The Oozie 4.3.0 Tomcat logs are written to 
{{$\{OOZIE_DIR\}/log/catalina--mm-dd.log}}. It's necessary to have the same 
log location and file pattern (rollover each day), but not necessary to have 
the same filename prefix. It's also a must to have the same log format like the 
Tomcat one. It's nice to have log levels per package configurable via 
{{oozie-default.xml}}.


> Improve Jetty logging
> -
>
> Key: OOZIE-2860
> URL: https://issues.apache.org/jira/browse/OOZIE-2860
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
>
> At the moment only Oozie server logs are written by Jetty, but not its own 
> [*server 
> logs*|https://www.eclipse.org/jetty/documentation/9.3.x/configuring-logging.html].
> The Oozie 4.3.0 Tomcat logs are written to 
> {{$\{OOZIE_DIR\}/logs/catalina--mm-dd.log}}. It's necessary to have the 
> same log location and file pattern (rollover each day), but not necessary to 
> have the same filename prefix. It's also a must to have the same log format 
> like the Tomcat one. It's nice to have log levels per package configurable 
> via {{oozie-default.xml}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2860) Improve Jetty logging

2017-04-05 Thread Andras Piros (JIRA)

Andras Piros created OOZIE-2860:
---

 Summary: Improve Jetty logging
 Key: OOZIE-2860
 URL: https://issues.apache.org/jira/browse/OOZIE-2860
 Project: Oozie
  Issue Type: Improvement
  Components: core
Affects Versions: 5.0.0
Reporter: Andras Piros
Assignee: Andras Piros
 Fix For: 5.0.0


At the moment only Oozie server logs are written by Jetty, but not its own 
[*server 
logs*|https://www.eclipse.org/jetty/documentation/9.3.x/configuring-logging.html].

The Oozie 4.3.0 Tomcat logs are written to 
{{$\{OOZIE_DIR\}/log/catalina--mm-dd.log}}. It's necessary to have the same 
log location and file pattern (rollover each day), but not necessary to have 
the same filename prefix. It's also a must to have the same log format like the 
Tomcat one. It's nice to have log levels per package configurable via 
{{oozie-default.xml}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2859) Can't compile oozie master

2017-04-05 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2859:
---

I managed to compile Oozie after adding the conjars repo into the pom.xml:
{noformat}

  conjars.org
  http://conjars.org/repo

{noformat}


> Can't compile oozie master
> --
>
> Key: OOZIE-2859
> URL: https://issues.apache.org/jira/browse/OOZIE-2859
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>
> I have cleared out my local maven cache and I can't compile Oozie master ever 
> since. The error I'm getting is :
> {noformat}
> [ERROR] Failed to execute goal on project oozie-core: Could not resolve 
> dependencies for project org.apache.oozie:oozie-core:jar:4.4.0-SNAPSHOT: 
> Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in 
> http://repo1.maven.org/maven2 was cached in the local repository, resolution 
> will not be reattempted until the update interval of central has elapsed or 
> updates are forced -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :oozie-core
> {noformat}
> This dependency comes in via hive-exec. 
> Did anyone bumped into this issue here? 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2859) Can't compile oozie master

2017-04-05 Thread Peter Cseh (JIRA)

Peter Cseh created OOZIE-2859:
-

 Summary: Can't compile oozie master
 Key: OOZIE-2859
 URL: https://issues.apache.org/jira/browse/OOZIE-2859
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Cseh


I have cleared out my local maven cache and I can't compile Oozie master ever 
since. The error I'm getting is :
{noformat}
[ERROR] Failed to execute goal on project oozie-core: Could not resolve 
dependencies for project org.apache.oozie:oozie-core:jar:4.4.0-SNAPSHOT: 
Failure to find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in 
http://repo1.maven.org/maven2 was cached in the local repository, resolution 
will not be reattempted until the update interval of central has elapsed or 
updates are forced -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :oozie-core
{noformat}

This dependency comes in via hive-exec. 
Did anyone bumped into this issue here? 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

2017-04-05 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2701:
---

Thanks for the clarification [~abhishekbafna]! +1


> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch, OOZIE-2701-04.patch, 
> OOZIE-2701-05.patch, OOZIE-2701-06.patch, OOZIE-2701-07.patch, 
> OOZIE-2701-08.patch, OOZIE-2701-09.patch, OOZIE-2701-10.patch, 
> OOZIE-2701-11.patch, OOZIE-2701-12.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

2017-04-05 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2850:
---

Thanks [~asasvari]! committed to master!

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch, 
> OOZIE-2850-06.patch, OOZIE-2850-07.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

2017-04-05 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2850:
--

Testing JIRA OOZIE-2850

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color: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:orange}0{color} There are [1] new bugs found in total that would be nice 
to have fixed.
. {color:orange}0{color} There are [1] new bugs found in [server] that would be 
nice to have fixed.
. You can find the FindBugs diff here: server/findbugs-new.html
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {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/hcatalog].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
{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: 1907
.Tests rerun: 2
.Tests failed at first run: 
org.apache.oozie.command.coord.TestCoordActionsKillXCommand,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


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

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

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch, 
> OOZIE-2850-06.patch, OOZIE-2850-07.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Jenkins build is back to normal : oozie-trunk-precommit-build #3777

2017-04-05 Thread Apache Jenkins Server

See

[jira] [Commented] (OOZIE-2844) Increase stability of Oozie actions when log4j.properties is missing or not readable

2017-04-05 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2844:
--

Testing JIRA OOZIE-2844

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 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} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{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 [333] new bugs found below threshold in total 
that must be fixed.
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {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/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:red}-1{color} There are [327] new bugs found below threshold in 
[server] that must be fixed, listing only the first [5] ones.
. You can find the FindBugs diff here (look for the red and orange ones): 
server/findbugs-new.html
. The top [5] most important FindBugs errors are:
. At BinaryBlob.java:[line 68]: org.apache.oozie.BinaryBlob.getBytes() may 
expose internal representation by returning BinaryBlob.bytes
. org.apache.oozie.BinaryBlob.getRawBlob() may expose internal representation 
by returning BinaryBlob.rawBlob: Another occurrence at BinaryBlob.java:[line 88]
. Another occurrence at BinaryBlob.java:[line 116]: At BinaryBlob.java:[line 99]
. At BinaryBlob.java:[line 43]: new org.apache.oozie.BinaryBlob(byte[], 
boolean) may expose internal representation by storing an externally mutable 
object into BinaryBlob.bytes
. At BinaryBlob.java:[line 47]: new org.apache.oozie.BinaryBlob(byte[], 
boolean) may expose internal representation by storing an externally mutable 
object into BinaryBlob.rawBlob
. {color:green}+1{color} There are no new bugs found in [core].
. {color:red}-1{color} There are [6] new bugs found below threshold in 
[hadooplibs/hadoop-utils-2] that must be fixed, listing only the first [5] ones.
. You can find the FindBugs diff here (look for the red and orange ones): 
hadooplibs/hadoop-utils-2/findbugs-new.html
. The top [5] most important FindBugs errors are:
. At DateList.java:[line 55]: Nullcheck of date at line 55 of value previously 
dereferenced in org.apache.oozie.example.DateList.main(String[])
. Private method org.apache.oozie.example.DateList.formatDateUTC(Calendar) is 
never called: Redundant null check at DateList.java:[line 62]
. org.apache.oozie.example.LocalOozieExample.execute(String[]) may fail to 
clean up java.io.InputStream: At DateList.java:[line 97]
. Path continues at LocalOozieExample.java:[line 76]: Obligation to clean up 
resource created at LocalOozieExample.java:[line 72] is not discharged
. Path continues at LocalOozieExample.java:[line 78]: Path continues at 
LocalOozieExample.java:[line 77]
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Increase stability of Oozie actions when log4j.properties is missing or not 
> readable
> -

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

2017-04-05 Thread Apache Jenkins Server

See 


--
[...truncated 875.28 KB...]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
oozie-zookeeper-security-tests ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  4.924 s]
[INFO] Apache Oozie Hadoop Utils hadoop-2-4.4.0-SNAPSHOT .. SUCCESS [  3.331 s]
[INFO] Apache Oozie Hadoop Distcp hadoop-2-4.4.0-SNAPSHOT . SUCCESS [  0.257 s]
[INFO] Apache Oozie Hadoop Auth hadoop-2-4.4.0-SNAPSHOT Test SUCCESS [  0.455 s]
[INFO] Apache Oozie Hadoop Libs ... SUCCESS [  0.032 s]
[INFO] Apache Oozie Client  SUCCESS [ 39.405 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  3.889 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  5.768 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  1.063 s]
[INFO] Apache Oozie Core .. SUCCESS [01:16 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  5.466 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  8.223 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [ 10.330 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  7.097 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  1.140 s]
[INFO] Apache Oozie Examples .. SUCCESS [  4.961 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 24.049 s]
[INFO] Apache Oozie Share Lib . SUCCESS [01:08 min]
[INFO] Apache Oozie Docs .. SUCCESS [ 30.764 s]
[INFO] Apache Oozie WebApp  SUCCESS [01:22 min]
[INFO] Apache Oozie Tools . SUCCESS [  6.083 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.031 s]
[INFO] Apache Oozie Server  SUCCESS [  9.522 s]
[INFO] Apache Oozie Distro  SUCCESS [02:22 min]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  5.335 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 09:07 min
[INFO] Finished at: 2017-04-05T11:25:29+00:00
[INFO] Final Memory: 115M/1113M
[INFO] 

Reports
  Running test-patch task CLEAN
  Running test-patch task RAW_PATCH_ANALYSIS
  Running test-patch task RAT
  Running test-patch task JAVADOC
  Running test-patch task COMPILE
  Running test-patch task FINDBUGS_DIFF
[TRACE] Downloading FindBugs diff JAR from 
https://repo1.maven.org/maven2/me/andrz/findbugs/findbugs-diff/0.1.0/findbugs-diff-0.1.0-all.jar
[TRACE] FindBugs diff JAR downloaded
grep: 
:
 No such file or directory
[TRACE] FindBugs diff JAR checked, is safe to use
[TRACE] Performing FindBugs diffs
bin/test-patch-11-findbugs-diff: line 253: : No such file or directory
bin/test-patch-11-findbugs-diff: line 255: [: -le: unary operator expected
Exception in thread "main" groovy.lang.GroovyRuntimeException: Ambiguous method 
overloading for method java.io.File#.
Cannot resolve which method to invoke for [null] due to overlapping prototypes 
between:
[class java.lang.String]
[class java.net.URI]
at 
groovy.lang.MetaClassImpl.chooseMostSpecificParams(MetaClassImpl.java:3202)
at 
groovy.lang.MetaClassImpl.chooseMethodInternal(MetaClassImpl.java:3154)
at groovy.lang.MetaClassImpl.chooseMethod(MetaClassImpl.java:3097)
at 
groovy.lang.MetaClassImpl.createConstructorSite(MetaClassImpl.java:3384)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallConstructorSite(CallSiteArray.java:88)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:182)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:1

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

2017-04-05 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2850:
---

Yes, other endpoints are responding with 403 to my requests.
+1 for patch -7

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch, 
> OOZIE-2850-06.patch, OOZIE-2850-07.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

2017-04-05 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2850:
--

Testing JIRA OOZIE-2850

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color: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:orange}0{color} There are [1] new bugs found in total that would be nice 
to have fixed.
. {color:orange}0{color} There are [1] new bugs found in [server] that would be 
nice to have fixed.
. You can find the FindBugs diff here: server/findbugs-new.html
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
{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: 1907
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


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

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

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch, 
> OOZIE-2850-06.patch, OOZIE-2850-07.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Jenkins build is back to normal : oozie-trunk-precommit-build #3775

2017-04-05 Thread Apache Jenkins Server

See

[jira] [Updated] (OOZIE-2850) Fix default callback notifications

2017-04-05 Thread Attila Sasvari (JIRA)


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

Attila Sasvari updated OOZIE-2850:
--
Attachment: OOZIE-2850-07.patch

@rkanter thanks for the reivew

Attaching new patch because my IDE tricked me, and the \t remained there.

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch, 
> OOZIE-2850-06.patch, OOZIE-2850-07.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2844) Increase stability of Oozie actions when log4j.properties is missing or not readable

2017-04-05 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2844:

Attachment: OOZIE-2844.003.patch

Addressing review comments.

> Increase stability of Oozie actions when log4j.properties is missing or not 
> readable
> 
>
> Key: OOZIE-2844
> URL: https://issues.apache.org/jira/browse/OOZIE-2844
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 4.3.0
>
> Attachments: OOZIE-2844.001.patch, OOZIE-2844.002.patch, 
> OOZIE-2844.003.patch
>
>
> In several Oozie actions we face the problem that if {{log4j.properties}} is 
> not readable by current thread, or not present on the classpath, while taking 
> an {{URL.openStream()}} call afterwards, an {{IOException}} is thrown and the 
> action won't run.
> Such actions are:
> * 
> [*{{DistcpMain}}*|https://github.com/apache/oozie/blob/master/sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java#L135]
> * 
> [*{{HiveMain}}*|https://github.com/apache/oozie/blob/master/sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java#L146]
> * 
> [*{{PigMain}}*|https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java#L173]
> * 
> [*{{PigMainWithOldApi}}*|https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java#L160]
> * 
> [*{{SparkMain}}*|https://github.com/apache/oozie/blob/master/sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java#L430]
> * 
> [*{{SqoopMain}}*|https://github.com/apache/oozie/blob/master/sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java#L124]
> Extend 
> [*{{LauncherMain.run()}}*|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java#L62-L65]
>  by a convenience method that loads Hadoop's {{log4j.properties}} in 
> beforehand. In case {{URL.openStream()}} would throw {{IOException}} we 
> resort to a call to a new file {{hadoop-default-log4j.properties}} on the 
> classpath (packaged along w/ {{LauncherMain.class}}) that has the same 
> contents as the {{log4j.properties}} that is not accessible / readable / 
> present.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 58171: OOZIE-2844 Increase stability of Oozie actions when log4j.properties is missing or not readable

2017-04-05 Thread András Piros


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

(Updated April 5, 2017, 8:47 a.m.)


Review request for oozie and Peter Bacsko.


Changes
---

Addressing review comments.


Repository: oozie-git


Description
---

In several Oozie actions we face the problem that if `log4j.properties` is not 
readable by current thread, or not present on the classpath, while taking an 
`URL.openStream()` call afterwards, an `IOException` is thrown and the action 
won't run.

Such actions are:

* 
[`DistcpMain`](https://github.com/apache/oozie/blob/master/sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java#L135)
* 
[`HiveMain`](https://github.com/apache/oozie/blob/master/sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java#L146)
* 
[`PigMain`](https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java#L173)
* 
[`PigMainWithOldApi`](https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java#L160)
* 
[`SparkMain`](https://github.com/apache/oozie/blob/master/sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java#L430)
* 
[`SqoopMain`](https://github.com/apache/oozie/blob/master/sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java#L124)

Extend 
[`LauncherMain.run()`](https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java#L62-L65)
 by a convenience method that loads Hadoop's `log4j.properties` in beforehand. 
In case `URL.openStream()` would throw `IOException` we resort to a call to a 
new file `hadoop-default-log4j.properties` on the classpath (packaged along w/ 
`LauncherMain.class`) that has the same contents as the `log4j.properties` that 
is not accessible / readable / present.


Diffs (updated)
-

  sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java 
fcaadefd215368565fb126ca92515792e1f1a09b 
  sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java 
f314bab3808c41f2576f8f64d9fdf8f34e578042 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
7ae48e168a310b4d55feda7cbce8b2d29c2ec505 
  sharelib/oozie/src/main/resources/default-log4j.properties PRE-CREATION 
  
sharelib/oozie/src/test/java/org/apache/oozie/action/hadoop/TestLauncherMain.java
 PRE-CREATION 
  sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java 
ba393eee53e92d144159f83893d4baab00737a44 
  
sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java
 14ab65e7d00c426036ced3e80400c80deea0e282 
  sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java 
88de5c4c614a5cc33c1f4760d2510928ba4b8ede 
  sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java 
cb8f56e9b66de0eb2799e68bc56d0ee36d4ba317 


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

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


Testing
---

Relevant unit tests run.


Thanks,

András Piros

[jira] [Assigned] (OOZIE-2829) Improve sharelib upload to accept multiple source folders

2017-04-05 Thread Attila Sasvari (JIRA)


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

Attila Sasvari reassigned OOZIE-2829:
-

Assignee: Attila Sasvari

> Improve sharelib upload to accept multiple source folders
> -
>
> Key: OOZIE-2829
> URL: https://issues.apache.org/jira/browse/OOZIE-2829
> Project: Oozie
>  Issue Type: Bug
>  Components: tools
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
>
> Right now sharelib can be created via {{sharelib create -fs FS_URI -locallib 
> SHARED_LIBRARY}} where the SHARED_LIBRARY can be a tarbal or a folder. 
> It would be nice to have the possibility to define additional folders to be 
> uploaded into the sharelib, so the users don't have to copy or link the files 
> together on their machine.
> The syntax could be something like -additional-lib 
> sharelibName=/path/to/source/;/path/to/some/file,sharelibName2=/path/to/some/folder



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 58171: OOZIE-2844 Increase stability of Oozie actions when log4j.properties is missing or not readable

2017-04-05 Thread András Piros



> On April 4, 2017, 11:31 a.m., Peter Bacsko wrote:
> > sharelib/oozie/src/main/resources/auxiliary-log4j.properties
> > Lines 1 (patched)
> > 
> >
> > Where does the contents of this file come from?

Taken mostly from Hadoop's 
[`default-log4.properties`](https://github.com/apache/hadoop/blob/f67237cbe7bc48a1b9088e990800b37529f1db2a/hadoop-hdfs-project/hadoop-hdfs-httpfs/src/main/resources/default-log4j.properties).


- András


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


On April 4, 2017, 10:37 a.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/58171/
> ---
> 
> (Updated April 4, 2017, 10:37 a.m.)
> 
> 
> Review request for oozie and Peter Bacsko.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> In several Oozie actions we face the problem that if `log4j.properties` is 
> not readable by current thread, or not present on the classpath, while taking 
> an `URL.openStream()` call afterwards, an `IOException` is thrown and the 
> action won't run.
> 
> Such actions are:
> 
> * 
> [`DistcpMain`](https://github.com/apache/oozie/blob/master/sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java#L135)
> * 
> [`HiveMain`](https://github.com/apache/oozie/blob/master/sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java#L146)
> * 
> [`PigMain`](https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java#L173)
> * 
> [`PigMainWithOldApi`](https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java#L160)
> * 
> [`SparkMain`](https://github.com/apache/oozie/blob/master/sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java#L430)
> * 
> [`SqoopMain`](https://github.com/apache/oozie/blob/master/sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java#L124)
> 
> Extend 
> [`LauncherMain.run()`](https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java#L62-L65)
>  by a convenience method that loads Hadoop's `log4j.properties` in 
> beforehand. In case `URL.openStream()` would throw `IOException` we resort to 
> a call to a new file `hadoop-default-log4j.properties` on the classpath 
> (packaged along w/ `LauncherMain.class`) that has the same contents as the 
> `log4j.properties` that is not accessible / readable / present.
> 
> 
> Diffs
> -
> 
>   
> sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java 
> fcaadefd215368565fb126ca92515792e1f1a09b 
>   sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java 
> bc8ab29c25405806f40232d32254ba2a7f5271e4 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
> 7ae48e168a310b4d55feda7cbce8b2d29c2ec505 
>   sharelib/oozie/src/main/resources/auxiliary-log4j.properties PRE-CREATION 
>   
> sharelib/oozie/src/test/java/org/apache/oozie/action/hadoop/TestLauncherMain.java
>  PRE-CREATION 
>   sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java 
> ba393eee53e92d144159f83893d4baab00737a44 
>   
> sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java
>  14ab65e7d00c426036ced3e80400c80deea0e282 
>   sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java 
> c24d95c88be0dbf6fe80241d887a70100a5e1b4a 
>   sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java 
> cb8f56e9b66de0eb2799e68bc56d0ee36d4ba317 
> 
> 
> Diff: https://reviews.apache.org/r/58171/diff/1/
> 
> 
> Testing
> ---
> 
> Relevant unit tests run.
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] Subscription: Oozie Patch Available

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

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

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

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

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

[jira] [Commented] (OOZIE-2846) TestSSLServerConnectorFactory fails with Jetty 9.3 and 9.4

[jira] [Updated] (OOZIE-2860) Improve Jetty logging

[jira] [Created] (OOZIE-2860) Improve Jetty logging

[jira] [Commented] (OOZIE-2859) Can't compile oozie master

[jira] [Created] (OOZIE-2859) Can't compile oozie master

[jira] [Commented] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

Jenkins build is back to normal : oozie-trunk-precommit-build #3777

[jira] [Commented] (OOZIE-2844) Increase stability of Oozie actions when log4j.properties is missing or not readable

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

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

Jenkins build is back to normal : oozie-trunk-precommit-build #3775

[jira] [Updated] (OOZIE-2850) Fix default callback notifications

[jira] [Updated] (OOZIE-2844) Increase stability of Oozie actions when log4j.properties is missing or not readable

Re: Review Request 58171: OOZIE-2844 Increase stability of Oozie actions when log4j.properties is missing or not readable

[jira] [Assigned] (OOZIE-2829) Improve sharelib upload to accept multiple source folders

Re: Review Request 58171: OOZIE-2844 Increase stability of Oozie actions when log4j.properties is missing or not readable

25 matches

Site Navigation

Mail list logo

Footer information