date:20180329

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

2018-03-29 Thread Robert Kanter

Here's what I did:
- Verified sha512
- Verified signature (gpg)
- Looked at rat report
- Looked at release log
- Built Oozie against Hadoop 2.7.2, using an empty local maven repo
- Ran a few of the examples, clicked around the UI, tried various CLI
commands, looked at the REST output, launcher log output, etc

+1 LGTM

Non-blocker issues which I've filed JIRAs for
- OOZIE-3206 : The
README.txt links to the 4.3.0 version of the quickstart page:
http://oozie.apache.org/docs/4.3.0/DG_QuickStart.html
- OOZIE-3207 : We're
using version 17 of the ASF root pom, and the latest is 19.  version 17 is
from 2015!
- OOZIE-3208 : If the
sharelib isn't installed, you get a "It should never happen" error code
when submitting an action

If a blocking issue is found, OOZIE-3206 and OOZIE-3208 would be
nice-to-have's in an RC1 (OOZIE-3207 is too risky).  Otherwise, we can save
them for Oozie 5.1.0.


thanks
- Robert


On Thu, Mar 29, 2018 at 11:00 AM, Attila Sasvari 
wrote:

> Thanks Andras for driving the release!
>
> +1
>
> Here is what I did:
> - Verified signature, hash
> - Created Oozie 5.0.0 distro using hadoop-2.6
> - On a pseudo Hadoop 2.6.0, I executed  SparkFileCopy (both in
> yarn-cluster, yarn-client mode),  custom-main-wf, datelist-java-main-wf,
> demo-wf, distcp-wf, hadoop-el-wf, java-main-wf, map-reduce-wf, no-op-wf,
> pig-wf, shell-wf, sqoop-freeform-wf, sqoop-wf, ssh-wf, streaming-wf,
> subwf-wf  - all the workflows have succeeded
> - Verified Web UI: version, getting logs and Job DAG
>
>
> On Wed, Mar 28, 2018 at 4:30 PM, Artem Ervits 
> wrote:
> >
> > additionally, I've ran the mvn verify and after some time it failed due
> to
> > timeout, still OK in my opinion.
> >
> > INFO] Results:
> > [INFO]
> > [INFO] Tests run: 738, Failures: 0, Errors: 0, Skipped: 0
> > [INFO]
> > [INFO]
> > 
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache Oozie Main 5.0.0  SUCCESS [
> > 3.859 s]
> > [INFO] Apache Oozie Client  SUCCESS [
> > 34.826 s]
> > [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [
> > 25.740 s]
> > [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [
> > 11.842 s]
> > [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [
> > 7.465 s]
> > [INFO] Apache Oozie Core .. FAILURE [
> > 01:30 h]
> > [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> > [INFO] Apache Oozie Share Lib Pig . SKIPPED
> > [INFO] Apache Oozie Share Lib Hive  SKIPPED
> > [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> > [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> > [INFO] Apache Oozie Examples .. SKIPPED
> > [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> > [INFO] Apache Oozie Share Lib . SKIPPED
> > [INFO] Apache Oozie Docs .. SKIPPED
> > [INFO] Apache Oozie WebApp  SKIPPED
> > [INFO] Apache Oozie Tools . SKIPPED
> > [INFO] Apache Oozie MiniOozie . SKIPPED
> > [INFO] Apache Oozie Server  SKIPPED
> > [INFO] Apache Oozie Distro  SKIPPED
> > [INFO] Apache Oozie ZooKeeper Security Tests 5.0.0  SKIPPED
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Total time: 01:32 h
> > [INFO] Finished at: 2018-03-28T14:21:30Z
> > [INFO]
> > 
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test
> (default-test)
> > on project oozie-core: There was a timeout or other error in the fork ->
> > [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/MojoFailureException
> > [ERROR]
> > [ERROR] After correcting the problems, you can resume the build with the
> > command
> > [ERROR]   mvn  -rf :oozie-core
> >
> > On Wed, Mar 28, 2018 at 8:50 AM, Artem Ervits 
> wrote:
> >
> > > +1 non-binding
> > >
> > > signatures and checksum: OK
> > > build

[jira] [Updated] (OOZIE-3208) "It should never happen" error code when running an action when Sharelib doesn't exist

2018-03-29 Thread Robert Kanter (JIRA)


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

Robert Kanter updated OOZIE-3208:
-
Description: 
If you forget to install the sharelib and you try to run a workflow, the action 
will fail (as expected), but the error code will be "It should never happen".  
That's not a good error code :D

{noformat}
2018-03-29 14:35:02,361  WARN ActionStartXCommand:523 - 
SERVER[rkanter-MBP.local] USER[rkanter] GROUP[-] TOKEN[] APP[map-reduce-wf] 
JOB[000-180329142919509-oozie-rkan-W] 
ACTION[000-180329142919509-oozie-rkan-W@mr-node] Error starting action 
[mr-node]. ErrorType [FAILED], ErrorCode [It should never happen], Message 
[File /user/rkanter/share/lib does not exist]
org.apache.oozie.action.ActionExecutorException: File /user/rkanter/share/lib 
does not exist
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.addSystemShareLibForAction(JavaActionExecutor.java:646)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.addAllShareLibs(JavaActionExecutor.java:760)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.setLibFilesArchives(JavaActionExecutor.java:746)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:984)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1512)
at 
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:243)
at 
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:68)
at org.apache.oozie.command.XCommand.call(XCommand.java:290)
at 
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:334)
at 
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:263)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:181)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
{noformat}
Error starting action [mr-node]. ErrorType [FAILED], ErrorCode [It should never 
happen]
{noformat}

  was:
If you forget to install the sharelib and you try to run a workflow, the action 
will fail (as expected), but the error code will be "It should never happen".  
That's not a good error code :D

{noformat}
2018-03-29 14:35:02,361  WARN ActionStartXCommand:523 - 
SERVER[rkanter-MBP.local] USER[rkanter] GROUP[-] TOKEN[] APP[map-reduce-wf] 
JOB[000-180329142919509-oozie-rkan-W] 
ACTION[000-180329142919509-oozie-rkan-W@mr-node] Error starting action 
[mr-node]. ErrorType [FAILED], ErrorCode [It should never happen], Message 
[File /user/rkanter/share/lib does not exist]
org.apache.oozie.action.ActionExecutorException: File /user/rkanter/share/lib 
does not exist
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.addSystemShareLibForAction(JavaActionExecutor.java:646)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.addAllShareLibs(JavaActionExecutor.java:760)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.setLibFilesArchives(JavaActionExecutor.java:746)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:984)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1512)
at 
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:243)
at 
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:68)
at org.apache.oozie.command.XCommand.call(XCommand.java:290)
at 
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:334)
at 
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:263)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:181)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}


