[jira] [Updated] (OOZIE-3242) Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3242:

Fix Version/s: (was: trunk)
   5.1.0

> Flaky test TestXCommand#testXCommandLifecycleLockingFailingToLock
> -
>
> Key: OOZIE-3242
> URL: https://issues.apache.org/jira/browse/OOZIE-3242
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3242-001.patch
>
>
> The test case TestXCommand#testXCommandLifecycleLockingFailingToLock 
> occasionally fails with the following error:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.command.TestXCommand.testXCommandLifecycleLockingFailingToLock(TestXCommand.java:186)
> {noformat}



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

[jira] [Updated] (OOZIE-3192) OozieDBCLI does not clean up temporary files

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3192:

Fix Version/s: (was: trunk)
   5.1.0

> OozieDBCLI does not clean up temporary files
> 
>
> Key: OOZIE-3192
> URL: https://issues.apache.org/jira/browse/OOZIE-3192
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Prabhu Joseph
>Assignee: Prabhu Joseph
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3192.1.patch, OOZIE-3192.2.patch
>
>
> Oozie runtime directories are getting accumulated under /tmp. OozieDBCLI does 
> not destroy the Services and so the code to delete runtime directories are 
> skipped.
>  
> {code:java}
> [root@bigdata2 libtools]# ls  /tmp/oozie-oozi*
> /tmp/oozie-oozi1000989288737845910.dir:
> /tmp/oozie-oozi1036845504637967814.dir:
> /tmp/oozie-oozi2051016416521814301.dir:
> /tmp/oozie-oozi3194893167383531504.dir:
> /tmp/oozie-oozi3750814910369499964.dir:
> /tmp/oozie-oozi3988391799981903880.dir:
> /tmp/oozie-oozi4308477407910112054.dir:
> /tmp/oozie-oozi4717881377452217148.dir:
> /tmp/oozie-oozi5894080803700698940.dir:
> /tmp/oozie-oozi6367849996578983710.dir:
> /tmp/oozie-oozi682733264186033679.dir:
> /tmp/oozie-oozi7006370502487976692.dir:
> {code}



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

[jira] [Updated] (OOZIE-3313) Hive example action fails

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3313:

Fix Version/s: (was: trunk)
   5.1.0

> Hive example action fails
> -
>
> Key: OOZIE-3313
> URL: https://issues.apache.org/jira/browse/OOZIE-3313
> Project: Oozie
>  Issue Type: Bug
>  Components: action, workflow
>Affects Versions: trunk, 5.0.0, 5.1.0
>Reporter: Daniel Becker
>Assignee: Daniel Becker
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: OOZIE-3313.patch
>
>
> The patch for OOZIE-2619 introduced the following property in 
> core/src/main/conf/action-conf/hive.xml:
> {code:java}
> 
> mapreduce.input.fileinputformat.split.maxsize
> 25600L
> {code}
> This makes the hive example fail because the value "25600L" cannot be 
> parsed as a Long because of the final 'L' (as a literal in the source code, 
> the L suffix is ok but not when trying to parse it from a string). The action 
> fails with the following stack trace:
> {noformat}
> java.lang.NumberFormatException: For input string: "25600L"
>   at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
>   at java.lang.Long.parseLong(Long.java:589)
>   at java.lang.Long.parseLong(Long.java:631)
>   at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:1267)
>   at 
> org.apache.hadoop.hive.shims.HadoopShimsSecure$CombineFileInputFormatShim.getSplits(HadoopShimsSecure.java:305)
>   at 
> org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.getCombineSplits(CombineHiveInputFormat.java:470)
>   at 
> org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.getSplits(CombineHiveInputFormat.java:571)
>   at 
> org.apache.hadoop.mapreduce.JobSubmitter.writeOldSplits(JobSubmitter.java:329)
>   at 
> org.apache.hadoop.mapreduce.JobSubmitter.writeSplits(JobSubmitter.java:321)
>   at 
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:197)
>   at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1297)
>   at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1294)
>   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:1692)
>   at org.apache.hadoop.mapreduce.Job.submit(Job.java:1294)
>   at org.apache.hadoop.mapred.JobClient$1.run(JobClient.java:562)
>   at org.apache.hadoop.mapred.JobClient$1.run(JobClient.java:557)
>   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:1692)
>   at 
> org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:557)
>   at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:548)
>   at 
> org.apache.hadoop.hive.ql.exec.mr.ExecDriver.execute(ExecDriver.java:431)
>   at 
> org.apache.hadoop.hive.ql.exec.mr.MapRedTask.execute(MapRedTask.java:137)
>   at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
>   at 
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:88)
>   at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1650)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1409)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1192)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1059)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1049)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:213)
>   at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:165)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:376)
>   at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:311)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:409)
>   at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:425)
>   at 
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:714)
>   at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
>   at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:621)
>   at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:310)
>   at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:294)
>   at 
> org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:101)
>   at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
>

