[jira] [Assigned] (OOZIE-2644) Skip queuing Notification Commands when there's nothing to notify

[Azrael Seoeun (JIRA)]

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

Azrael Seoeun reassigned OOZIE-2644:


Assignee: Azrael Seoeun

> Skip queuing Notification Commands when there's nothing to notify
> -
>
> Key: OOZIE-2644
> URL: https://issues.apache.org/jira/browse/OOZIE-2644
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 3.1.3
>Reporter: Robert Kanter
>Assignee: Azrael Seoeun
> Fix For: 4.4.0
>
>
> When you use the 
> [Workflow|https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html#a5_Workflow_Notifications]
>  or 
> [Coordinator|https://oozie.apache.org/docs/4.2.0/CoordinatorFunctionalSpec.html#a15._Coordinator_Notifications]
>  Notification features, Oozie can end up queuing up a lot of 
> {{WorkflowNotificationXCommand}} and {{CoordActionNotificationXCommand}}.  
> This happens even if there's no notification configured on the job (which I 
> imagine is most of the time); in this case, the {{execute}} method simply 
> does nothing.  This is wasteful and clogs the queue up.  
> We should change the code so that it doesn't queue up one of these Commands 
> unless there's actually a URL to notify.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 44204: OOZIE:2243 - Hadoop jobs doesnot get killed when coordinator action get killed

[Rohini Palaniswamy]

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




core/src/test/java/org/apache/hadoop/examples/SleepJob.java (lines 166 - 167)


Why is this required? Isn't core-site.xml a default resource?



core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
(line 547)


Assume.assumeTrue("Skip this test for Hadoop 1.x", HadoopShims.isYARN());


- Rohini Palaniswamy


On Aug. 27, 2016, 7:46 p.m., Jaydeep Vishwakarma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/44204/
> ---
> 
> (Updated Aug. 27, 2016, 7:46 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2243
> https://issues.apache.org/jira/browse/OOZIE-2243
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Whenever the coord action or workflow gets killed only the job that has error 
> gets killed while the other hadoop jobs keeps on running and only the 
> workflow status gets changed to killed.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> e546e77 
>   core/src/main/java/org/apache/oozie/action/hadoop/LauncherMapperHelper.java 
> ed06707 
>   
> core/src/main/java/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.java
>  1ea7097 
>   core/src/test/java/org/apache/hadoop/examples/SleepJob.java 8dec534 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> 5f9e29a 
>   
> hadooplibs/hadoop-utils-1/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java
>  dca7820 
>   
> hadooplibs/hadoop-utils-2/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java
>  ce8c14f 
>   
> hadooplibs/hadoop-utils-3/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java
>  94e01ea 
> 
> Diff: https://reviews.apache.org/r/44204/diff/
> 
> 
> Testing
> ---
> 
> done
> 
> 
> Thanks,
> 
> Jaydeep Vishwakarma
> 
>

[jira] [Commented] (OOZIE-2194) oozie job -kill doesn't work with spark action

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2194:
---

bq. This is a current limitation in most actions: see OOZIE-1025.
  This is fixed in OOZIE-2243 for mapreduce jobs. But that does not work with 
Spark. 

There are two things we require from Spark
- Ability to kill the running job through API (We do this in shutdown hook 
for Mapreduce and Tez jobs in Pig and Hive)
- Support for yarn application tags (To kill any orphaned jobs during AM 
retries and RM restart and handle any that were missed when shutdown hook did 
not execute) 

> oozie job -kill doesn't work with spark action
> --
>
> Key: OOZIE-2194
> URL: https://issues.apache.org/jira/browse/OOZIE-2194
> Project: Oozie
>  Issue Type: Bug
>Reporter: Thomas Graves
>
> I was trying the spark action out with oozie and was able to launch fine. But 
> when I tried do use oozie job -kill it only killed the launcher job and not 
> the spark application itself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2678:
---

[~abhishekbafna] or [~satishsaley], can one of you pick this up. Fix is simple. 
Just need to set tez.application.tags in addition to mapreduce.job.tags in the 
action conf for Pig and Hive actions.

> Oozie job -kill doesn't work with tez jobs
> --
>
> Key: OOZIE-2678
> URL: https://issues.apache.org/jira/browse/OOZIE-2678
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
> Fix For: 4.3.0
>
>
>  OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
> as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OOZIE-2678) Oozie job -kill doesn't work with tez jobs

[Rohini Palaniswamy (JIRA)]

Rohini Palaniswamy created OOZIE-2678:
-

 Summary: Oozie job -kill doesn't work with tez jobs
 Key: OOZIE-2678
 URL: https://issues.apache.org/jira/browse/OOZIE-2678
 Project: Oozie
  Issue Type: Bug
Reporter: Rohini Palaniswamy
 Fix For: 4.3.0


 OOZIE-2243 added support for mapreduce jobs. We need to do that for Tez jobs 
as well. TEZ-909 added tez.application.tags similar to mapreduce.job.tags,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (OOZIE-2194) oozie job -kill doesn't work with spark action

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy reopened OOZIE-2194:
---

> oozie job -kill doesn't work with spark action
> --
>
> Key: OOZIE-2194
> URL: https://issues.apache.org/jira/browse/OOZIE-2194
> Project: Oozie
>  Issue Type: Bug
>Reporter: Thomas Graves
>
> I was trying the spark action out with oozie and was able to launch fine. But 
> when I tried do use oozie job -kill it only killed the launcher job and not 
> the spark application itself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OOZIE-1025) Killing oozie job kills oozie launcher job alone in hadoop.

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy resolved OOZIE-1025.
---
Resolution: Duplicate

This has been fixed as part of OOZIE-2243

> Killing oozie job kills oozie launcher job alone in hadoop.
> ---
>
> Key: OOZIE-1025
> URL: https://issues.apache.org/jira/browse/OOZIE-1025
> Project: Oozie
>  Issue Type: Bug
> Environment: Centos-5.8,Hadoop 2.0.0-cdh4.0.1
>Reporter: PriyaSundararajan
>
> As per the release  build version: 3.1.3-cdh4.0.1 killing oozie job using 
> kill command kills the oozie launcher job alone in hadoop and all other jobs 
> associated with that workflow is running till it gets complete. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2536) Shell action got stuck for 6 hours even after Exit status is 0

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-2536:
---
Priority: Blocker  (was: Major)

> Shell action got stuck for 6 hours even after Exit status is 0
> --
>
> Key: OOZIE-2536
> URL: https://issues.apache.org/jira/browse/OOZIE-2536
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Blocker
> Fix For: 4.3.0
>
>
> In out environment, we faced an issue where uberized Shell action was getting 
> stuck even though the shell action got completed with status 0. Please refer 
> the attached syslog and stdout if launcher job, here I point out partially
> stdout :
> {quote}
> >>> Invoking Shell command line now >>
> Stdoutput myshellType=qmyshellUpdate
> Exit code of the Shell command 0
> <<< Invocation of Shell command completed <<<
> <<< Invocation of Main class completed <<<
> {quote} 
> syslog
> {quote}
> 2016-05-23 11:15:52,587 WARN [uber-SubtaskRunner] 
> org.apache.hadoop.mapred.LocalContainerLauncher: Unable to delete unexpected 
> local file/dir .action.xml.crc: insufficient permissions?
> 2016-05-23 11:15:52,588 FATAL [AsyncDispatcher event handler] 
> org.apache.hadoop.conf.Configuration: error parsing conf propagation-conf.xml
> java.io.FileNotFoundException: 
> /tmp/yarn-local/usercache/saley/appcache/application_1234_123/container_e01_1234_123_01_01/propagation-conf.xml
>  (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:93)
> at 
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at 
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at java.net.URL.openStream(URL.java:1038)
> at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2468)
> at 
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2539)
> at 
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2492)
> at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2405)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:981)
> at 
> org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:1031)
> at org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1251)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.getMemoryRequired(TaskAttemptImpl.java:568)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.updateMillisCounters(TaskAttemptImpl.java:1295)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.createJobCounterUpdateEventTASucceeded(TaskAttemptImpl.java:1323)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.access$3500(TaskAttemptImpl.java:147)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl$SucceededTransition.transition(TaskAttemptImpl.java:1710)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl$SucceededTransition.transition(TaskAttemptImpl.java:1701)
> at 
> org.apache.hadoop.yarn.state.StateMachineFactory$SingleInternalArc.doTransition(StateMachineFactory.java:362)
> at 
> org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
> at 
> org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
> at 
> org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.handle(TaskAttemptImpl.java:1085)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.handle(TaskAttemptImpl.java:146)
> at 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster$TaskAttemptEventDispatcher.handle(MRAppMaster.java:1394)
> at 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster$TaskAttemptEventDispatcher.handle(MRAppMaster.java:1386)
> at 
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:184)
> at 
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:110)
> at java.lang.Thread.run(Thread.java:745)
> 2016-05-23 11:15:52,590 FATAL [AsyncDispatcher event handler] 
> org.apache.hadoop.yarn.event.AsyncDispatcher: Error in dispatcher thread
> java.lang.RuntimeException: java.io.FileNotFoundException: 
> /grid/5/tmp/yarn-local/usercache/saley/appcache/application_1234_123/container_e01_1234_123_01_01/propagation-conf.xml
>  (No such file or directory)
> 

[jira] [Updated] (OOZIE-2536) Shell action got stuck for 6 hours even after Exit status is 0

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-2536:
---
Fix Version/s: 4.3.0