> "It should never happen" error code when running an action when Sharelib 
> doesn't exist
> --
>
> Key: OOZIE-3208
> URL: https://issues.apache.org/jira/browse/OOZIE-3208
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>

[jira] [Created] (OOZIE-3208) "It should never happen" error code when running an action when Sharelib doesn't exist

2018-03-29 Thread Robert Kanter (JIRA)

Robert Kanter created OOZIE-3208:


 Summary: "It should never happen" error code when running an 
action when Sharelib doesn't exist
 Key: OOZIE-3208
 URL: https://issues.apache.org/jira/browse/OOZIE-3208
 Project: Oozie
  Issue Type: Bug
Affects Versions: 5.0.0
Reporter: Robert Kanter
 Fix For: 5.1.0


If you forget to install the sharelib and you try to run a workflow, the action 
will fail (as expected), but the error code will be "It should never happen".  
That's not a good error code :D

{noformat}
2018-03-29 14:35:02,361  WARN ActionStartXCommand:523 - 
SERVER[rkanter-MBP.local] USER[rkanter] GROUP[-] TOKEN[] APP[map-reduce-wf] 
JOB[000-180329142919509-oozie-rkan-W] 
ACTION[000-180329142919509-oozie-rkan-W@mr-node] Error starting action 
[mr-node]. ErrorType [FAILED], ErrorCode [It should never happen], Message 
[File /user/rkanter/share/lib does not exist]
org.apache.oozie.action.ActionExecutorException: File /user/rkanter/share/lib 
does not exist
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.addSystemShareLibForAction(JavaActionExecutor.java:646)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.addAllShareLibs(JavaActionExecutor.java:760)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.setLibFilesArchives(JavaActionExecutor.java:746)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:984)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1512)
at 
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:243)
at 
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:68)
at org.apache.oozie.command.XCommand.call(XCommand.java:290)
at 
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:334)
at 
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:263)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:181)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}



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