[jira] [Updated] (OOZIE-3240) Flaky test TestJMSAccessorService#testConnectionRetry

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3240:

Fix Version/s: (was: trunk)
   5.1.0

> Flaky test TestJMSAccessorService#testConnectionRetry
> -
>
> Key: OOZIE-3240
> URL: https://issues.apache.org/jira/browse/OOZIE-3240
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3240-002.patch, OOZIE-3240.txt
>
>
> The test TestJMSAccessorService#testConnectionRetry failed with the following 
> errors in the log:
> {noformat}
> junit.framework.AssertionFailedError
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:183)
> {noformat}
> {noformat}
> [jndiProperties=java.naming.factory.initial#org.apache.activemq.jndi.ActiveMQInitialContextFactory;java.naming.provider.url#tcp://localhost:39362;connectionFactoryNames#ConnectionFactory]]
> javax.jms.JMSException: Could not connect to broker URL: 
> tcp://localhost:39362. Reason: java.net.ConnectException: Connection refused 
> (Connection refused)
>   at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:373)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:303)
>   at 
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:243)
>   at 
> org.apache.oozie.jms.DefaultConnectionContext.createConnection(DefaultConnectionContext.java:53)
>   at 
> org.apache.oozie.service.JMSAccessorService.createConnectionContext(JMSAccessorService.java:264)
>   at 
> org.apache.oozie.service.JMSAccessorService.registerForNotification(JMSAccessorService.java:110)
>   at 
> org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:173)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at org.junit.runners.Suite.runChild(Suite.java:127)
>   at org.junit.runners.Suite.runChild(Suite.java:26)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
>   at 
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
>   at 
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at 
> org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilder$PC$1.run(ParallelComputerBuilder.java:593)
>   at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
>   at 
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
>   at 
>

[jira] [Updated] (OOZIE-3222) The description for DAG is not accurate in the documentation

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3222:

Fix Version/s: (was: trunk)
   5.1.0

> The description for DAG is not accurate in the documentation
> 
>
> Key: OOZIE-3222
> URL: https://issues.apache.org/jira/browse/OOZIE-3222
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 5.0.0, 4.3.1
>Reporter: gongchuanjie
>Assignee: gongchuanjie
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: OOZIE-3222.001.patch
>
>
> the description for DAG is not accurate,it should be Directed Acyclic Graph.



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

[jira] [Updated] (OOZIE-3270) Upgrade Derby to 10.14.1.0

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3270:

Fix Version/s: (was: trunk)
   5.1.0

>  Upgrade Derby to 10.14.1.0
> ---
>
> Key: OOZIE-3270
> URL: https://issues.apache.org/jira/browse/OOZIE-3270
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3270.01.patch, OOZIE-3270.02.patch, 
> OOZIE-3270.03.patch, OOZIE-3270.04.patch, OOZIE-3270.05.patch
>
>
> We should upgrade  Derby to 10.14.1.0



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

[jira] [Updated] (OOZIE-3303) Oozie UI does not work after Jetty 9.3 upgrade

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3303:

Fix Version/s: (was: trunk)
   5.1.0