> Shell action got stuck for 6 hours even after Exit status is 0
> --
>
> Key: OOZIE-2536
> URL: https://issues.apache.org/jira/browse/OOZIE-2536
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 4.3.0
>
>
> In out environment, we faced an issue where uberized Shell action was getting 
> stuck even though the shell action got completed with status 0. Please refer 
> the attached syslog and stdout if launcher job, here I point out partially
> stdout :
> {quote}
> >>> Invoking Shell command line now >>
> Stdoutput myshellType=qmyshellUpdate
> Exit code of the Shell command 0
> <<< Invocation of Shell command completed <<<
> <<< Invocation of Main class completed <<<
> {quote} 
> syslog
> {quote}
> 2016-05-23 11:15:52,587 WARN [uber-SubtaskRunner] 
> org.apache.hadoop.mapred.LocalContainerLauncher: Unable to delete unexpected 
> local file/dir .action.xml.crc: insufficient permissions?
> 2016-05-23 11:15:52,588 FATAL [AsyncDispatcher event handler] 
> org.apache.hadoop.conf.Configuration: error parsing conf propagation-conf.xml
> java.io.FileNotFoundException: 
> /tmp/yarn-local/usercache/saley/appcache/application_1234_123/container_e01_1234_123_01_01/propagation-conf.xml
>  (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:93)
> at 
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at 
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at java.net.URL.openStream(URL.java:1038)
> at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2468)
> at 
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2539)
> at 
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2492)
> at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2405)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:981)
> at 
> org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:1031)
> at org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1251)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.getMemoryRequired(TaskAttemptImpl.java:568)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.updateMillisCounters(TaskAttemptImpl.java:1295)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.createJobCounterUpdateEventTASucceeded(TaskAttemptImpl.java:1323)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.access$3500(TaskAttemptImpl.java:147)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl$SucceededTransition.transition(TaskAttemptImpl.java:1710)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl$SucceededTransition.transition(TaskAttemptImpl.java:1701)
> at 
> org.apache.hadoop.yarn.state.StateMachineFactory$SingleInternalArc.doTransition(StateMachineFactory.java:362)
> at 
> org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
> at 
> org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
> at 
> org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.handle(TaskAttemptImpl.java:1085)
> at 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.handle(TaskAttemptImpl.java:146)
> at 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster$TaskAttemptEventDispatcher.handle(MRAppMaster.java:1394)
> at 
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster$TaskAttemptEventDispatcher.handle(MRAppMaster.java:1386)
> at 
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:184)
> at 
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:110)
> at java.lang.Thread.run(Thread.java:745)
> 2016-05-23 11:15:52,590 FATAL [AsyncDispatcher event handler] 
> org.apache.hadoop.yarn.event.AsyncDispatcher: Error in dispatcher thread
> java.lang.RuntimeException: java.io.FileNotFoundException: 
> /grid/5/tmp/yarn-local/usercache/saley/appcache/application_1234_123/container_e01_1234_123_01_01/propagation-conf.xml
>  (No such file or directory)
> at 
> 

[jira] [Commented] (OOZIE-2606) Set spark.yarn.jars to fix Spark 2.0 with Oozie

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2606:
---

Some comments:
  1) Please use a separate method than fixFsDefaultUris
  2) Please use separate if blocks for pattern matching and getting the file
{code}
SPARK_YARN_JAR_PATTERN.matcher(p.getName()).find() || 
SPARK_ASSEMBLY_JAR_PATTERN.matcher(p.getName()).find()
{code}
 3) Hadoop has APIs to get version- 
org.apache.hadoop.util.VersionInfo.getVersion(). Check if spark has something 
similar and that can be used instead of looking at manifest directly
 4) Skip adding --conf spark.yarn.jars if it is version 1.x. 
 5) Currently all jars are in --files and spark.yarn.jars which will be 
confusing for user and will also generate lot of log messages saying duplicate 
jar. Will it work if you just put spark-yarn*.jar in spark.yarn.jars and rest 
in --files?

> Set spark.yarn.jars to fix Spark 2.0 with Oozie
> ---
>
> Key: OOZIE-2606
> URL: https://issues.apache.org/jira/browse/OOZIE-2606
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Jonathan Kelly
>Assignee: Satish Subhashrao Saley
>  Labels: spark, spark2.0.0
> Fix For: 4.3.0
>
> Attachments: OOZIE-2606-2.patch, OOZIE-2606.patch
>
>
> Oozie adds all of the jars in the Oozie Spark sharelib to the 
> DistributedCache such that all jars will be present in the current working 
> directory of the YARN container (as well as in the container classpath). 
> However, this is not quite enough to make Spark 2.0 work, since Spark 2.0 by 
> default looks for the jars in assembly/target/scala-2.11/jars [1] (as if it 
> is a locally built distribution for development) and will not find them in 
> the current working directory.
> To fix this, we can set spark.yarn.jars to *.jar so that it finds the jars in 
> the current working directory rather than looking in the wrong place. [2]
> [1] 
> https://github.com/apache/spark/blob/v2.0.0-rc2/launcher/src/main/java/org/apache/spark/launcher/CommandBuilderUtils.java#L357
> [2] 
> https://github.com/apache/spark/blob/v2.0.0-rc2/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala#L476
> Note: This property will be ignored by Spark 1.x.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2661:


Test failures are flaky.

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2667) Optimize queries for DB export

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2667:
--

Testing JIRA OOZIE-2667

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1807
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Optimize queries for DB export
> --
>
> Key: OOZIE-2667
> URL: https://issues.apache.org/jira/browse/OOZIE-2667
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2667.001.patch, OOZIE-2667.002.patch
>
>
> Right now OozieDBExportCLI uses named queries, some of which are sorting the 
> result which is not necessary. 
> They should be checked and replaced with faster queries when possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

Changes:

[rohini] OOZIE-2569 Adding yarn-site, core-site, hdfs-site and mapred-site into

[rohini] OOZIE-2491 oozie acl cannot specify group,it does not work

[rohini] OOZIE-2498 Oozie CallerId configuration for downstream components

--
[...truncated 6257 lines...]
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-tools ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 11 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile 

[jira] [Commented] (OOZIE-2664) SharelibService should never purge currently used sharelib

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2664:
---

It would be good to store the active and previously used ones that still fall 
within the retention time in memory or ZK in case of HA and not purge them.

> SharelibService should never purge currently used sharelib
> --
>
> Key: OOZIE-2664
> URL: https://issues.apache.org/jira/browse/OOZIE-2664
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>
> We came across the following scenario:
> - the user uploads several newer sharelibs
> - before running sharelibupdate,  some tests are run and the update is 
> scheduled to a maintenance window
> - SharelibService.purgeLibs can delete the currently active sharelib
> The purge should watch for the currently active sharelib and never delete it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1854) Sharelib purging for HA

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-1854:
---

bq. This would allow individual oozie server to purge the launcher sharelib 
without affecting others.
  Problem with this is that sometimes hosts can go down and you will have to 
replace with another without bringing up the dead one again. That will leave 
orphans. Better thing is to store state in ZK

> Sharelib purging for HA
> ---
>
> Key: OOZIE-1854
> URL: https://issues.apache.org/jira/browse/OOZIE-1854
> Project: Oozie
>  Issue Type: Bug
>  Components: HA
>Reporter: Purshotam Shah
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-1854-1.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2582) Populating external child Ids for action failures

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2582:
---

Few comments:
  1) Can you move below declarations from PigMain to LauncherMain and replace 
references of oozie.action.externalChildIDs with that constant?
{code}
public static final String ACTION_PREFIX = "oozie.action.";
public static final String EXTERNAL_CHILD_IDS = ACTION_PREFIX + 
"externalChildIDs";
public static final String EXTERNAL_ACTION_STATS = ACTION_PREFIX + 
"stats.properties";
public static final String EXTERNAL_STATS_WRITE = ACTION_PREFIX + 
"external.stats.write";
{code}
  2) 
https://issues.apache.org/jira/browse/OOZIE-2503?focusedCommentId=15315945=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15315945

Distcp and Spark child job url was added by [~satishsaley] only in this release 
(OOZIE-2471 and OOZIE-2503) in Oozie 4.3. But they were implemented by 
overwriting getCaptureOutput to true and implementing getActionData and writing 
to output.properties instead of externalChildIDs. Had asked him to create 
OOZIE-2561 to remove that and write directly to externalChildIDs. Can you take 
care of that in this patch? HiveMain, Hive2Main and SqoopMain also need to be 
changed similarly but the code existed in previous releases. So for jobs that 
were launched before upgrade, we need to still read from output.properties. i.e

{code}
String externalIDs = 
actionData.get(LauncherMapper.ACTION_DATA_EXTERNAL_CHILD_IDS);
if (externalIDs != null) {
context.setExternalChildIDs(externalIDs);
LOG.info(XLog.STD, "Hadoop Jobs launched : [{0}]", 
externalIDs);
} 
else if (LauncherMapperHelper.hasOutputData(actionData)) {
// Load stored Hadoop jobs ids and promote them as external child 
ids
// This is for jobs launched with older release during upgrade to 
Oozie 4.3
Properties props = PropertiesUtils.stringToProperties(actionData

.get(LauncherMapper.ACTION_DATA_OUTPUT_PROPS)
   if (props.get(LauncherMain.HADOOP_JOBS) != null) {
context.setExternalChildIDs((String) 
props.get(LauncherMain.HADOOP_JOBS));
LOG.info(XLog.STD, "Hadoop Jobs launched : [{0}]", externalIDs);
}
}
{code}
Your current patch writes to externalChildIds in addition to the properties 
file. With above change you need to only write to externalChildIds file. Please 
remove readExternalChildIDs in JavaActionExecutor as well as it will be unused 
after above change. This will also avoid duplication and wastage of storing 
child ids in two fields (action output and external child ids) of 
WorkflowAction in the database. 

4)  Can you put the job ids in a LinkedHashSet (to maintain the order in which 
jobs were launched) first and then create the string? Doing toString() and 
contains check every time is inefficient.
{code}
if (!sb.toString().contains(jobId)) {
+sb.append(separator).append(jobId);
+}
{code}

> Populating external child Ids for action failures
> -
>
> Key: OOZIE-2582
> URL: https://issues.apache.org/jira/browse/OOZIE-2582
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2582-00.patch, OOZIE-2582-01.patch, 
> OOZIE-2582-02.patch, OOZIE-2582-03.patch, OOZIE-2582-04.patch, 
> OOZIE-2582-05.patch
>
>
> Currently Oozie external child ids are populated into workflow bean, when the 
> job/action completes successfully. It should populate external child ids in 
> case of job failures as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2667) Optimize queries for DB export

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2667:
--
Attachment: OOZIE-2667.002.patch

Thank you for the review [~satishsaley] and [~rkanter]!
Extracted queries into constants.


> Optimize queries for DB export
> --
>
> Key: OOZIE-2667
> URL: https://issues.apache.org/jira/browse/OOZIE-2667
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2667.001.patch, OOZIE-2667.002.patch
>
>
> Right now OozieDBExportCLI uses named queries, some of which are sorting the 
> result which is not necessary. 
> They should be checked and replaced with faster queries when possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [SCOPE] Oozie 4.3.0 Release

[Rohini Palaniswamy]

Sorry Abhishek for the long delay. Was on vacation and then busy catching
up with stuff. I did review a bunch of patches today which were marked
4.3.0 and Patch Available apart from those which Robert or others have
already not commented on. Skipping those as they have better context. Tag
my name if there is something else that needs to be looked at.

Regards,
Rohini

On Mon, Sep 19, 2016 at 6:33 AM, Abhishek Bafna 
wrote:

> Hello Robert, Rohini, Purshotam, Jaydeep
>
> As we discussed earlier, will be bumping the priority of some Jira's to
> 'blocker' for to be included into Oozie 4.3.0 release. We will try to
> complete as much possible out of that. (It would to good complete all.)
>
> @All, If I miss something, Please do priorities or send a message here.
>
> Thanks a lot for all the efforts and time we have put in last few weeks.
>
> Thanks,
> Abhishek
> > On Sep 8, 2016, at 10:14 AM, Abhishek Bafna 
> wrote:
> >
> > Hi All,
> >
> > It has been a long time since we started the scope discussion for the
> Oozie-4.3.0 release.
> > Since then a lot of patches got reviewed and committed and I would to
> thank each one you for contributing your efforts for that.
> >
> > I think we should move to the next stage and go into blocker only mode
> from next week (one week). After that 7-10 days for preparing and
> completing release condidate.
> >
> > We did plan to update some of the old tech and some of them are still
> pending for review. If can spend time into reviewing them, it would be
> good, else we might have to move without them.
> >
> > There are also some good to have patches available for review and
> commit, I will bump up the priority for them. If I miss something, please
> feel free to do the same.
> >
> > Regards,
> > Abhishek
> >
> >> On Aug 31, 2016, at 2:30 PM, Abhishek Bafna 
> wrote:
> >>
> >> Hi All,
> >>
> >> Can we please look into these upgrade related bugs?
> >>
> >> ActiveMQ https://issues.apache.org/jira/browse/OOZIE-2552
> >> HttpClient   https://issues.apache.org/jira/browse/OOZIE-2538
> >> OpenJPA  https://issues.apache.org/jira/browse/OOZIE-2488
> >> Curator  https://issues.apache.org/jira/browse/OOZIE-2231
> >> Hive https://issues.apache.org/jira/browse/OOZIE-2613
> >>
> >> Are the current patches good and feedback if there is any.
> >>
> >> Also, If we can do some reviews collectively.
> >>
> >> Thanks,
> >> Abhishek
> >>
> >>> On Aug 27, 2016, at 1:14 AM, Abhishek Bafna 
> wrote:
> >>>
> >>> Hello All,
> >>>
> >>> How is it looking now?
> >>>
> >>> I think we should move to blocker and critical patch mode. If
> required, we can take couple of days extra there.
> >>>
> >>> ~Abhishek
>  On Aug 19, 2016, at 11:31 AM, Abhishek Bafna 
> wrote:
> 
>  Sure Robert. We can use some more time.
> 
>  ~Abhishek
> > On Aug 19, 2016, at 7:13 AM, Robert Kanter 
> wrote:
> >
> > Do you think we could wait one more week?  I've been really hammered
> with
> > some other work and there's more that I'd like to review here that I
> > haven't been able to get to.
> >
> > thanks
> > - Robert
> >
> > On Fri, Aug 12, 2016 at 2:30 AM, Abhishek Bafna <
> bafna.i...@gmail.com>
> > wrote:
> >
> >> Sure. I guess we can one extra week and complete some more work.
> >> Thanks everyone for responding.
> >>
> >> ~Abhishek
> >>> On Aug 12, 2016, at 2:46 PM, Purshotam Shah <
> purus...@yahoo-inc.com.INVALID>
> >> wrote:
> >>>
> >>> Yes. I also have some pending patches.
> >>>
> >>> On Friday, August 12, 2016 2:11 AM, Robert Kanter <
> >> rkan...@cloudera.com> wrote:
> >>>
> >>>
> >>> Ya, I could use some more time as well.  I have some deadlines
> early next
> >>> week, which has kept me from doing more reviews.
> >>>
> >>> thanks
> >>> - Robert
> >>>
> >>> On Thu, Aug 11, 2016 at 11:04 AM, jaydeep vishwakarma <
> >>> jaydeepma...@gmail.com> wrote:
> >>>
>  Let see if we can wait for another week. So we can merge few more
> >> important
>  jiras.  Few of them I personally want to get reviewed and merged.
> 
>  Regards,
>  Jaydeep
> 
>  On Thu, Aug 11, 2016 at 4:09 PM, Abhishek Bafna <
> bafna.i...@gmail.com>
>  wrote:
> 
> > As previously discussed, we will be moving with whatever patches
> can be
> > reviewed/merged till end of this week.
> >
> > But there are some which needs to be reviewed and merged, mainly
>  regarding
> > the upgrades. Some of the patches require Java 1.7, so I think we
> >> should
> > review OOZIE-2036 and merged it.
> >
> > ~Abhishek
> >> On Aug 4, 2016, at 12:37 AM, Rohini Palaniswamy <
>  

[jira] [Updated] (OOZIE-2573) dataset url which contains spaces can not be handled rightly

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2573:
--
Assignee: WangMeng

[~sjtufighter],
  It is kind of hacky to just encode space. Need to encode the uri path for all 
special characters. You can use something like URLEncoder, but before that you 
need to just parse path out to avoid encoding the whole url. A simpler solution 
would be to use the Path class in hadoop which already does that. Can you do 
new Path(uri).toUri(); instead?



> dataset url  which contains spaces can not be handled rightly
> -
>
> Key: OOZIE-2573
> URL: https://issues.apache.org/jira/browse/OOZIE-2573
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: WangMeng
>Assignee: WangMeng
> Fix For: 4.3.0
>
> Attachments: OOZIE-2573.01.patch
>
>
> Currently , Oozie does not escape special character-spaces , this will lead 
> to dataset url  which contains spaces can not be handled rightly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2667) Optimize queries for DB export

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2667:
--

Testing JIRA OOZIE-2667

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 3 line(s) longer than 132 
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1807
.Tests failed: 0
.Tests errors: 1

.The patch failed the following testcases:

.  

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Optimize queries for DB export
> --
>
> Key: OOZIE-2667
> URL: https://issues.apache.org/jira/browse/OOZIE-2667
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2667.001.patch
>
>
> Right now OozieDBExportCLI uses named queries, some of which are sorting the 
> result which is not necessary. 
> They should be checked and replaced with faster queries when possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

Changes:

[rohini] OOZIE-2588 Support getting credentials for same cluster hcat when

[rohini] OOZIE-2675 Drop support for hadoop 0.23 (abhishekbafna via rohini)

[rohini] New testcase of OOZIE-2588 which was missed in the first commit

--
[...truncated 6269 lines...]
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[jira] [Commented] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2661:
--

Testing JIRA OOZIE-2661

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1807
.Tests failed: 6
.Tests errors: 6

.The patch failed the following testcases:

.  testCoordinatorActionEvent(org.apache.oozie.event.TestEventGeneration)
.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This 

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

[Apache Jenkins Server]

See 

Changes:

[rohini] OOZIE-2588 Support getting credentials for same cluster hcat when

[rohini] OOZIE-2675 Drop support for hadoop 0.23 (abhishekbafna via rohini)

[rohini] New testcase of OOZIE-2588 which was missed in the first commit

--
[...truncated 6306 lines...]
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- 

[jira] [Commented] (OOZIE-2273) MiniOozie does not work outside of Oozie

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2273:
---

+1. Good to have this fixed.

> MiniOozie does not work outside of Oozie
> 
>
> Key: OOZIE-2273
> URL: https://issues.apache.org/jira/browse/OOZIE-2273
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 4.2.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2273.001.patch
>
>
> {{MiniOozie}} doesn't appear to work correctly outside of Oozie, due to some 
> hardcoded paths/assumptions.  We should fix this.
> As a quick workaround, I added the "core" folder and sub folders/files.  For 
> example:
> {noformat}
> project-root
> |- src
> |- pom.xml
> |- (other typical maven stuff)
> |- core
> |- |- src
> |- |- |- test
> |- |- |- |- resources
> |- |- |- |- |- hadoop-config.xml (a copy of this file [1])
> {noformat}
> Also, the Metastore doesn't work properly either (not sure why).  It can be 
> disabled by adding {{System.setProperty("oozie.test.metastore.server", 
> "false");}} in the {{setUp()}} method, as done at \[2], but we should fix 
> that as well.
> \[1] 
> https://raw.githubusercontent.com/apache/oozie/master/core/src/test/resources/hadoop-config.xml
> \[2] 
> https://github.com/apache/oozie/blob/master/minitest/src/test/java/org/apache/oozie/test/WorkflowTest.java#L45



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2667) Optimize queries for DB export

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2667:
--

I'm not sure that's necessary.  The output format isn't supposed to be 
user-facing.  

I think we should use {{private static final String}} constants for each of the 
queries in here though.

> Optimize queries for DB export
> --
>
> Key: OOZIE-2667
> URL: https://issues.apache.org/jira/browse/OOZIE-2667
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2667.001.patch
>
>
> Right now OozieDBExportCLI uses named queries, some of which are sorting the 
> result which is not necessary. 
> They should be checked and replaced with faster queries when possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2338) Invalid configuration defined reported for some valid configs

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2338:
---

1) Connection timeout and socket timeout are different. One is for establishing 
connection and other is for response. Better to keep two different settings for 
them. I am fine getting rid of SMTP_TIMEOUT and using 
EMAIL_SMTP_SOCKET_TIMEOUT_MS instead. But can we add equivalent 
EmailActionExecutor.EMAIL_CONNECTION_SOCKET_TIMEOUT_MS for 
SMTP_CONNECTION_TIMEOUT and use that in EmailActionExecutor as well for 
connection timeout.
{code}
-String smtpConnectTimeout = conf.get(SMTP_CONNECTION_TIMEOUT, 
SMTP_CONNECTION_TIMEOUT_DEFAULT);
-String smtpTimeout = conf.get(SMTP_TIMEOUT, SMTP_TIMEOUT_DEFAULT);
+Integer timeoutMillisInt = 
ConfigurationService.getInt(EmailActionExecutor.EMAIL_SMTP_SOCKET_TIMEOUT_MS);
{code}
2)  String path = ConfigurationService.get(HCAT_CONFIGURATION).trim();
  Not a fan of this idea as it is hacky. Requires adding dummy values to 
oozie-default.xml when it does not make sense and handling the dummy value in 
code. I would rather have them included in a separate list like 
VERIFY_PREFIX_PROPERTIES_TO_IGNORE and be skipped.