[jira] [Created] (OOZIE-3207) Update ASF root pom version

2018-03-29 Thread Robert Kanter (JIRA)

Robert Kanter created OOZIE-3207:


 Summary: Update ASF root pom version
 Key: OOZIE-3207
 URL: https://issues.apache.org/jira/browse/OOZIE-3207
 Project: Oozie
  Issue Type: Bug
  Components: build
Affects Versions: 5.0.0
Reporter: Robert Kanter
 Fix For: 5.1.0


The Oozie root pom uses the ASF root pom as it's parent (as required by ASF 
rules).  We're currently using version 17, which is from 2015.  The current 
version is 19, from earlier this year (2018).  We should update this.  

You can see more details about the ASF root pom, including diffs between each 
version here:
https://maven.apache.org/pom/asf/index.html

This may require some testing or at least looking into because the ASF root pom 
defines the versions of some things, especially maven plugins, and so things 
may break or be incompatible.



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

[jira] [Created] (OOZIE-3206) The README.txt file refers to the 4.3.0 Quickstart docs

2018-03-29 Thread Robert Kanter (JIRA)

Robert Kanter created OOZIE-3206:


 Summary: The README.txt file refers to the 4.3.0 Quickstart docs
 Key: OOZIE-3206
 URL: https://issues.apache.org/jira/browse/OOZIE-3206
 Project: Oozie
  Issue Type: Bug
  Components: docs
Affects Versions: 5.0.0
Reporter: Robert Kanter
 Fix For: 5.1.0


The README.txt file refers to the 4.3.0 Quickstart docs.  It should refer to 
whatever the current version we're on is.
http://oozie.apache.org/docs/4.3.0/DG_QuickStart.html 