> Oozie UI does not work after Jetty 9.3 upgrade
> --
>
> Key: OOZIE-3303
> URL: https://issues.apache.org/jira/browse/OOZIE-3303
> Project: Oozie
>  Issue Type: Bug
>  Components: build, ui
>Affects Versions: 5.1.0
> Environment: Mac OS X
> Java 8 u171
> Hadoop 2.6.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3303-1.patch, OOZIE-3303-2.patch
>
>
> When latest {{master}} Oozie is built locally with Hadoop version 2.6.0, and 
> {{bin/oozied.sh start}} is issued, reaching the UI or accessing CLI results 
> in following error message:
> {noformat}
> {"errorMessage":"org.apache.jasper.JasperException: Unable to compile class 
> for JSP","httpStatusCode":500}
> {noformat}
> Server side error message in {{logs/jetty.log}} is:
> {noformat}
> 2018-07-11 14:57:18,956  INFO Server:414 - Started @6514ms
> 2018-07-11 14:57:46,110  WARN ServletHandler:624 - 
> org.apache.jasper.JasperException: Unable to compile class for JSP
> at 
> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:116)
> ...
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
> ...
> at java.lang.Thread.run(Thread.java:748)
> Caused by: Unable to find a javac compiler;
> com.sun.tools.javac.Main is not on the classpath.
> Perhaps JAVA_HOME does not point to the JDK.
> It is currently set to 
> "/Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre"
> at 
> org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.getCompiler(CompilerAdapterFactory.java:129)
> ...
> at 
> org.apache.jasper.compiler.AntCompiler.generateClass(AntCompiler.java:233)
> ... 60 more
> {noformat}
> From CLI, following is the error message:
> {noformat}
> $ bin/oozie admin -oozie http://localhost:11000 -status
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server. 
> No of retries = 1. Exception = Could not authenticate, Authentication failed, 
> status: 404, message: Not Found
> {noformat}
> Oozie 5.0.0 UI and CLI both work in the same environment.



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

[jira] [Updated] (OOZIE-3334) Don't use org.apache.hadoop.hbase.security.User in HDFSCredentials

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3334:

Fix Version/s: (was: trunk)
   5.1.0

> Don't use org.apache.hadoop.hbase.security.User in HDFSCredentials
> --
>
> Key: OOZIE-3334
> URL: https://issues.apache.org/jira/browse/OOZIE-3334
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0b1
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3334.01.patch, OOZIE-3334.02.patch
>
>
> HDFSCredentials is using org.apache.hadoop.hbase.security.User to obtain 
> delegation tokens.
> It introduces a runtime dependency on HBase which is not required in Oozie 
> core.
> It was reported on GitHub:
> https://github.com/apache/oozie/commit/c29d9c5fce27f5f5335662ce2649387258f1c7fd#commitcomment-30224511



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

[jira] [Updated] (OOZIE-3246) Flaky test TestJMSJobEventListener#testConnectionDrop

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3246:

Fix Version/s: (was: trunk)
   5.1.0

> Flaky test TestJMSJobEventListener#testConnectionDrop
> -
>
> Key: OOZIE-3246
> URL: https://issues.apache.org/jira/browse/OOZIE-3246
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3246-001.patch
>
>
> The testcase TestJMSJobEventListener#testConnectionDrop occasionally fails 
> with the following error:
> {noformat}
> junit.framework.AssertionFailedError: 
> org.apache.activemq:type=Broker,brokerName=localhost
>   at 
> org.apache.oozie.jms.TestJMSJobEventListener.testConnectionDrop(TestJMSJobEventListener.java:365)
> {noformat}



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

[jira] [Updated] (OOZIE-3226) [tools] TestOozieDBCLI#testOozieDBCLI() fails

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3226:

Fix Version/s: (was: trunk)
   5.1.0

> [tools] TestOozieDBCLI#testOozieDBCLI() fails
> -
>
> Key: OOZIE-3226
> URL: https://issues.apache.org/jira/browse/OOZIE-3226
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tools
> Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 
> 2018 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3226-001.patch, OOZIE-3226-002.patch
>
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the 
> test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 
> 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>     at 
> org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



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

[jira] [Updated] (OOZIE-3168) Remove -secure option from DG_QuickStart.twiki and from oozie-setup.sh

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3168:

Fix Version/s: (was: trunk)
   5.0.0