> Invalid configuration defined reported for some valid configs
> -
>
> Key: OOZIE-2338
> URL: https://issues.apache.org/jira/browse/OOZIE-2338
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2338.001.patch, OOZIE-2338.002.patch
>
>
> OOZIE-1890 moved all default config values from the code and oozie-site into 
> oozie-default; it also added a WARN message on startup when a config is found 
> in oozie-site that's not defined in oozie-default.  
> However, this can produce some false positives.  In particular, we observed 
> these:
> {noformat}
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.auth]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.host]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.HCatAccessorService.hcat.configuration]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.from.address]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.ProxyUserService.proxyuser.hue.hosts]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.GroupsService.hadoop.security.group.mapping]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.port]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.ProxyUserService.proxyuser.hue.groups]
> {noformat}
> While harmful, these messages may be concerning or confusing for users.
> Some of these are simply missing from oozie-default (because they have no 
> default value?), while others such as the ProxyUserService configs, will 
> require special handling because the property name can vary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2622) ExtJS 2.2 in no available

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2622:
--

I've created LEGAL-269 to get advice on what to do here.

> ExtJS 2.2 in no available
> -
>
> Key: OOZIE-2622
> URL: https://issues.apache.org/jira/browse/OOZIE-2622
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Sergey Svinarchuk
>Priority: Blocker
> Fix For: 4.3.0
>
>
> ExtJS 2.2 is no longer available by link from Oozie docs - 
> http://dev.sencha.com/deploy/ext-2.2.zip 
> (http://oozie.apache.org/docs/4.2.0/DG_QuickStart.html)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2622) ExtJS 2.2 in no available

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2622:
--

At some point, it might make sense to redo the Oozie Web UI given how old extjs 
is (plus, the current Web UI is pretty ugly).  We had looked into including a 
stripped down version of Hue's Oozie Dashboard as the Web UI, but because it's 
in python, we ran into some complications with building.  

> ExtJS 2.2 in no available
> -
>
> Key: OOZIE-2622
> URL: https://issues.apache.org/jira/browse/OOZIE-2622
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Sergey Svinarchuk
>Priority: Blocker
> Fix For: 4.3.0
>
>
> ExtJS 2.2 is no longer available by link from Oozie docs - 
> http://dev.sencha.com/deploy/ext-2.2.zip 
> (http://oozie.apache.org/docs/4.2.0/DG_QuickStart.html)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2622) ExtJS 2.2 in no available

[Jaydeep Vishwakarma (JIRA)]

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

Jaydeep Vishwakarma commented on OOZIE-2622:


[~rkanter], I am not sure if we can use the same code from somewhere else also, 
I have gone through License https://www.sencha.com/legal/GPL/ , unable to 
interpret. I would recommend you to go through license. We should be careful 
before putting the link. 
Oozie Monitoring UI is one of most useful feature what oozie user use. If we 
are not able to use it, We have to find some alternate solution. 

> ExtJS 2.2 in no available
> -
>
> Key: OOZIE-2622
> URL: https://issues.apache.org/jira/browse/OOZIE-2622
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Sergey Svinarchuk
>Priority: Blocker
> Fix For: 4.3.0
>
>
> ExtJS 2.2 is no longer available by link from Oozie docs - 
> http://dev.sencha.com/deploy/ext-2.2.zip 
> (http://oozie.apache.org/docs/4.2.0/DG_QuickStart.html)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2525) SchemaChecker fails with NPE

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2525:
---

+1. 

[~rkanter],
   Can you make SchemaCheckerRunnable class private before checking in? It is 
not referenced from anywhere else and so need to keep it package visible. 

> SchemaChecker fails with NPE
> 
>
> Key: OOZIE-2525
> URL: https://issues.apache.org/jira/browse/OOZIE-2525
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2525.001.patch
>
>
> {code}
> 2016-05-03 14:38:03,851  WARN SchedulerService:523 [pool-1-thread-2] - 
> SERVER[-] Error executing runnable [SchemaCheckerRunnable], null
> java.lang.NullPointerException
> at 
> org.apache.oozie.service.SchemaCheckerService.access$002(SchemaCheckerService.java:29)
> at 
> org.apache.oozie.service.SchemaCheckerService$SchemaCheckerRunnable.run(SchemaCheckerService.java:120)
> at 
> org.apache.oozie.service.SchedulerService$2.run(SchedulerService.java:175)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> 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)
> {code}
> It;s trying to use SchemaCheckerService before it is initialized.
> {code:title=SchemaCheckerService.java}
> Services.get().get(SchemaCheckerService.class).status = "DISABLED (not leader 
> in HA)";
> Services.get().get(SchemaCheckerService.class).lastCheck = 
> "N/A";
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2667) Optimize queries for DB export

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2667:


+1 {{non-binding}} can we document somewhere that results are not ordered?

> Optimize queries for DB export
> --
>
> Key: OOZIE-2667
> URL: https://issues.apache.org/jira/browse/OOZIE-2667
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2667.001.patch
>
>
> Right now OozieDBExportCLI uses named queries, some of which are sorting the 
> result which is not necessary. 
> They should be checked and replaced with faster queries when possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1793) Improve find bugs reporting for Oozie

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-1793:
---

+1. Good to have this added.

> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-1793-01.patch, OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie.  And even if it does 
> work, it looks like it's just going to create an XML file.  
> Based on some minor refactoring to this 
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
>  and this [stack overflow 
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
>  I was able to improve our findbugs reporting.  Now, when you run {{mvn 
> verify}} (which we use to generate a checkstyle report), it will also run 
> findbugs and transform the resulting XML files into html files that are human 
> readable.
> The hard part here will be actually going through the reports and fixing 
> these bugs; but that's for other JIRAs :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2676:
---

I'll look into the test failures, there shouldn't be any. (and we have a lot 
less flaky ones)
Thanks [~satishsaley] for the suggestion, I'll change those values as well.



> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2676:
--

Sure, that sounds good then.

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2491) oozie acl cannot specify group,it does`t work

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2491:
---

[~rohini] Thanks for review and committing it. I will take care of your 
suggestion. Thanks.

> oozie acl cannot specify group,it does`t work
> -
>
> Key: OOZIE-2491
> URL: https://issues.apache.org/jira/browse/OOZIE-2491
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.1.0
>Reporter: Lingang Deng
>Assignee: Abhishek Bafna
>Priority: Minor
> Fix For: 4.3.0
>
> Attachments: OOZIE-2491-01.patch
>
>
> when I do oozie acl, specify oozie.job.acl=aclGroup, it doesn`t work when 
> modify the job with user which belong to the aclGroup.By debugging source 
> code, " groupsService.getGroups(user).equals(aclItem) ", a List object 
> compare to a String object ,it`s false forever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2676:
---

I think, it would be better to change the default profile, so when the user 
compile and build the Oozie, It will be done using Hadoop 2, without passing 
any specific parameter. Also many of us pointed, most of the consumers use 
Hadoop 2.

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2657:
--

Ya, it wouldn't be a backwards compatibility issue.  I just meant, at least to 
me, it's less clear because instead of just seeing that it's {{public static}} 
or whatever in the code directly, I have to go and think about "Ok, this is an 
interface, so that means that...".  

But if that's the best practices, I suppose that's fine then.

> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
>  Labels: code-cleanup
> Fix For: 4.3.0
>
> Attachments: OOZIE-2657-00-amend.patch, OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the 
> Oozie interface still explicitly declare these redundant access modifier. I 
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant 
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for 
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2491) oozie acl cannot specify group,it does`t work

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2491:
---

Abhishek,
Don't stress yourself with uploading patches to review board if it is just 
few lines of change and fix is easily understandable looking at the patch file 
itself.

> oozie acl cannot specify group,it does`t work
> -
>
> Key: OOZIE-2491
> URL: https://issues.apache.org/jira/browse/OOZIE-2491
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.1.0
>Reporter: Lingang Deng
>Assignee: Abhishek Bafna
>Priority: Minor
> Fix For: 4.3.0
>
> Attachments: OOZIE-2491-01.patch
>
>
> when I do oozie acl, specify oozie.job.acl=aclGroup, it doesn`t work when 
> modify the job with user which belong to the aclGroup.By debugging source 
> code, " groupsService.getGroups(user).equals(aclItem) ", a List object 
> compare to a String object ,it`s false forever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2676:
--

Do we want to change the default profile in Oozie itself?  Or just the jenkins 
run?

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2667) Optimize queries for DB export

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-2667:
-
Summary: Optimize queries for DB export  (was: Optimize querries for DB 
export)

> Optimize queries for DB export
> --
>
> Key: OOZIE-2667
> URL: https://issues.apache.org/jira/browse/OOZIE-2667
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2667.001.patch
>
>
> Right now OozieDBExportCLI uses named queries, some of which are sorting the 
> result which is not necessary. 
> They should be checked and replaced with faster queries when possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2661) Coordinator Action status not updated when workflow job SUSPENDED

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-2661:
---
Attachment: OOZIE-2661-3.patch