It might be a good idea to update our website with a /docs/current/*.html site 
so that we don't have to keep updating this, as long as we update the "current".



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

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

2018-03-29 Thread Attila Sasvari

Thanks Andras for driving the release!

+1

Here is what I did:
- Verified signature, hash
- Created Oozie 5.0.0 distro using hadoop-2.6
- On a pseudo Hadoop 2.6.0, I executed  SparkFileCopy (both in
yarn-cluster, yarn-client mode),  custom-main-wf, datelist-java-main-wf,
demo-wf, distcp-wf, hadoop-el-wf, java-main-wf, map-reduce-wf, no-op-wf,
pig-wf, shell-wf, sqoop-freeform-wf, sqoop-wf, ssh-wf, streaming-wf,
subwf-wf  - all the workflows have succeeded
- Verified Web UI: version, getting logs and Job DAG


On Wed, Mar 28, 2018 at 4:30 PM, Artem Ervits  wrote:
>
> additionally, I've ran the mvn verify and after some time it failed due to
> timeout, still OK in my opinion.
>
> INFO] Results:
> [INFO]
> [INFO] Tests run: 738, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main 5.0.0  SUCCESS [
> 3.859 s]
> [INFO] Apache Oozie Client  SUCCESS [
> 34.826 s]
> [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [
> 25.740 s]
> [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [
> 11.842 s]
> [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [
> 7.465 s]
> [INFO] Apache Oozie Core .. FAILURE [
> 01:30 h]
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests 5.0.0  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 01:32 h
> [INFO] Finished at: 2018-03-28T14:21:30Z
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test)
> on project oozie-core: There was a timeout or other error in the fork ->
> [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/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :oozie-core
>
> On Wed, Mar 28, 2018 at 8:50 AM, Artem Ervits 
wrote:
>
> > +1 non-binding
> >
> > signatures and checksum: OK
> > build with Hadoop 2.7.5: OK
> > install on a single-node pseudo-distributed cluster: OK
> > ran no-op workflow: OK
> >
> > the directions to install sharelib on 5.0 are unclear and I'm not able
to
> > execute other workflows due to share lib problems. (not a blocker in my
> > opinion).
> >
> > Thank you
> >
> > On Tue, Mar 27, 2018 at 8:39 AM, Andras Piros  wrote:
> >
> >> Hi there,
> >>
> >> I have created a build for Oozie 5.0.0, release candidate 0.
> >>
> >> This release introduces major changes:
> >> - moved launcher from MapReduce AM to YARN AM,
> >> - switched from Tomcat to embedded Jetty,
> >> - updated third party libraries,
> >> - completely rewritten workflow graph generator,
> >> - JDK 8 support,
> >> - deprecated Instrumentation in favor of Metrics,
> >> - added indexes to speed up DB queries,
> >> - fixed CVE-2017-15712
> >>
> >> Keys to verify the signature of the release artifact are available at
> >>
> >>  http://www.apache.org/dist/oozie/KEYS
> >>
> >> Please download, test, and try it out:
> >>
> >> http://people.apache.org/~andras/oozie-5.0.0-rc0/
> >>
> >> The release candidate, sha512 signature, gpg signature, and rat report
can
> >> all be found
> >> at the above address.
> >>
> >> The vote is open until Saturday, March 31, 2018 at 12:00am PDT.
> >>
> >> Thanks,
> >>

[jira] [Commented] (OOZIE-3203) Oozie web console - links to job

2018-03-29 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-3203:
---

Thanks for filing this jira!
This is an interesting change, I'll have to take a deep dive into the git logs 
to figure out what happened.

> Oozie web console - links to job
> 
>
> Key: OOZIE-3203
> URL: https://issues.apache.org/jira/browse/OOZIE-3203
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Łukasz
>Priority: Minor
> Attachments: Selection_002.png
>
>
> In oozie web console there is a option to go to yarn job that is associated 
> with current oozie action (see image).
> I have the situation that luncher starts new job:
> _Submitting Oozie action Map-Reduce job_
> _===_ 
> _<<< Invocation of Main class completed_ 
> _<<< Oozie Launcher, propagating new Hadoop job id to Oozie_ 
> _=== job_1522069947629_0148 ===_ 
> _Oozie Launcher, uploading action data to HDFS sequence file: 
> hdfs://n1/user/hadoop/oozie-hado/055-180326153118810-oozie-hado-W/createPhraseIndex--map-reduce/action-data.seq_
>  
> _Successfully reset security manager from 
> org.apache.oozie.action.hadoop.LauncherSecurityManager@5d5e780d to null_ 
> _Oozie Launcher ends_
> Launcher started new job and new id was propagated to Oozie, but after this 
> link in web console is not updated i.e. link from web console still directs 
> to luncher action, not the actual job.
> In version 3.3, I was using previously, links in web console where updated 
> after Launcher finished.
> Can this behavior be restored, because right now it it necessary  to manually 
> look for job in yarn console to control logs and counter of the action.
> Thank you in advance.
>  



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

[jira] [Assigned] (OOZIE-3204) Oozie cannot run HBase code in Java action

2018-03-29 Thread Peter Cseh (JIRA)


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

Peter Cseh reassigned OOZIE-3204:
-

Assignee: Peter Cseh  (was: Satish Subhashrao Saley)

> Oozie cannot run HBase code in Java action 
> ---
>
> Key: OOZIE-3204
> URL: https://issues.apache.org/jira/browse/OOZIE-3204
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.1
>Reporter: Denes Bodo
>Assignee: Peter Cseh
>Priority: Critical
>
> After having custom raw file system implementation, HBase (java) action 
> cannot run:
> {noformat}
> 018-03-28 06:55:46,372  WARN HbaseCredentials:523 - 
> SERVER[ctr-e138-1518143905142-137559-01-03.hwx.site] USER[hrt_qa] 
> GROUP[-] TOKEN[] APP[tpch_query1] JOB[002-180328065157516-oozie-oozi-W] 
> ACTION[002-180328065157516-oozie-oozi-W@tpch_query1] Exception in 
> receiving hbase credentials
> java.io.IOException: java.lang.reflect.InvocationTargetException
>   at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:240)
>   at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
>   at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
>   at 
> org.apache.hadoop.hbase.security.token.TokenUtil.obtainToken(TokenUtil.java:68)
>   at 
> org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:86)
>   at 
> org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:84)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1869)
>   at 
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:313)
>   at 
> org.apache.oozie.action.hadoop.HbaseCredentials.obtainToken(HbaseCredentials.java:83)
>   at 
> org.apache.oozie.action.hadoop.HbaseCredentials.addtoJobConf(HbaseCredentials.java:56)
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1338)
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1178)
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1424)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:287)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
>   ... 24 more
> Caused by: java.lang.ExceptionInInitializerError
>   at org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
>   at 
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
>   at 
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
>   at 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:903)
>   at 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
>   ... 29 more
> Caused by: java.lang.UnsupportedOperationException: Accessing local file 
> system is not allowed
>   at 
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
>   at 
> org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
>   at 
>

[jira] [Created] (OOZIE-3205) Add better support for Hadoop: Distributed Cache Deploy

2018-03-29 Thread Peter Cseh (JIRA)

Peter Cseh created OOZIE-3205:
-

 Summary: Add better support for Hadoop: Distributed Cache Deploy
 Key: OOZIE-3205
 URL: https://issues.apache.org/jira/browse/OOZIE-3205
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Cseh


Hadoop provides [Distributed Cache 
Deploy|https://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/DistributedCacheDeploy.html]
 functionality to distribute MR libraries across the cluster. We should take 
it's settings into account so we include the correct jars in the classpath.



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

[jira] [Commented] (OOZIE-3196) Authorization: restrict world readability by user

2018-03-29 Thread Peter Orova (JIRA)


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

Peter Orova commented on OOZIE-3196:


+1 for the internal implementation [~dbist13]. Let's focus first on the 
implementations necessary within Oozie, having in mind the possible integration 
patterns with external tools. 
As to the granularity, the best would be to secure the whole REST Api and  the 
different use cases will have to be mapped to that. 
e.g. do we want to grant access to an "ordinary" user on oozie server configs? 
on server state? on the workflow list?

> Authorization: restrict world readability by user
> -
>
> Key: OOZIE-3196
> URL: https://issues.apache.org/jira/browse/OOZIE-3196
> Project: Oozie
>  Issue Type: New Feature
>  Components: bundle, coordinator, workflow
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Peter Orova
>Priority: Major
>
> The [*current authorization 
> model*|https://issues.apache.org/jira/browse/OOZIE-228] does not fit the 
> enterprise requirements as everything is readable and writable by everyone by 
> default.
> Write access can be restricted using authorization but restricting read 
> rights is only possible via Yarn ACLs and HDFS rights which still does not 
> prevent accessing the workflow, coordinator or bundle job’s configurations 
> for everyone.
> Improve authorization so it’s possible to configure read/write access for 
> workflows, coordinators, and bundles in a more granular way. Could involve 
> Sentry during implementation or create and design a new system that fits the 
> needs.



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

[jira] [Updated] (OOZIE-3204) Oozie cannot run HBase code in Java action

2018-03-29 Thread Denes Bodo (JIRA)


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

Denes Bodo updated OOZIE-3204:
--
Description: 
After having custom raw file system implementation, HBase (java) action cannot 
run:
{noformat}
018-03-28 06:55:46,372  WARN HbaseCredentials:523 - 
SERVER[ctr-e138-1518143905142-137559-01-03.hwx.site] USER[hrt_qa] GROUP[-] 
TOKEN[] APP[tpch_query1] JOB[002-180328065157516-oozie-oozi-W] 
ACTION[002-180328065157516-oozie-oozi-W@tpch_query1] Exception in receiving 
hbase credentials
java.io.IOException: java.lang.reflect.InvocationTargetException
at 
org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:240)
at 
org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
at 
org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
at 
org.apache.hadoop.hbase.security.token.TokenUtil.obtainToken(TokenUtil.java:68)
at 
org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:86)
at 
org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:84)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1869)
at 
org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:313)
at 
org.apache.oozie.action.hadoop.HbaseCredentials.obtainToken(HbaseCredentials.java:83)
at 
org.apache.oozie.action.hadoop.HbaseCredentials.addtoJobConf(HbaseCredentials.java:56)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1338)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1178)
at 
org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1424)
at 
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
at 
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
at org.apache.oozie.command.XCommand.call(XCommand.java:287)
at 
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
at 
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at 
org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
... 24 more
Caused by: java.lang.ExceptionInInitializerError
at org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
at 
org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
at 
org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
at 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:903)
at 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
... 29 more
Caused by: java.lang.UnsupportedOperationException: Accessing local file system 
is not allowed
at 
org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
at 
org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2796)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
at 
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2830)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2812)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:179)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:374)
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:295)

[jira] [Assigned] (OOZIE-3204) Oozie cannot run HBase code in Java action

2018-03-29 Thread Denes Bodo (JIRA)


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

Denes Bodo reassigned OOZIE-3204:
-

Assignee: Satish Subhashrao Saley

> Oozie cannot run HBase code in Java action 
> ---
>
> Key: OOZIE-3204
> URL: https://issues.apache.org/jira/browse/OOZIE-3204
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.1
>Reporter: Denes Bodo
>Assignee: Satish Subhashrao Saley
>Priority: Critical
>
> After having custom raw file system implementation, HBase action cannot run:
> {noformat}
> 018-03-28 06:55:46,372  WARN HbaseCredentials:523 - 
> SERVER[ctr-e138-1518143905142-137559-01-03.hwx.site] USER[hrt_qa] 
> GROUP[-] TOKEN[] APP[tpch_query1] JOB[002-180328065157516-oozie-oozi-W] 
> ACTION[002-180328065157516-oozie-oozi-W@tpch_query1] Exception in 
> receiving hbase credentials
> java.io.IOException: java.lang.reflect.InvocationTargetException
>   at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:240)
>   at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
>   at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
>   at 
> org.apache.hadoop.hbase.security.token.TokenUtil.obtainToken(TokenUtil.java:68)
>   at 
> org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:86)
>   at 
> org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:84)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1869)
>   at 
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:313)
>   at 
> org.apache.oozie.action.hadoop.HbaseCredentials.obtainToken(HbaseCredentials.java:83)
>   at 
> org.apache.oozie.action.hadoop.HbaseCredentials.addtoJobConf(HbaseCredentials.java:56)
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1338)
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1178)
>   at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1424)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
>   at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:287)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
>   at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
>   ... 24 more
> Caused by: java.lang.ExceptionInInitializerError
>   at org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
>   at 
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
>   at 
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
>   at 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:903)
>   at 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
>   ... 29 more
> Caused by: java.lang.UnsupportedOperationException: Accessing local file 
> system is not allowed
>   at 
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
>   at 
> org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
>   at 
>

[jira] [Updated] (OOZIE-2947) Support job-xml or global configs for credentials provider

2018-03-29 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2947:

Description: Today, one needs to specify their HBase properties in their 
credentials section by 
[hand|https://github.com/apache/oozie/blob/99a3df568d182e75751126aac5fe8b63d876e64f/client/src/main/resources/oozie-workflow-0.5.xsd#L321-L341]
 (or EL Expression) if acquiring an HBase credential for example. This is 
despite having the same settings in {{hbase-site.xml}} e.g. for a Java action. 
It would be nice if the same configurations the actions used for HBase could be 
used by the credentials provider.

> Support job-xml or global configs for credentials provider
> --
>
> Key: OOZIE-2947
> URL: https://issues.apache.org/jira/browse/OOZIE-2947
> Project: Oozie
>  Issue Type: New Feature
>  Components: security
>Affects Versions: 4.2.0
>Reporter: Clay B.
>Priority: Minor
>
> Today, one needs to specify their HBase properties in their credentials 
> section by 
> [hand|https://github.com/apache/oozie/blob/99a3df568d182e75751126aac5fe8b63d876e64f/client/src/main/resources/oozie-workflow-0.5.xsd#L321-L341]
>  (or EL Expression) if acquiring an HBase credential for example. This is 
> despite having the same settings in {{hbase-site.xml}} e.g. for a Java 
> action. It would be nice if the same configurations the actions used for 
> HBase could be used by the credentials provider.



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

[jira] [Updated] (OOZIE-2947) Support job-xml or global configs for credentials provider

2018-03-29 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2947:

Environment: (was: Today, one needs to specify their HBase properties 
in their credentials section by 
[hand|https://github.com/apache/oozie/blob/99a3df568d182e75751126aac5fe8b63d876e64f/client/src/main/resources/oozie-workflow-0.5.xsd#L321-L341]
 (or EL Expression) if acquiring an HBase credential for example. This is 
despite having the same settings in `hbase-site.xml` e.g. for a Java action. It 
would be nice if the same configurations the actions used for HBase could be 
used by the credentials provider.)

> Support job-xml or global configs for credentials provider
> --
>
> Key: OOZIE-2947
> URL: https://issues.apache.org/jira/browse/OOZIE-2947
> Project: Oozie
>  Issue Type: New Feature
>  Components: security
>Affects Versions: 4.2.0
>Reporter: Clay B.
>Priority: Minor
>




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

[jira] [Updated] (OOZIE-2947) Support job-xml or global configs for credentials provider

2018-03-29 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2947:

Environment: Today, one needs to specify their HBase properties in their 
credentials section by 
[hand|https://github.com/apache/oozie/blob/99a3df568d182e75751126aac5fe8b63d876e64f/client/src/main/resources/oozie-workflow-0.5.xsd#L321-L341]
 (or EL Expression) if acquiring an HBase credential for example. This is 
despite having the same settings in `hbase-site.xml` e.g. for a Java action. It 
would be nice if the same configurations the actions used for HBase could be 
used by the credentials provider.  (was: Today, one needs to specify their 
HBase properties in their credentials section by 
[hand|https://github.com/apache/oozie/blob/99a3df568d182e75751126aac5fe8b63d876e64f/client/src/main/resources/oozie-workflow-0.5.xsd#L321-L341[
 (or EL Expression) if acquiring an HBase credential for example. This is 
despite having the same settings in `hbase-site.xml` e.g. for a Java action. It 
would be nice if the same configurations the actions used for HBase could be 
used by the credentials provider.)

> Support job-xml or global configs for credentials provider
> --
>
> Key: OOZIE-2947
> URL: https://issues.apache.org/jira/browse/OOZIE-2947
> Project: Oozie
>  Issue Type: New Feature
>  Components: security
>Affects Versions: 4.2.0
> Environment: Today, one needs to specify their HBase properties in 
> their credentials section by 
> [hand|https://github.com/apache/oozie/blob/99a3df568d182e75751126aac5fe8b63d876e64f/client/src/main/resources/oozie-workflow-0.5.xsd#L321-L341]
>  (or EL Expression) if acquiring an HBase credential for example. This is 
> despite having the same settings in `hbase-site.xml` e.g. for a Java action. 
> It would be nice if the same configurations the actions used for HBase could 
> be used by the credentials provider.
>Reporter: Clay B.
>Priority: Minor
>




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

[jira] Subscription: Oozie Patch Available

2018-03-29 Thread jira

Issue Subscription
Filter: Oozie Patch Available (105 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
OOZIE-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3193  Applications are not killed when submitted via subworkflow
https://issues.apache.org/jira/browse/OOZIE-3193
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
OOZIE-3185  Conflicting JARs org.apache.derby exist in Oozie
https://issues.apache.org/jira/browse/OOZIE-3185
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3134  Potential inconsistency between the in-memory SLA map and the Oozie 
database
https://issues.apache.org/jira/browse/OOZIE-3134
OOZIE-3109  Escape log-streaming's HTML-specific characters
https://issues.apache.org/jira/browse/OOZIE-3109
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues.apache.org/jira/browse/OOZIE-3105
OOZIE-3094  fix for grammar mistake
https://issues.apache.org/jira/browse/OOZIE-3094
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-3061  Kill only those child jobs which are not already killed
https://issues.apache.org/jira/browse/OOZIE-3061
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

[jira] [Updated] (OOZIE-3208) "It should never happen" error code when running an action when Sharelib doesn't exist

[jira] [Created] (OOZIE-3208) "It should never happen" error code when running an action when Sharelib doesn't exist

[jira] [Created] (OOZIE-3207) Update ASF root pom version

[jira] [Created] (OOZIE-3206) The README.txt file refers to the 4.3.0 Quickstart docs

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

[jira] [Commented] (OOZIE-3203) Oozie web console - links to job

[jira] [Assigned] (OOZIE-3204) Oozie cannot run HBase code in Java action

[jira] [Created] (OOZIE-3205) Add better support for Hadoop: Distributed Cache Deploy

[jira] [Commented] (OOZIE-3196) Authorization: restrict world readability by user

[jira] [Updated] (OOZIE-3204) Oozie cannot run HBase code in Java action

[jira] [Assigned] (OOZIE-3204) Oozie cannot run HBase code in Java action

[jira] [Updated] (OOZIE-2947) Support job-xml or global configs for credentials provider

[jira] [Updated] (OOZIE-2947) Support job-xml or global configs for credentials provider

[jira] [Updated] (OOZIE-2947) Support job-xml or global configs for credentials provider

[jira] Subscription: Oozie Patch Available

16 matches

Site Navigation

Mail list logo

Footer information