> Remove -secure option from DG_QuickStart.twiki and from oozie-setup.sh 
> ---
>
> Key: OOZIE-3168
> URL: https://issues.apache.org/jira/browse/OOZIE-3168
> Project: Oozie
>  Issue Type: Bug
>  Components: docs, scripts
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3168-001.patch, OOZIE-3168-002.patch
>
>
> The DG_QuickStart.twiki still contains reference to the -secure option from 
> DG_QuickStart.twiki: 
> [https://github.com/apache/oozie/blob/master/docs/src/site/twiki/DG_QuickStart.twiki#L149-L150]
> This is a valid option in the oozie-setup.sh, but is not used anymore.
> oozie-setup.ps1 also contains reference to -prepare-war and -secure options:
> [https://github.com/apache/oozie/blob/master/distro/src/main/bin/oozie-setup.ps1#L26]
>  
>  



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

[jira] [Updated] (OOZIE-3149) Delete work.log

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3149:

Fix Version/s: (was: trunk)
   5.0.0

> Delete work.log
> ---
>
> Key: OOZIE-3149
> URL: https://issues.apache.org/jira/browse/OOZIE-3149
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
>Priority: Trivial
>  Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-3149-01.patch
>
>
> The root dir has a file named {{work.log}} which appears to be an old version 
> of {{release-log.txt}}, up to Oozie 3.0.1.  It should be safe to simply 
> delete it.



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

[jira] [Updated] (OOZIE-3162) Precommit build fails to add comment to JIRA

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3162:

Fix Version/s: (was: trunk)
   5.0.0

> Precommit build fails to add comment to JIRA
> 
>
> Key: OOZIE-3162
> URL: https://issues.apache.org/jira/browse/OOZIE-3162
> Project: Oozie
>  Issue Type: Bug
>  Components: build
> Environment: Oozie precommit build, 
> [https://builds.apache.org/job/PreCommit-OOZIE-Build/321/,] failed to add 
> comment to JIRA 
> Reason: 
> Adding comment to JIRA 
> Unable to log in to server: 
> [https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2] with user: 
> hadoopqa. 
> It is related to the JIRA major update on 1/14. As per INFRA-15843:
> "The SOAP RPC methods have been deprecated since 2013 and were completely 
> removed in Jira 7. You'll have to make use of the REST API instead"
> We need to update the Oozie precommit job  because it currently relies on 
> jira-cli-2.6.0. If we upgrade to atlassian-cli-7.5.0 and use jira.sh, it 
> shall work.
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3162-000.patch, OOZIE-3162-001.patch, 
> OOZIE-3162-002.patch, OOZIE-3162-003.patch, OOZIE-3162-004.patch, 
> amend-OOZIE-3162-001.patch
>
>




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

[jira] [Updated] (OOZIE-2847) Oozie Ha timing issue

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-2847:

Fix Version/s: (was: trunk)

> Oozie Ha timing issue
> -
>
> Key: OOZIE-2847
> URL: https://issues.apache.org/jira/browse/OOZIE-2847
> Project: Oozie
>  Issue Type: Bug
>  Components: HA
>Affects Versions: 4.3.0, 5.0.0b1, 5.0.0
>Reporter: Péter Gergő Barna
>Assignee: Denes Bodo
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-2847-4.3.patch, OOZIE-2847-5.0.patch, 
> OOZIE-2847.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Oozie Ha timing issue
> When Oozie is launching the mapper, it is writing a job id into a file on 
> hdfs. Let's assume the ApplicationMaster is killed, and Oozie will make a 
> second try, during recovery. On the second try, Oozie is trying to see if the 
> previously written job id on hdfs matches the current job id. In most 
> occasion, this will match. However, in the event when Oozie launcher is 
> killed right in the middle when Oozie is in the process of writing id in the 
> file, the Oozie file in hdfs is created, but the id has yet to be written to 
> the file. During the next recovery, Oozie will mistakenly think the id exists 
> in the file while the file is actually empty, therefore throwing this 
> exception: 
> {noformat}
> 2015-07-10 
> 05:56:58,137|beaver.machine|INFO|5208|1344|MainThread|
> 2015-07-10 05:56:58,137|beaver.machine|INFO|5208|1344|MainThread|Console URL  
>  : http://dal-ha21:8088/proxy/application_1436507526035_0001/
> 2015-07-10 05:56:58,138|beaver.machine|INFO|5208|1344|MainThread|Error Code   
>  : JA018
> 2015-07-10 05:56:58,138|beaver.machine|INFO|5208|1344|MainThread|Error 
> Message : Hadoop job Id mismatch, action file 
> [hdfs://hdp2-ha2/user/hadoopqa/oozie-hado/003-150710041341636-oozie-hado-W/pig-node--pig/003-150710041341636-oozie-hado-W@pig-node@0]
>  declares Id [null] current Id [job_1436507526035_0001]
> 2015-07-10 05:56:58,138|beaver.machine|INFO|5208|1344|MainThread|External ID  
>  : job_1436507526035_0001
> 2015-07-10 05:56:58,138|beaver.machine|INFO|5208|1344|MainThread|External 
> Status   : FAILED/KILLED
> 2015-07-10 05:56:58,138|beaver.machine|INFO|5208|1344|MainThread|Name 
>  : pig-node
> 2015-07-10 05:56:58,138|beaver.machine|INFO|5208|1344|MainThread|Retries  
>  : 0
> 2015-07-10 05:56:58,138|beaver.machine|INFO|5208|1344|MainThread|Tracker URI  
>  : dal-ha21:8032
> 2015-07-10 05:56:58,138|beaver.machine|INFO|5208|1344|MainThread|Type 
>  : pig
> 2015-07-10 05:56:58,158|beaver.machine|INFO|5208|1344|MainThread|Started  
>  : 2015-07-10 05:55:19 GMT
> 2015-07-10 05:56:58,160|beaver.machine|INFO|5208|1344|MainThread|Status   
>  : ERROR
> 2015-07-10 05:56:58,161|beaver.machine|INFO|5208|1344|MainThread|Ended
>  : 2015-07-10 05:56:42 GMT
> 2015-07-10 05:56:58,161|beaver.machine|INFO|5208|1344|MainThread|External 
> Stats: null
> 2015-07-10 05:56:58,161|beaver.machine|INFO|5208|1344|MainThread|External 
> ChildIDs : null
> 2015-07-10 
> 05:56:58,161|beaver.machine|INFO|5208|1344|MainThread|
> Exception:
> 2015-07-10 05:56:18,658 INFO [main] 
> org.apache.hadoop.mapreduce.v2.jobhistory.JobHistoryUtils: Default file 
> system [hdfs://hdp2-ha2:8020]
> 2015-07-10 05:56:18,665 INFO [main] 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Previous history file is at 
> hdfs://hdp2-ha2:8020/user/hadoopqa/.staging/job_1436507526035_0001/job_1436507526035_0001_1.jhist
> 2015-07-10 05:56:18,693 WARN [main] 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Unable to parse prior job 
> history, aborting recovery
> java.io.IOException: Incompatible event log version: null
>   at 
> org.apache.hadoop.mapreduce.jobhistory.EventReader.(EventReader.java:71)
>   at 
> org.apache.hadoop.mapreduce.jobhistory.JobHistoryParser.parse(JobHistoryParser.java:139)
>   at 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster.parsePreviousJobHistory(MRAppMaster.java:1206)
>   at 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster.processRecovery(MRAppMaster.java:1175)
>   at 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster.serviceStart(MRAppMaster.java:1039)
>   at 
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
>   at 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster$4.run(MRAppMaster.java:1519)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at

[jira] [Updated] (OOZIE-2770) Show missing dependencies for coord actions

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-2770:

Fix Version/s: (was: trunk)
   5.0.0

> Show missing dependencies for coord actions
> ---
>
> Key: OOZIE-2770
> URL: https://issues.apache.org/jira/browse/OOZIE-2770
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: DG_CommandLineTool.html, OOZIE-2770-V1.patch, 
> OOZIE-2770-V2.patch, OOZIE-2770-V4.patch, OOZIE-2770-V5.patch, 
> OOZIE-2770-V6.patch, OOZIE-2770-V7.patch, OOZIE-2770-V8.patch, UI.png, 
> amend-OOZIE-2770-V1.patch
>
>
> {code}
> $oozie job   -oozie http://localhost:11000/oozie -missingDependencies 
> 002-170106125510433-oozie-puru-C@6
> CoordAction : 6
> Blocked on   : 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/06/00/_SUCCESS
> DataSet: input-1
> Pending Dependencies : 
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/06/00/_SUCCESS
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/05/40/_SUCCESS
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/05/20/_SUCCESS
> Blocked on : input-2
> Pending Dependencies : 
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/06/00/_SUCCESS
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/05/40/_SUCCESS
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/05/20/_SUCCESS
> $ 
> {code}



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

[jira] [Updated] (OOZIE-2691) Show workflow action retry information in UI

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-2691:

Fix Version/s: (was: trunk)
   5.0.0

> Show workflow action retry information in UI
> 
>
> Key: OOZIE-2691
> URL: https://issues.apache.org/jira/browse/OOZIE-2691
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: Action Retries - webservice.png, OOZIE-2691-V1.patch, 
> OOZIE-2691-V2.patch, OOZIE-2691-V3.patch, OOZIE-2691-V5.patch, 
> OOZIE-2691-V6.patch, OOZIE-2691-V6.patch, UI.png, amend-OOZIE-2691.patch, 
> screenshot.png
>
>
> CLI
> {code}
> $ oozie job -info 000-161212175234862-oozie-puru-W@:start: -oozie 
> http://localhost:11000/oozie -retries
> ID : 000-161212175234862-oozie-puru-W@:start:
> No Retries
> ---
> $ oozie job -info 000-161212175234862-oozie-puru-W@pig-node -oozie 
> http://localhost:11000/oozie -retries
> ID : 000-161212175234862-oozie-puru-W@pig-node
> ---
> Retry  : 1
> Start Time : Tue, 13 Dec 2016 01:54:13 GMT
> End Time   : Tue, 13 Dec 2016 01:54:20 GMT
> Console URL: 
> http://localhost:50030/jobdetails.jsp?jobid=job_201612051339_2648
> ---
> Retry  : 2
> Start Time : Tue, 13 Dec 2016 01:55:20 GMT
> End Time   : Tue, 13 Dec 2016 01:55:24 GMT
> Console URL: 
> http://localhost:50030/jobdetails.jsp?jobid=job_201612051339_2649
> ---
> Retry  : 3
> Start Time : Tue, 13 Dec 2016 01:56:24 GMT
> End Time   : Tue, 13 Dec 2016 01:56:27 GMT
> Console URL: 
> http://localhost:50030/jobdetails.jsp?jobid=job_201612051339_2650
> ---
> $ 
> {code}



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

[jira] [Updated] (OOZIE-1717) Add indexes to speed up db queries

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-1717:

Fix Version/s: (was: trunk)
   5.0.0

> Add indexes to speed up db queries
> --
>
> Key: OOZIE-1717
> URL: https://issues.apache.org/jira/browse/OOZIE-1717
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Attila Sasvari
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-1717-00.patch, OOZIE-1717-002.patch, 
> OOZIE-1717-003.patch, OOZIE-1717-004.patch, OOZIE-1717-01.patch, 
> amend-OOZIE-1717-00.patch, amend-OOZIE-1717-01.patch
>
>
> User_name is one of the frequently used filter. Adding index should avoid  
> full db scan.
> Index need to be done for BUNDLE_JOBS,COORD_JOBS and WF_JOBS.



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

[jira] [Commented] (OOZIE-3355) Regex based search option for searching workflows in the WFM-View of Ambari

2018-10-04 Thread Denes Bodo (JIRA) 


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

Denes Bodo commented on OOZIE-3355:
---

As I understand Ambari's Workflow Manager uses Oozie REST API as is. I am not 
sure if this issue can be solved efficiently without Oozie's support; querying 
all the job names from Oozie means no impact on Oozie but generating heavy DB 
queries and great volume of data transmission over REST.

However, that would be a great feature in Oozie, too, if it supported some 
wildcard-like search, for example regex, or simply use the SQL's "%" and "_" 
characters. In the latter case, it would have only impact on Oozie but not on 
Ambari.

> Regex based search option for searching workflows in the WFM-View of Ambari
> ---
>
> Key: OOZIE-3355
> URL: https://issues.apache.org/jira/browse/OOZIE-3355
> Project: Oozie
>  Issue Type: New Feature
>  Components: bundle, coordinator, core, tools, ui, workflow
>Affects Versions: 4.2.0
>Reporter: Krishnadevan Purushothaman
>Priority: Critical
>
> *Challenge faced :*
> _{color:#d04437}In the WFM view of ambari, there is no Filter option 
> available to search for the Workflows. In order to search for the desired 
> workflow, one has to type the full name of workflow,coordinator,bundles else 
> it does not return anything which becomes a time-consuming job.{color}_
> *Feature description:*
> _{color:#14892c}There is a need for Regex based filter option in order to 
> search the workflows without the need of entering the complete name of the 
> workflow,coordinator,bundles rather by just typing the first three letters of 
> the work post which it should populate suggestions based on the first three 
> letters of the workflow,coordinator,bundles through which we can refine and 
> optimize the searching mechanism.{color}_



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

[jira] [Commented] (OOZIE-3355) Regex based search option for searching workflows in the WFM-View of Ambari

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros commented on OOZIE-3355:
-

[~dionusos] as you seem to be more familiar to Ambari's Workflow Manager than I 
am, can you please point to some of the code Ambari integrates w/ Oozie given 
Oozie REST services?

I'm thinking of supporting for some of the filter field names a couple of SQL 
compatible wildcards, like the ones provided for [SLA REST 
endpoint|https://github.com/apache/oozie/blob/master/docs/src/site/markdown/DG_SLAMonitoring.md]
 via OOZIE-3229.

> Regex based search option for searching workflows in the WFM-View of Ambari
> ---
>
> Key: OOZIE-3355
> URL: https://issues.apache.org/jira/browse/OOZIE-3355
> Project: Oozie
>  Issue Type: New Feature
>  Components: bundle, coordinator, core, tools, ui, workflow
>Affects Versions: 4.2.0
>Reporter: Krishnadevan Purushothaman
>Priority: Critical
>
> *Challenge faced :*
> _{color:#d04437}In the WFM view of ambari, there is no Filter option 
> available to search for the Workflows. In order to search for the desired 
> workflow, one has to type the full name of workflow,coordinator,bundles else 
> it does not return anything which becomes a time-consuming job.{color}_
> *Feature description:*
> _{color:#14892c}There is a need for Regex based filter option in order to 
> search the workflows without the need of entering the complete name of the 
> workflow,coordinator,bundles rather by just typing the first three letters of 
> the work post which it should populate suggestions based on the first three 
> letters of the workflow,coordinator,bundles through which we can refine and 
> optimize the searching mechanism.{color}_



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

Re: Release Oozie 5.1.0 - branching

2018-10-04 Thread Andras Piros 
Hi again,

branching is complete, branch-5.1
 has been pushed and master
 has been updated. You can
resume commits on both branches.

Thanks,

Andras

On Thu, Oct 4, 2018 at 12:30 PM Andras Piros  wrote:

> Hi there,
>
> I'm going to create branch-5.1 from master. Please hold off any commits
> targeting either one until further email.
>
> Thanks,
>
> Andras
>

Re: Oozie 5.1.0 release and plans for the year

2018-10-04 Thread Peter Cseh 
Sure, go ahead Andras. Thanks for stepping up!
Unfortunately I have too much on my plate currently to manage the release.
I'll happily be part of it's testing though!

gp

On Wed, Oct 3, 2018 at 4:17 PM Andras Piros
 wrote:

> Hi everyone,
>
> Gp, I can take over 5.1.0 release management. AFAIK we're almost a go for
> RC0.
>
> Regards,
>
> Andras
>
> On Tue, Jun 19, 2018 at 10:32 PM Artem Ervits 
> wrote:
>
> > +1 on the plans, I won't get to the jiras I'm assigned to until next
> week.
> > Don't want to be a blocker.
> >
> > On Tue, Jun 19, 2018, 4:48 AM Andras Piros  wrote:
> >
> > > Good idea Gp!
> > >
> > > Thanks for volunteering as the release manager for 5.1.0. I can see *a
> > few
> > > blockers
> > > <
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OOZIE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%205.1.0%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20%20%20priority%20DESC%2C%20updated%20DESC
> > > >*
> > > for 5.1.0 now, of which *OOZIE-3178
> > > * seems to be a real
> > > one.
> > >
> > > Regards,
> > >
> > > Andras
> > >
> > > On Tue, Jun 19, 2018 at 12:50 PM Gézapeti Cseh 
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > Now, that Oozie-2339 is in (with other fixes as well), I think it
> would
> > > be
> > > > nice to release it as part of Oozie 5.1.0 so more people will try it
> > out
> > > > before we jump in to do the coordinator/bunlde part as well.
> > > >
> > > > Also, we're planning to pick up on new action types with Andras and
> > Peter
> > > > and probably will do a bunch of new releases as they are ready later
> > this
> > > > year. The git action is the closest one, but there are others in the
> > > > pipeline like Maven and callback.
> > > >
> > > > Is anyone aware of issues in which we should wait for to start
> working
> > on
> > > > 5.1.0?
> > > > If nobody else does, I can volunteer to be the release manager for it
> > and
> > > > start the branching process in a week or so.
> > > >
> > > > thanks
> > > > gp
> > > >
> > >
> >
>


-- 
*Peter Cseh *| Software Engineer
cloudera.com 

[image: Cloudera] 

[image: Cloudera on Twitter]  [image:
Cloudera on Facebook]  [image: Cloudera
on LinkedIn] 
--

Release Oozie 5.1.0 - branching

2018-10-04 Thread Andras Piros 
Hi there,

I'm going to create branch-5.1 from master. Please hold off any commits
targeting either one until further email.

Thanks,

Andras

[jira] [Updated] (OOZIE-3358) [docs] Check and fix differences between help and command line documentation for Fluent Job API

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros updated OOZIE-3358:

Summary: [docs] Check and fix differences between help and command line 
documentation for Fluent Job API  (was: [docs] Check and fix difference between 
help and command line documentation for Fluent Job API)

> [docs] Check and fix differences between help and command line documentation 
> for Fluent Job API
> ---
>
> Key: OOZIE-3358
> URL: https://issues.apache.org/jira/browse/OOZIE-3358
> Project: Oozie
>  Issue Type: Bug
>  Components: docs, fluent-job
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3358-001.patch
>
>
> The {{job}} command lists the fluent job options as {{apijarcheck}}, 
> {{apijarsubmit}}, and {{apijarrun}} but these options has been renamed to 
> {{validatejar}}, {{submitjar}}, and {{runjar}}. The CLI help shows the 
> correct names.



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

[jira] [Commented] (OOZIE-3358) [docs] Check and fix difference between help and command line documentation for Fluent Job API

2018-10-04 Thread Andras Piros (JIRA) 


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

Andras Piros commented on OOZIE-3358:
-

Thanks for the contribution [~kmarton]! +1

> [docs] Check and fix difference between help and command line documentation 
> for Fluent Job API
> --
>
> Key: OOZIE-3358
> URL: https://issues.apache.org/jira/browse/OOZIE-3358
> Project: Oozie
>  Issue Type: Bug
>  Components: docs, fluent-job
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3358-001.patch
>
>
> The {{job}} command lists the fluent job options as {{apijarcheck}}, 
> {{apijarsubmit}}, and {{apijarrun}} but these options has been renamed to 
> {{validatejar}}, {{submitjar}}, and {{runjar}}. The CLI help shows the 
> correct names.



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

[jira] Subscription: Oozie Patch Available

2018-10-04 Thread jira 
Issue Subscription
Filter: Oozie Patch Available (91 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3358  [docs] Check and fix difference between help and command line 
documentation for Fluent Job API
https://issues.apache.org/jira/browse/OOZIE-3358
OOZIE-3338  Remove SVN references
https://issues.apache.org/jira/browse/OOZIE-3338
OOZIE-3326  Sqoop Action should support tez delegation tokens for hive-import
https://issues.apache.org/jira/browse/OOZIE-3326
OOZIE-3320  Oozie ShellAction should support absolute bash file path
https://issues.apache.org/jira/browse/OOZIE-3320
OOZIE-3319  Log SSH action callback error output
https://issues.apache.org/jira/browse/OOZIE-3319
OOZIE-3301  Update NOTICE file
https://issues.apache.org/jira/browse/OOZIE-3301
OOZIE-3277  [build] Check for star imports in patches in pre-commit
https://issues.apache.org/jira/browse/OOZIE-3277
OOZIE-3274  Remove slf4j
https://issues.apache.org/jira/browse/OOZIE-3274
OOZIE-3266  Coord action rerun support RERUN_SKIP_NODES option
https://issues.apache.org/jira/browse/OOZIE-3266
OOZIE-3265  properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to 
appear together
https://issues.apache.org/jira/browse/OOZIE-3265
OOZIE-3256  refactor OozieCLI class
https://issues.apache.org/jira/browse/OOZIE-3256
OOZIE-3249  [tools] Instrumentation log parser
https://issues.apache.org/jira/browse/OOZIE-3249
OOZIE-3218  Oozie Sqoop action with command splits the select clause into 
multiple parts due to delimiter being space
https://issues.apache.org/jira/browse/OOZIE-3218
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
OOZIE-3196  Authorization: restrict world readability by user
https://issues.apache.org/jira/browse/OOZIE-3196
OOZIE-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
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-3120  maven-assembly-plugin fails when bumped from 2.2.1
https://issues.apache.org/jira/browse/OOZIE-3120
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2714  Detect conflicting resources during class loading
https://issues.apache.org/jira/browse/OOZIE-2714
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693