> Coordinator Action status not updated when workflow job SUSPENDED
> -
>
> Key: OOZIE-2661
> URL: https://issues.apache.org/jira/browse/OOZIE-2661
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2661-1.patch, OOZIE-2661-2.patch, 
> OOZIE-2661-3.patch
>
>
> It's a bug in Oozie. CoordActionCheckXCommand doesn't take care of SUSPENDED 
> state. It only handles SUCCEEDED, FAILED and KILLED.
> {code}
> protected Void execute() throws CommandException {
> try {
> InstrumentUtils.incrJobCounter(getName(), 1, 
> getInstrumentation());
> Status slaStatus = null;
> CoordinatorAction.Status initialStatus = coordAction.getStatus();
> if (workflowJob.getStatus() == WorkflowJob.Status.SUCCEEDED) {
> coordAction.setStatus(CoordinatorAction.Status.SUCCEEDED);
> // set pending to false as the status is SUCCEEDED
> coordAction.setPending(0);
> slaStatus = Status.SUCCEEDED;
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.FAILED) {
> coordAction.setStatus(CoordinatorAction.Status.FAILED);
> slaStatus = Status.FAILED;
> // set pending to false as the status is FAILED
> coordAction.setPending(0);
> }
> else {
> if (workflowJob.getStatus() == WorkflowJob.Status.KILLED) 
> {
> 
> coordAction.setStatus(CoordinatorAction.Status.KILLED);
> slaStatus = Status.KILLED;
> // set pending to false as the status is KILLED
> coordAction.setPending(0);
> }
> else {
> LOG.warn("Unexpected workflow " + workflowJob.getId() 
> + " STATUS " + workflowJob.getStatus());
> coordAction.setLastModifiedTime(new Date());
> CoordActionQueryExecutor.getInstance().executeUpdate(
> 
> CoordActionQueryExecutor.CoordActionQuery.UPDATE_COORD_ACTION_FOR_MODIFIED_DATE,
> coordAction);
> return null;
> }
> }
> }
> {code}
> Thank you [~puru] for pointing it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2676:


One trivial thing- we can change the properties {{hadoop.version}} and 
{{hadoop.majorversion}} in [main 
pom.xml|https://github.com/apache/oozie/blob/master/pom.xml#L81-L82]. These 
values are getting picked up from default profile though.

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2676) Make hadoop-2 as the default profile

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2676:
--

Testing JIRA OOZIE-2676

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1804
.Tests failed: 27
.Tests errors: 22

.The patch failed the following testcases:

.  testConfiguration(org.apache.oozie.servlet.TestV1AdminServlet)
.  testInstrumentation(org.apache.oozie.servlet.TestV1AdminServlet)
.  testStatus(org.apache.oozie.servlet.TestV1AdminServlet)
.  testJavaSysProps(org.apache.oozie.servlet.TestV1AdminServlet)
.  testOsEnv(org.apache.oozie.servlet.TestV1AdminServlet)
.  testSafeMode(org.apache.oozie.servlet.TestV1AdminServlet)
.  testAvailableTimeZones(org.apache.oozie.servlet.TestV1AdminServlet)
.  testVersion(org.apache.oozie.servlet.TestV1AdminServlet)
.  testV1QueueDump(org.apache.oozie.servlet.TestV1AdminServlet)
.  testSubmit(org.apache.oozie.servlet.TestJobsServlet)
.  testDiffUser(org.apache.oozie.servlet.TestJobsServlet)
.  testCallbackGet(org.apache.oozie.servlet.TestCallbackServlet)
.  testCallbackPost(org.apache.oozie.servlet.TestCallbackServlet)
.  testSLA(org.apache.oozie.servlet.TestV2SLAServlet)
.  testBundleSLA(org.apache.oozie.servlet.TestV2SLAServlet)
.  testSubmit(org.apache.oozie.servlet.TestV1JobsServlet)
.  testRecovery(org.apache.oozie.action.hadoop.TestJavaActionExecutor)
.  testConfiguration(org.apache.oozie.servlet.TestAdminServlet)
.  testInstrumentation(org.apache.oozie.servlet.TestAdminServlet)
.  testShareLib(org.apache.oozie.servlet.TestAdminServlet)
.  testStatus(org.apache.oozie.servlet.TestAdminServlet)
.  testJavaSysProps(org.apache.oozie.servlet.TestAdminServlet)
.  testOsEnv(org.apache.oozie.servlet.TestAdminServlet)
.  testShareLibUpdate(org.apache.oozie.servlet.TestAdminServlet)
.  testSafeMode(org.apache.oozie.servlet.TestAdminServlet)
.  testVersion(org.apache.oozie.servlet.TestAdminServlet)
.  testVersion(org.apache.oozie.servlet.TestVersionServlet)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

--
[...truncated 7435 lines...]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz
  [get] To: 

...
[mkdir] Created dir: 

   [gunzip] Expanding 

 to 

[untar] Expanding: 

 into 

   [delete] Deleting directory 

[mkdir] Created dir: 

   [delete] Deleting: 

 [copy] Copying 1 file to 

[jira] [Commented] (OOZIE-2634) Queue dump command message is confusing when the queue is empty

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2634:
--

Testing JIRA OOZIE-2634

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 1 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1804
.Tests failed: 6
.Tests errors: 4

.The patch failed the following testcases:

.  
testCoordActionInputCheckXCommandUniqueness(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Queue dump command message is confusing when the queue is empty
> ---
>
> Key: OOZIE-2634
> URL: https://issues.apache.org/jira/browse/OOZIE-2634
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Minor
>  Labels: newbie
> Fix For: 4.4.0
>
> Attachments: OOZIE-2634.001.patch, OOZIE-2634.002.patch
>
>
> If the callable queue is empty, and you run the queue dump command, the 
> message says:
> {noformat}
> # oozie admin queuedump
> [Server Queue Dump]:
> Queue dump is null!
> **
> [Server Uniqueness Map Dump]:
> Uniqueness dump is null!
> {noformat}
> This message makes it sound like a bad thing, especially the exclamation 
> mark.  We should change the message to something more neutral and helpful, 
> like "The queue is empty" or something like that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

--
[...truncated 6303 lines...]
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz
  [get] To: 

[jira] [Commented] (OOZIE-2670) Upgrade Hbase to 1.2

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2670:
---

1) It's just a constructor call, so if there's an exception, the {{connection}} 
would be {{null}} and nothing would happen in the finally block. The {{try}} 
block is there to make sure the connection is closed, exceptions are handled 
elsewhere. 
2) I haven't tried that out yet, I've only checked the two codebases and they 
seem to do the same things. Will do that soon.

I had to exclude {{hadoop-auth}} dependency to make oozie comile with hadoop-1, 
some testing might be needed on that part too.

> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2676) Make hadoop-2 as the default profile

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2676:
--
Attachment: OOZIE-2676.001.patch

Thank you for opening this ticked [~abhishekbafna]!
Attaching first patch version.

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
> Attachments: OOZIE-2676.001.patch
>
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OOZIE-2676) Make hadoop-2 as the default profile

[Peter Cseh (JIRA)]

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

Peter Cseh reassigned OOZIE-2676:
-

Assignee: Peter Cseh

> Make hadoop-2 as the default profile
> 
>
> Key: OOZIE-2676
> URL: https://issues.apache.org/jira/browse/OOZIE-2676
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Peter Cseh
>
> Currently, {{hadoop-1}} is the default profile in Oozie for build the 
> project. It would be good to make the {{hadoop-2}} profile as default for 
> building Oozie and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2674) Improve oozie commads documentation

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2674:
---

Thank you for this [~abhishekbafna]!
+1 (non-binding)

> Improve oozie commads documentation
> ---
>
> Key: OOZIE-2674
> URL: https://issues.apache.org/jira/browse/OOZIE-2674
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Attachments: OOZIE-2674-00.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OOZIE-2677) Multiple jline version jars in spark sharelib

[Abhishek Bafna (JIRA)]

Abhishek Bafna created OOZIE-2677:
-

 Summary: Multiple jline version jars in spark sharelib
 Key: OOZIE-2677
 URL: https://issues.apache.org/jira/browse/OOZIE-2677
 Project: Oozie
  Issue Type: Bug
  Components: core
Reporter: Abhishek Bafna


Oozie Spark sharelib is packing multiple version of the {{jilne}} jar. I have 
not produce/re-produced any specific issue because of the different versions of 
the {{jline}}, but in general, It is not a good thing.

{noformat}
ab:share abafna$ pwd
/Users/abafna/workspace/apache/oozie/distro/target/oozie-4.3.0-SNAPSHOT/share
ab:share abafna$ find . -name jline*
./lib/hive/jline-0.9.94.jar
./lib/hive2/jline-0.9.94.jar
./lib/pig/jline-0.9.94.jar
./lib/spark/jline-0.9.94.jar
./lib/spark/jline-2.10.5.jar
{noformat}

Here is the dependency tree from spark module for {{jline}}. Full output is 
attached in the bug.

{noformat}
[INFO] +- org.apache.spark:spark-repl_2.10:jar:1.6.1:compile
[INFO] |  +- org.scala-lang:scala-compiler:jar:2.10.5:compile
[INFO] |  +- org.scala-lang:scala-reflect:jar:2.10.5:compile
[INFO] |  \- org.scala-lang:jline:jar:2.10.5:compile
[INFO] | \- org.fusesource.jansi:jansi:jar:1.4:compile


[INFO] +- org.apache.spark:spark-hive_2.10:jar:1.6.1:compile
[INFO] |  +- com.twitter:parquet-hadoop-bundle:jar:1.6.0:compile
[INFO] |  +- org.spark-project.hive:hive-cli:jar:1.2.1.spark:compile
[INFO] |  |  +- commons-cli:commons-cli:jar:1.2:compile
[INFO] |  |  \- jline:jline:jar:0.9.94:compile
[INFO] |  +- org.apache.avro:avro:jar:1.7.7:compile
{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2677) Multiple jline version jars in spark sharelib

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2677:
--
Attachment: tree_spark.txt

> Multiple jline version jars in spark sharelib
> -
>
> Key: OOZIE-2677
> URL: https://issues.apache.org/jira/browse/OOZIE-2677
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
> Attachments: tree_spark.txt
>
>
> Oozie Spark sharelib is packing multiple version of the {{jilne}} jar. I have 
> not produce/re-produced any specific issue because of the different versions 
> of the {{jline}}, but in general, It is not a good thing.
> {noformat}
> ab:share abafna$ pwd
> /Users/abafna/workspace/apache/oozie/distro/target/oozie-4.3.0-SNAPSHOT/share
> ab:share abafna$ find . -name jline*
> ./lib/hive/jline-0.9.94.jar
> ./lib/hive2/jline-0.9.94.jar
> ./lib/pig/jline-0.9.94.jar
> ./lib/spark/jline-0.9.94.jar
> ./lib/spark/jline-2.10.5.jar
> {noformat}
> Here is the dependency tree from spark module for {{jline}}. Full output is 
> attached in the bug.
> {noformat}
> [INFO] +- org.apache.spark:spark-repl_2.10:jar:1.6.1:compile
> [INFO] |  +- org.scala-lang:scala-compiler:jar:2.10.5:compile
> [INFO] |  +- org.scala-lang:scala-reflect:jar:2.10.5:compile
> [INFO] |  \- org.scala-lang:jline:jar:2.10.5:compile
> [INFO] | \- org.fusesource.jansi:jansi:jar:1.4:compile
> [INFO] +- org.apache.spark:spark-hive_2.10:jar:1.6.1:compile
> [INFO] |  +- com.twitter:parquet-hadoop-bundle:jar:1.6.0:compile
> [INFO] |  +- org.spark-project.hive:hive-cli:jar:1.2.1.spark:compile
> [INFO] |  |  +- commons-cli:commons-cli:jar:1.2:compile
> [INFO] |  |  \- jline:jline:jar:0.9.94:compile
> [INFO] |  +- org.apache.avro:avro:jar:1.7.7:compile
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OOZIE-2676) Make hadoop-2 as the default profile

[Abhishek Bafna (JIRA)]

Abhishek Bafna created OOZIE-2676:
-

 Summary: Make hadoop-2 as the default profile
 Key: OOZIE-2676
 URL: https://issues.apache.org/jira/browse/OOZIE-2676
 Project: Oozie
  Issue Type: Bug
  Components: core
Reporter: Abhishek Bafna


Currently, {{hadoop-1}} is the default profile in Oozie for build the project. 
It would be good to make the {{hadoop-2}} profile as default for building Oozie 
and running the unit testcase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2675:
--

Testing JIRA OOZIE-2675

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1804
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Drop support for hadoop 0.23
> 
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

[jira] [Updated] (OOZIE-2457) Oozie log parsing regex consume more than 90% cpu

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2457:
--
Priority: Blocker  (was: Minor)

> Oozie log parsing regex consume more than 90% cpu
> -
>
> Key: OOZIE-2457
> URL: https://issues.apache.org/jira/browse/OOZIE-2457
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: OOZIE-2457-1.patch, OOZIE-2457-2.patch, 
> OOZIE-2457-3.patch
>
>
> http-0.0.0.0-4080-26  TID=62215  STATE=RUNNABLE  CPU_TIME=1992 (92.59%)  
> USER_TIME=1990 (92.46%) Allocted: 269156584
> java.util.regex.Pattern$Curly.match0(Pattern.java:4170)
> java.util.regex.Pattern$Curly.match(Pattern.java:4132)
> java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
> java.util.regex.Matcher.match(Matcher.java:1221)
> java.util.regex.Matcher.matches(Matcher.java:559)
> org.apache.oozie.util.XLogFilter.matches(XLogFilter.java:136)
> 
> org.apache.oozie.util.TimestampedMessageParser.parseNextLine(TimestampedMessageParser.java:145)
> 
> org.apache.oozie.util.TimestampedMessageParser.increment(TimestampedMessageParser.java:92)
> Regex 
> {code}
> (.* USER\[[^\]]*\] GROUP\[[^\]]*\] TOKEN\[[^\]]*\] APP\[[^\]]*\] 
> JOB\[000-150625114739728-oozie-puru-W\] ACTION\[[^\]]*\] .*)
> {code}
> For single line parsing we use two regex.
> 1. 
> {code}
> public ArrayList splitLogMessage(String logLine) {
> Matcher splitter = SPLITTER_PATTERN.matcher(logLine);
> if (splitter.matches()) {
> ArrayList logParts = new ArrayList();
> logParts.add(splitter.group(1));// timestamp
> logParts.add(splitter.group(2));// log level
> logParts.add(splitter.group(3));// Log Message
> return logParts;
> }
> else {
> return null;
> }
> }
> {code}
> 2.
> {code}
>  public boolean matches(ArrayList logParts) {
> if (getStartDate() != null) {
> if (logParts.get(0).substring(0, 
> 19).compareTo(getFormattedStartDate()) < 0) {
> return false;
> }
> }
> String logLevel = logParts.get(1);
> String logMessage = logParts.get(2);
> if (this.logLevels == null || 
> this.logLevels.containsKey(logLevel.toUpperCase())) {
> Matcher logMatcher = filterPattern.matcher(logMessage);
> return logMatcher.matches();
> }
> else {
> return false;
> }
> }
> {code}
> Also there is repetitive parsing  for same log message in
> {code}
> private String parseTimestamp(String line) {
> String timestamp = null;
> ArrayList logParts = filter.splitLogMessage(line);
> if (logParts != null) {
> timestamp = logParts.get(0);
> }
> return timestamp;
> }
> {code}
> where the {{line}} has already parsed using regex and we already know the 
> {{logParts}} if any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2501) ZK reentrant lock doesn't work for few cases

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2501:
--
Priority: Blocker  (was: Major)

> ZK reentrant lock doesn't work for few cases
> 
>
> Key: OOZIE-2501
> URL: https://issues.apache.org/jira/browse/OOZIE-2501
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2501-V2.patch, OOZIE-2501-V4.patch
>
>
> We will have an issue when oozie trying to acquire a lock and at the same 
> time, some other thread is releasing the same lock .
> acquireLock will wait for 5 sec to acquire the lock. It will bypass the 
> synchronized block and get lockEntry from the hashmap.
> While it waiting for 5 sec to acquire the lock, other thread releases the 
> lock and may execute the release code which will remove  lockEntry from the 
> map.
> If some other command from same thread tries to acquire the lock, it will 
> create a new InterProcessReadWriteLock object and use that for acquiring the 
> lock. 
> Logic for lock acquiring.
> {code}
>  public LockToken getWriteLock(String resource, long wait) throws 
> InterruptedException {
> InterProcessReadWriteLock lockEntry;
> synchronized (zkLocks) {
> if (zkLocks.containsKey(resource)) {
> lockEntry = zkLocks.get(resource);
> }
> else {
> lockEntry = new InterProcessReadWriteLock(zk.getClient(), 
> LOCKS_NODE + "/" + resource);
> zkLocks.put(resource, lockEntry);
> }
> }
> InterProcessMutex writeLock = lockEntry.writeLock();
> return acquireLock(wait, writeLock, resource);
> }
> {code}
> Logic for lock releasing
> {code}
> public void release() {
> try {
> lock.release();
> if (zkLocks.get(resource) == null) {
> return;
> }
> if (!isLockHeld()) {
> synchronized (zkLocks) {
> if (zkLocks.get(resource) != null) {
> if (!isLockHeld()) {
> zkLocks.remove(resource);
> }
> }
> }
> }
> }
> catch (Exception ex) {
> LOG.warn("Could not release lock: " + ex.getMessage(), ex);
> }
> }
> {code}
> Curator code to acquire lock.
> {code}
> private boolean internalLock(long time, TimeUnit unit) throws Exception
> {
> /*
>Note on concurrency: a given lockData instance
>can be only acted on by a single thread so locking isn't necessary
> */
> Thread  currentThread = Thread.currentThread();
> LockDatalockData = threadData.get(currentThread);
> if ( lockData != null )
> {
> // re-entering
> lockData.lockCount.incrementAndGet();
> return true;
> }
> String lockPath = internals.attemptLock(time, unit, 
> getLockNodeBytes());
> if ( lockPath != null )
> {
> LockDatanewLockData = new LockData(currentThread, 
> lockPath);
> threadData.put(currentThread, newLockData);
> return true;
> }
> return false;
> }
> {code}
> The approach we have followed is to use map with weakvalue. Once the lock is 
> unreachable. GC will remove it from the map. We don't have to explicitly 
> remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2231) Upgrade curator to latest version 2.11.0

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2231:
--
Priority: Blocker  (was: Major)

> Upgrade curator to latest version 2.11.0
> 
>
> Key: OOZIE-2231
> URL: https://issues.apache.org/jira/browse/OOZIE-2231
> Project: Oozie
>  Issue Type: Bug
>  Components: HA
>Reporter: Purshotam Shah
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch, 
> OOZIE-2231-02.patch, OOZIE-2231-02.patch, OOZIE-2231-03.patch
>
>
> It have some fix related to InterProcessReadWriteLock, ChildReaper, 
> LeaderSelector which we use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-1793:
--
Priority: Blocker  (was: Major)

> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-1793-01.patch, OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie.  And even if it does 
> work, it looks like it's just going to create an XML file.  
> Based on some minor refactoring to this 
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
>  and this [stack overflow 
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
>  I was able to improve our findbugs reporting.  Now, when you run {{mvn 
> verify}} (which we use to generate a checkstyle report), it will also run 
> findbugs and transform the resulting XML files into html files that are human 
> readable.
> The hard part here will be actually going through the reports and fixing 
> these bugs; but that's for other JIRAs :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-1978) Forkjoin validation code is ridiculously slow in some cases

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-1978:
--
Priority: Blocker  (was: Major)

> Forkjoin validation code is ridiculously slow in some cases
> ---
>
> Key: OOZIE-1978
> URL: https://issues.apache.org/jira/browse/OOZIE-1978
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk, 4.0.1
>Reporter: Robert Kanter
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-1978-001.patch, OOZIE-1978-002.patch, 
> OOZIE-1978-002.patch, OOZIE-1978-003.patch, OOZIE-1978-004.patch, 
> OOZIE-1978-005.patch, OOZIE-1978-006.patch, OOZIE-1978_wip.001.patch, 
> workflow.xml
>
>
> We've had a few users who have run into problems where submitting a workflow 
> appears to hang (in the case of a subworkflow, it's similar but stuck in 
> PREP).  It turns out that if you wait long enough, it will actually go 
> through and the workflow will run normally.  The problem is that the forkjoin 
> validation code is taking a really long time.
> The attached example has a series of 20 forks where each fork has 6 actions 
> (it's based on an actual workflow, but all of the names were changed and the 
> actions were all replaced by simple shell actions).  One of our support guys 
> said it took 1-2 hours , but on my computer it was taking {color:red}*15+ 
> hours*{color} (I had to cancel it)
> While this example doesn't have any nested forks, those can also take a long 
> time too.
> It's easy to verify that it's the forkjoin validation code that's taking so 
> long by looking at a jstack of the Oozie server and seeing deep recursive 
> calls to 
> {{org.apache.oozie.workflow.lite.LiteWorkflowAppParser.validateForkJoin}}.  I 
> also noticed a lot of sitting around in calls LinkedList.contains.  
> I think we have 3 options:
> # See if we can make the existing code faster somehow.  Perhaps there's a way 
> to parallelize it?  Maybe there's some redundant checking that we can 
> identify and skip? Change some data structures? etc
> # See if we can write a new way to do this validation.  I had originally 
> completely rewritten this code a while ago, and we've since made a few fixes 
> to catch edge cases and things.  Perhaps it needs another rewrite?
> # Try to identify when it's taking a long time and at least let the user know 
> what's happening or something.  Right now, it just appears that the Oozie CLI 
> has hung and the job doesn't show up in the Oozie server.  Most users aren't 
> going to wait more than a minute or two.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2613:
--
Priority: Blocker  (was: Major)

> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, 
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, 
> OOZIE-2613-06.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2675) Drop support for hadoop 0.23

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2675:
--
Priority: Blocker  (was: Major)

> Drop support for hadoop 0.23
> 
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [SCOPE] Oozie 4.3.0 Release

[Abhishek Bafna]

Hello Robert, Rohini, Purshotam, Jaydeep

As we discussed earlier, will be bumping the priority of some Jira's to 
'blocker' for to be included into Oozie 4.3.0 release. We will try to complete 
as much possible out of that. (It would to good complete all.)

@All, If I miss something, Please do priorities or send a message here.

Thanks a lot for all the efforts and time we have put in last few weeks.

Thanks,
Abhishek
> On Sep 8, 2016, at 10:14 AM, Abhishek Bafna  wrote:
> 
> Hi All,
> 
> It has been a long time since we started the scope discussion for the 
> Oozie-4.3.0 release.
> Since then a lot of patches got reviewed and committed and I would to thank 
> each one you for contributing your efforts for that.
> 
> I think we should move to the next stage and go into blocker only mode from 
> next week (one week). After that 7-10 days for preparing and completing 
> release condidate.
> 
> We did plan to update some of the old tech and some of them are still pending 
> for review. If can spend time into reviewing them, it would be good, else we 
> might have to move without them.
> 
> There are also some good to have patches available for review and commit, I 
> will bump up the priority for them. If I miss something, please feel free to 
> do the same.
> 
> Regards,
> Abhishek
> 
>> On Aug 31, 2016, at 2:30 PM, Abhishek Bafna  wrote:
>> 
>> Hi All,
>> 
>> Can we please look into these upgrade related bugs?
>> 
>> ActiveMQ https://issues.apache.org/jira/browse/OOZIE-2552
>> HttpClient   https://issues.apache.org/jira/browse/OOZIE-2538
>> OpenJPA  https://issues.apache.org/jira/browse/OOZIE-2488
>> Curator  https://issues.apache.org/jira/browse/OOZIE-2231
>> Hive https://issues.apache.org/jira/browse/OOZIE-2613
>> 
>> Are the current patches good and feedback if there is any.
>> 
>> Also, If we can do some reviews collectively.
>> 
>> Thanks,
>> Abhishek
>> 
>>> On Aug 27, 2016, at 1:14 AM, Abhishek Bafna  wrote:
>>> 
>>> Hello All,
>>> 
>>> How is it looking now?
>>> 
>>> I think we should move to blocker and critical patch mode. If required, we 
>>> can take couple of days extra there.
>>> 
>>> ~Abhishek
 On Aug 19, 2016, at 11:31 AM, Abhishek Bafna  wrote:
 
 Sure Robert. We can use some more time.
 
 ~Abhishek
> On Aug 19, 2016, at 7:13 AM, Robert Kanter  wrote:
> 
> Do you think we could wait one more week?  I've been really hammered with
> some other work and there's more that I'd like to review here that I
> haven't been able to get to.
> 
> thanks
> - Robert
> 
> On Fri, Aug 12, 2016 at 2:30 AM, Abhishek Bafna 
> wrote:
> 
>> Sure. I guess we can one extra week and complete some more work.
>> Thanks everyone for responding.
>> 
>> ~Abhishek
>>> On Aug 12, 2016, at 2:46 PM, Purshotam Shah 
>>> 
>> wrote:
>>> 
>>> Yes. I also have some pending patches.
>>> 
>>> On Friday, August 12, 2016 2:11 AM, Robert Kanter <
>> rkan...@cloudera.com> wrote:
>>> 
>>> 
>>> Ya, I could use some more time as well.  I have some deadlines early 
>>> next
>>> week, which has kept me from doing more reviews.
>>> 
>>> thanks
>>> - Robert
>>> 
>>> On Thu, Aug 11, 2016 at 11:04 AM, jaydeep vishwakarma <
>>> jaydeepma...@gmail.com> wrote:
>>> 
 Let see if we can wait for another week. So we can merge few more
>> important
 jiras.  Few of them I personally want to get reviewed and merged.
 
 Regards,
 Jaydeep
 
 On Thu, Aug 11, 2016 at 4:09 PM, Abhishek Bafna 
 wrote:
 
> As previously discussed, we will be moving with whatever patches can 
> be
> reviewed/merged till end of this week.
> 
> But there are some which needs to be reviewed and merged, mainly
 regarding
> the upgrades. Some of the patches require Java 1.7, so I think we
>> should
> review OOZIE-2036 and merged it.
> 
> ~Abhishek
>> On Aug 4, 2016, at 12:37 AM, Rohini Palaniswamy <
 rohini.adi...@gmail.com>
> wrote:
>> 
>> Cleaned up that list and now no jira refers to "trunk".  Patch
 Available
>> jiras targeted for trunk now point to 4.4.0.
>> 
>> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20Oozie%20AND%20fixVersion%20%3D%204.3.0%20and%20status%
> 20%3D%20%22Patch%20Available%22%20ORDER%20BY%20status%20DESC
>> 
>> There are 42 jiras to go. We can take a look mid next week to see if
 any
>> pending ones needs to be pushed out. There are quite a few which are
>> unassigned.

[jira] [Issue Comment Deleted] (OOZIE-2675) Drop support for hadoop 0.23

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna updated OOZIE-2675:
--
Comment: was deleted

(was: [~asasvari] I am able to execute the testcase with {{hadoop-2}} profile. 
Thanks.)

> Drop support for hadoop 0.23
> 
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2675:
---

[~asasvari] I am able to execute the testcase with {{hadoop-2}} profile. Thanks.

> Drop support for hadoop 0.23
> 
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23

[Abhishek Bafna (JIRA)]

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

Abhishek Bafna commented on OOZIE-2675:
---

[~asasvari] I am able to execute the testcase with {{hadoop-2}} profile. Thanks.

> Drop support for hadoop 0.23
> 
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch, OOZIE-2675-01.patch
>
>
> Drop support for Hadoop 0.23.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

Changes:

[jvishwakarma] OOZIE-2657 Clean up redundant access modifiers from oozie 
interfaces

--
[...truncated 9687 lines...]
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 

  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz
  [get] To: 

[jira] [Updated] (OOZIE-2634) Queue dump command message is confusing when the queue is empty

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2634:

Attachment: OOZIE-2634.002.patch

Unit tests.

> Queue dump command message is confusing when the queue is empty
> ---
>
> Key: OOZIE-2634
> URL: https://issues.apache.org/jira/browse/OOZIE-2634
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Minor
>  Labels: newbie
> Fix For: 4.4.0
>
> Attachments: OOZIE-2634.001.patch, OOZIE-2634.002.patch
>
>
> If the callable queue is empty, and you run the queue dump command, the 
> message says:
> {noformat}
> # oozie admin queuedump
> [Server Queue Dump]:
> Queue dump is null!
> **
> [Server Uniqueness Map Dump]:
> Uniqueness dump is null!
> {noformat}
> This message makes it sound like a bad thing, especially the exclamation 
> mark.  We should change the message to something more neutral and helpful, 
> like "The queue is empty" or something like that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2662) DB migration fails if DB is too big

[Ferenc Denes (JIRA)]

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

Ferenc Denes updated OOZIE-2662:

Summary: DB migration fails if DB is too big  (was: DB migration fails is 
DB is too big)

> DB migration fails if DB is too big
> ---
>
> Key: OOZIE-2662
> URL: https://issues.apache.org/jira/browse/OOZIE-2662
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Andras Piros
> Attachments: OOZIE-2662.001.patch
>
>
> The initial version of the DB import tool commits all the workflows, actions 
> etc. in one huge commit. If it does not fits into the memory, AOOME is thrown.
> We should commit every 1k or 10k elements to prevent this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 52021: Drop support for hadoop 0.23

[Abhishek Bafna]

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

(Updated Sept. 19, 2016, 10:45 a.m.)


Review request for oozie.


Bugs: OOZIE-2675
https://issues.apache.org/jira/browse/OOZIE-2675


Repository: oozie-git


Description
---

Drop support for hadoop 0.23


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/HadoopELFunctions.java 
c322887 
  core/src/main/java/org/apache/oozie/command/wf/SubmitMRXCommand.java 9124a45 
  core/src/main/java/org/apache/oozie/util/JobUtils.java a4d7272 
  core/src/test/java/org/apache/oozie/test/XTestCase.java 8ce44f3 
  docs/src/site/twiki/DG_QuickStart.twiki 2cfaa51 
  docs/src/site/twiki/DG_SqoopActionExtension.twiki 1e7f2a8 
  docs/src/site/twiki/ENG_Building.twiki d138817 
  hadooplibs/hadoop-auth-0.23/pom.xml 7b3b466 
  hadooplibs/hadoop-distcp-0.23/pom.xml 60c8e02 
  hadooplibs/hadoop-utils-0.23/pom.xml a55e647 
  
hadooplibs/hadoop-utils-0.23/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java
 dca7820 
  
hadooplibs/hadoop-utils-0.23/src/main/java/org/apache/oozie/hadoop/utils/HadoopShims.java
 799dffb 
  hadooplibs/pom.xml 17f1f07 
  pom.xml 0712d4c 

Diff: https://reviews.apache.org/r/52021/diff/


Testing
---


Thanks,

Abhishek Bafna

[jira] [Commented] (OOZIE-2662) DB migration fails is DB is too big

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2662:
---

Thanks for the feedback [~jaydeepvishwakarma]!
I think we should try to continue the import from where it has failed if 
possible. 

> DB migration fails is DB is too big
> ---
>
> Key: OOZIE-2662
> URL: https://issues.apache.org/jira/browse/OOZIE-2662
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Andras Piros
> Attachments: OOZIE-2662.001.patch
>
>
> The initial version of the DB import tool commits all the workflows, actions 
> etc. in one huge commit. If it does not fits into the memory, AOOME is thrown.
> We should commit every 1k or 10k elements to prevent this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2634) Queue dump command message is confusing when the queue is empty

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2634:

Attachment: OOZIE-2634.001.patch

> Queue dump command message is confusing when the queue is empty
> ---
>
> Key: OOZIE-2634
> URL: https://issues.apache.org/jira/browse/OOZIE-2634
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Minor
>  Labels: newbie
> Fix For: 4.4.0
>
> Attachments: OOZIE-2634.001.patch
>
>
> If the callable queue is empty, and you run the queue dump command, the 
> message says:
> {noformat}
> # oozie admin queuedump
> [Server Queue Dump]:
> Queue dump is null!
> **
> [Server Uniqueness Map Dump]:
> Uniqueness dump is null!
> {noformat}
> This message makes it sound like a bad thing, especially the exclamation 
> mark.  We should change the message to something more neutral and helpful, 
> like "The queue is empty" or something like that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces

[Jaydeep Vishwakarma (JIRA)]

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

Jaydeep Vishwakarma commented on OOZIE-2657:


[~rkanter], 
The changes are in {{interface}} and it does not change so frequently, except 
the {{interface}} with contains only {{constants}}. 
Also I believe removing redundant access modifier will make any backward 
compatibility issue, perhaps you meant something else?
It is common knowledge in case of interface that everything is public (there is 
no point in putting a private member, because you are actually establishing an 
interface) and and all assignments are final, because no instance it is also at 
class level. Java's native supplied JDK interfaces don't put these modifiers. 
So if you want to follow best practices, that is what you would follow.


> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
>  Labels: code-cleanup
> Fix For: 4.3.0
>
> Attachments: OOZIE-2657-00-amend.patch, OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the 
> Oozie interface still explicitly declare these redundant access modifier. I 
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant 
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for 
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2634) Queue dump command message is confusing when the queue is empty

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2634:
-

New output style for empty queue dumps is:

{code}
# bash-3.2$ bin/oozie admin -oozie http://localhost:11000/oozie -queuedump
**
[Server Queue Dump]:
The queue dump is empty, nothing to display.
**
[Server Uniqueness Map Dump]:
The uniqueness map dump is empty, nothing to display.
**
{code}

> Queue dump command message is confusing when the queue is empty
> ---
>
> Key: OOZIE-2634
> URL: https://issues.apache.org/jira/browse/OOZIE-2634
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Minor
>  Labels: newbie
> Fix For: 4.4.0
>
>
> If the callable queue is empty, and you run the queue dump command, the 
> message says:
> {noformat}
> # oozie admin queuedump
> [Server Queue Dump]:
> Queue dump is null!
> **
> [Server Uniqueness Map Dump]:
> Uniqueness dump is null!
> {noformat}
> This message makes it sound like a bad thing, especially the exclamation 
> mark.  We should change the message to something more neutral and helpful, 
> like "The queue is empty" or something like that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2675:
---

[~abhishekbafna] thanks a lot. I went through the modifications and it mostly 
looks good to me (I have only 1 comment on sqoop action's documentation). 

By the way, did you run tests against the hadoop-2 profile too? I assume so, 
and no thing should break by these changed, but I am asking just to be on the 
safe side.(Upstream QA build only runs tests with hadoop-1 profile - 
https://builds.apache.org/job/oozie-trunk-precommit-build/3293/consoleFull).

A related question coming from [~gezapeti], that might be addressed in a 
separate JIRA: can we change the default profile to hadoop-2? 

It would make the tests run somewhat slower (because of the time required for 
yarn/miniyarn cluster components' setup), but as far as I know most of the 
users are using hadoop-2 and dropping hadoop-1 support is also on the Oozie 
roadmap  (i.e. Oozie on YARN).


> Drop support for hadoop 0.23
> 
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch
>
>
> Drop support for Hadoop 0.23.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2675) Drop support for hadoop 0.23

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2675:
---

I think it would make sense to make the hadoop-2 profile the default so the 
tests would run on that. Most of the users are using hadoop 2.


> Drop support for hadoop 0.23
> 
>
> Key: OOZIE-2675
> URL: https://issues.apache.org/jira/browse/OOZIE-2675
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2675-00.patch
>
>
> Drop support for Hadoop 0.23.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 52021: Drop support for hadoop 0.23

[Attila Sasvari]

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




docs/src/site/twiki/DG_SqoopActionExtension.twiki (line 13)


According to  
https://sqoop.apache.org/docs/1.4.3/SqoopUserGuide.html#_prerequisites

Sqoop is currently supporting 4 major Hadoop releases - 0.20, 0.23, 1.0 and 
2.0.


- Attila Sasvari


On Sept. 19, 2016, 5:21 a.m., Abhishek Bafna wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/52021/
> ---
> 
> (Updated Sept. 19, 2016, 5:21 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2675
> https://issues.apache.org/jira/browse/OOZIE-2675
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Drop support for hadoop 0.23
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/HadoopELFunctions.java 
> c322887 
>   core/src/main/java/org/apache/oozie/command/wf/SubmitMRXCommand.java 
> 9124a45 
>   core/src/main/java/org/apache/oozie/util/JobUtils.java a4d7272 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 8ce44f3 
>   docs/src/site/twiki/DG_QuickStart.twiki 2cfaa51 
>   docs/src/site/twiki/DG_SqoopActionExtension.twiki 1e7f2a8 
>   docs/src/site/twiki/ENG_Building.twiki d138817 
>   hadooplibs/hadoop-auth-0.23/pom.xml 7b3b466 
>   hadooplibs/hadoop-distcp-0.23/pom.xml 60c8e02 
>   hadooplibs/hadoop-utils-0.23/pom.xml a55e647 
>   
> hadooplibs/hadoop-utils-0.23/src/main/java/org/apache/oozie/action/hadoop/LauncherMainHadoopUtils.java
>  dca7820 
>   
> hadooplibs/hadoop-utils-0.23/src/main/java/org/apache/oozie/hadoop/utils/HadoopShims.java
>  799dffb 
>   hadooplibs/pom.xml 17f1f07 
>   pom.xml 0712d4c 
> 
> Diff: https://reviews.apache.org/r/52021/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Abhishek Bafna
> 
>

[jira] [Updated] (OOZIE-2634) Queue dump command message is confusing when the queue is empty

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2634:

Summary: Queue dump command message is confusing when the queue is empty  
(was: queue dump command message is confusing when the queue is empty)

> Queue dump command message is confusing when the queue is empty
> ---
>
> Key: OOZIE-2634
> URL: https://issues.apache.org/jira/browse/OOZIE-2634
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Minor
>  Labels: newbie
> Fix For: 4.4.0
>
>
> If the callable queue is empty, and you run the queue dump command, the 
> message says:
> {noformat}
> # oozie admin queuedump
> [Server Queue Dump]:
> Queue dump is null!
> **
> [Server Uniqueness Map Dump]:
> Uniqueness dump is null!
> {noformat}
> This message makes it sound like a bad thing, especially the exclamation 
> mark.  We should change the message to something more neutral and helpful, 
> like "The queue is empty" or something like that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OOZIE-2634) queue dump command message is confusing when the queue is empty

[Andras Piros (JIRA)]

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

Andras Piros reassigned OOZIE-2634:
---

Assignee: Andras Piros

> queue dump command message is confusing when the queue is empty
> ---
>
> Key: OOZIE-2634
> URL: https://issues.apache.org/jira/browse/OOZIE-2634
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Minor
>  Labels: newbie
> Fix For: 4.4.0
>
>
> If the callable queue is empty, and you run the queue dump command, the 
> message says:
> {noformat}
> # oozie admin queuedump
> [Server Queue Dump]:
> Queue dump is null!
> **
> [Server Uniqueness Map Dump]:
> Uniqueness dump is null!
> {noformat}
> This message makes it sound like a bad thing, especially the exclamation 
> mark.  We should change the message to something more neutral and helpful, 
> like "The queue is empty" or something like that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2657) Clean up redundant access modifiers from oozie interfaces

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2657:
--

[~jaydeepvishwakarma], [~abhishekbafna]
I'm not sure this is a good idea.  It's going to make backporting patches (e.g. 
Cloudera, Yahoo!, Hortonworks, etc) harder because it makes a lot of changes to 
a lot of files (the same reason we don't do a mass cleanup of imports).  IMO, 
that would be better left to fixing when we make other changes to those files.  
I'm also not sure there's any real benefit to removing the redundant modifiers? 
 In fact, isn't it more clear with them?

> Clean up redundant access modifiers from oozie interfaces
> -
>
> Key: OOZIE-2657
> URL: https://issues.apache.org/jira/browse/OOZIE-2657
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Minor
>  Labels: code-cleanup
> Fix For: 4.3.0
>
> Attachments: OOZIE-2657-00-amend.patch, OOZIE-2657-00.patch
>
>
> By default java {{interface}} fields are {{public static final}}. Some of the 
> Oozie interface still explicitly declare these redundant access modifier. I 
> think we can clean it.
> Similarly, methods declared in the interface are {{public}}. This redundant 
> declaration can be cleaned up.
> {code}
> public interface RestConstants {
> public static final String VERSIONS = "versions";
> public static final String JOB = "job";
> ...
> }
> public interface JsonTags {
> public static final String OOZIE_SAFE_MODE = "safeMode"; //Applicable for 
> V0 only
> public static final String OOZIE_SYSTEM_MODE = "systemMode";
> ...
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (86 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues-test.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues-test.apache.org/jira/browse/OOZIE-2618
OOZIE-2617  Read properties files in action configurations
https://issues-test.apache.org/jira/browse/OOZIE-2617
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues-test.apache.org/jira/browse/OOZIE-2616
OOZIE-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues-test.apache.org/jira/browse/OOZIE-2606
OOZIE-2589  CompletedActionXCommand priority param is of no effect
https://issues-test.apache.org/jira/browse/OOZIE-2589
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues-test.apache.org/jira/browse/OOZIE-2588
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues-test.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues-test.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues-test.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues-test.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues-test.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues-test.apache.org/jira/browse/OOZIE-2572
OOZIE-2571  Add scala.binary.version Maven property so that Scala 2.11 can be 
used
https://issues-test.apache.org/jira/browse/OOZIE-2571
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues-test.apache.org/jira/browse/OOZIE-2569
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues-test.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues-test.apache.org/jira/browse/OOZIE-2564
OOZIE-2552  Update ActiveMQ version for security and other fixes
https://issues-test.apache.org/jira/browse/OOZIE-2552
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues-test.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues-test.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues-test.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues-test.apache.org/jira/browse/OOZIE-2528
OOZIE-2521  Filter options are case sensitive for jobtye=bundle
https://issues-test.apache.org/jira/browse/OOZIE-2521
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues-test.apache.org/jira/browse/OOZIE-2518
OOZIE-2517  Add support for startCreatedTime and endCreatedTime filters for 
coord and bundles
https://issues-test.apache.org/jira/browse/OOZIE-2517
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues-test.apache.org/jira/browse/OOZIE-2513
OOZIE-2512  ShareLibservice returns incorrect path for jar
https://issues-test.apache.org/jira/browse/OOZIE-2512
OOZIE-2508  Documentation change for Coord action rerun [OOZIE-1735]
https://issues-test.apache.org/jira/browse/OOZIE-2508
OOZIE-2501  ZK reentrant lock doesn't work for few cases
https://issues-test.apache.org/jira/browse/OOZIE-2501
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues-test.apache.org/jira/browse/OOZIE-2500
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues-test.apache.org/jira/browse/OOZIE-2499
OOZIE-2498  Oozie CallerId configuration for downstream components 
https://issues-test.apache.org/jira/browse/OOZIE-2498
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues-test.apache.org/jira/browse/OOZIE-2495
OOZIE-2491  oozie acl cannot specify group,it does`t work
https://issues-test.apache.org/jira/browse/OOZIE-2491