Re: Updating affected version

2015-11-23 Thread Robert Kanter 
Hi Mike,

I don't think the versions on the JIRA are taken into account for testing
the patch.  It looks like you figured it out (you have to do --no-prefix)
though.  I'll try to review OOZIE-2185 soon.

- Robert

On Fri, Nov 20, 2015 at 12:47 PM, Mike Grimes  wrote:

> Hi, I recently uploaded a patch to
> https://issues.apache.org/jira/browse/OOZIE-2185 and incorrectly set the
> affected version to "4.2.0" which im assuming is taken into account when
> the patch is applied. This has resulted in the patch not applying - is
> there a way to get the auto applier/tester to apply it to master?
>
> Best,
>

Re: Review Request 40157: OOZIE-2397: LAST_ONLY and NONE don't properly handle READY actions

2015-11-23 Thread Purshotam Shah 

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



core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java (line 
778)


I guess we missing "end_of_duration". If end_of_duration is set we need to 
adjust start time.


- Purshotam Shah


On Nov. 19, 2015, 5:41 a.m., Robert Kanter wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40157/
> ---
> 
> (Updated Nov. 19, 2015, 5:41 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2397
> https://issues.apache.org/jira/browse/OOZIE-2397
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2397
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/CoordinatorActionBean.java c3d4bb4 
>   core/src/main/java/org/apache/oozie/CoordinatorJobBean.java 3ec2eaf 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java
>  179dfbf 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionReadyXCommand.java
>  ad9cb12 
>   core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
> 131368a 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/CoordActionGetForInputCheckJPAExecutor.java
>  e58646b 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/CoordJobGetReadyActionsJPAExecutor.java
>  af81091 
>   core/src/main/java/org/apache/oozie/executor/jpa/CoordJobQueryExecutor.java 
> 45d2fc9 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordActionInputCheckXCommand.java
>  f78dafd 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordActionReadyXCommand.java
>  PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordCommandUtils.java 
> 652d792 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
>  77f5518 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordActionGetForInputCheckJPAExecutor.java
>  ca1d80a 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobGetReadyActionsJPAExecutor.java
>  c666b87 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobQueryExecutor.java
>  ee7ad6a 
>   core/src/test/java/org/apache/oozie/test/XDataTestCase.java e6a7d9c 
>   docs/src/site/twiki/CoordinatorFunctionalSpec.twiki faff37f 
> 
> Diff: https://reviews.apache.org/r/40157/diff/
> 
> 
> Testing
> ---
> 
> - Ran relevant unit tests
> - Verified in a cluster that it now has the correct behavior.  I had a 
> Coordinator with a concurrency of 1 and Coord Actions that took  longer than 
> the frequency.  This way, we'd have READY actions that should transition to 
> SKIPPED once the RUNNING action finished.
> 
> 
> Thanks,
> 
> Robert Kanter
> 
>

[jira] [Commented] (OOZIE-1396) Javadoc warning in SLAMessage.java

2015-11-23 Thread Manjunath Ballur (JIRA) 

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

Manjunath Ballur commented on OOZIE-1396:
-

I checked "SLAMessage.java". All the @return tags have arguments. Should we 
close this?

> Javadoc warning in SLAMessage.java
> --
>
> Key: OOZIE-1396
> URL: https://issues.apache.org/jira/browse/OOZIE-1396
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>  Labels: newbie
> Fix For: trunk
>
>
> There's currently a javadoc warning in SLAMessage.java
> {noformat}
> [WARNING] Javadoc Warnings
> [WARNING] 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/client/src/main/java/org/apache/oozie/client/event/message/SLAMessage.java:188:
>  warning - @return tag has no arguments.
> {noformat}



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

[jira] Subscription: Oozie Patch Available

2015-11-23 Thread jira 
Issue Subscription
Filter: Oozie Patch Available (58 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2402  oozie-setup.sh sharelib create takes a long time on large clusters
https://issues.apache.org/jira/browse/OOZIE-2402
OOZIE-2400  Workflow xml configuration parser cannot deal with namespace prefix
https://issues.apache.org/jira/browse/OOZIE-2400
OOZIE-2397  LAST_ONLY and NONE don't properly handle READY actions
https://issues.apache.org/jira/browse/OOZIE-2397
OOZIE-2390  Rerun with failed option removing completed output data
https://issues.apache.org/jira/browse/OOZIE-2390
OOZIE-2380  Oozie Hive action failed with wrong tmp path
https://issues.apache.org/jira/browse/OOZIE-2380
OOZIE-2362  SQL injection in BulkJPAExecutor
https://issues.apache.org/jira/browse/OOZIE-2362
OOZIE-2357  CoordRerun should queue CoordPushDependencyCheckXCommand if there 
is push dependencies
https://issues.apache.org/jira/browse/OOZIE-2357
OOZIE-2349  Method getCoordJobInfo(String jobId, String filter, int offset, int 
length, boolean desc) is not present in LocalOozieClientCoord
https://issues.apache.org/jira/browse/OOZIE-2349
OOZIE-2348  Recovery service keeps on recovering coord action of suspended jobs
https://issues.apache.org/jira/browse/OOZIE-2348
OOZIE-2338  Invalid configuration defined reported for some valid configs
https://issues.apache.org/jira/browse/OOZIE-2338
OOZIE-2312  oozie doesn't purge audit and error log
https://issues.apache.org/jira/browse/OOZIE-2312
OOZIE-2273  MiniOozie does not work outside of Oozie
https://issues.apache.org/jira/browse/OOZIE-2273
OOZIE-2259  Create a callback action 
https://issues.apache.org/jira/browse/OOZIE-2259
OOZIE-2258  Introducing a new counter in the instrumentation log to distinguish 
between the reasons for launcher failure
https://issues.apache.org/jira/browse/OOZIE-2258
OOZIE-2253  Spark Job is failing when it is running in standalone server
https://issues.apache.org/jira/browse/OOZIE-2253
OOZIE-2244  Oozie should mask passwords in the logs when logging command 
arguments
https://issues.apache.org/jira/browse/OOZIE-2244
OOZIE-2243  Kill Command does not kill the child job for java action
https://issues.apache.org/jira/browse/OOZIE-2243
OOZIE-  Oozie UI parent job should be clickable
https://issues.apache.org/jira/browse/OOZIE-
OOZIE-2203  Fix the login example
https://issues.apache.org/jira/browse/OOZIE-2203
OOZIE-2196  Create Local Client for Bundle
https://issues.apache.org/jira/browse/OOZIE-2196
OOZIE-2185  Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other 
env script)
https://issues.apache.org/jira/browse/OOZIE-2185
OOZIE-2134  Remove references to Services.get().getConf() in code
https://issues.apache.org/jira/browse/OOZIE-2134
OOZIE-2106  Make tomcat download url configurable in the pom file
https://issues.apache.org/jira/browse/OOZIE-2106
OOZIE-2105  Make version of submodules configurable with parent version 
https://issues.apache.org/jira/browse/OOZIE-2105
OOZIE-2099  Add test-patch support for patches generated without --no-prefix
https://issues.apache.org/jira/browse/OOZIE-2099
OOZIE-2081  WorkflowJob notification to include coordinator action id 
https://issues.apache.org/jira/browse/OOZIE-2081
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
OOZIE-2044  ssh action succeed with a not exists command which should be fail.
https://issues.apache.org/jira/browse/OOZIE-2044
OOZIE-2030  Configuration properties from global section is not getting set in 
Hadoop job conf when using sub-workflow action in Oozie workflow.xml 
https://issues.apache.org/jira/browse/OOZIE-2030
OOZIE-2020  Rerun all Failed/killed/timedout coordinator actions rather than 
specifying action numbers
https://issues.apache.org/jira/browse/OOZIE-2020
OOZIE-1980  Sql error should not fail coord job
https://issues.apache.org/jira/browse/OOZIE-1980
OOZIE-1977  Display patch analysis issues
https://issues.apache.org/jira/browse/OOZIE-1977
OOZIE-1936  Queuedump command should display queue information for all server.
https://issues.apache.org/jira/browse/OOZIE-1936
OOZIE-1931  Admin command to print all locks held by server(s)
https://issues.apache.org/jira/browse/OOZIE-1931
OOZIE-1927  Use StoreStatusFilter for WorkflowsJobGetJPAExecutor 
https://issues.apache.org/jira/browse/OOZIE-1927
OOZIE-1922  MemoryLocksService fails if lock is acquired multiple times in same 
thread and released
https://issues.apache.org/jira/browse/OOZIE-1922
OOZIE-1918  ActionXCommand

Re: Review Request 38474: OOZIE-1976- Specifying coordinator input datasets in more logical ways

2015-11-23 Thread Purshotam Shah 

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

(Updated Nov. 24, 2015, 1:17 a.m.)


Review request for oozie.


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


Repository: oozie-git


Description
---

There are three components in this patch

1. User interface
A new tag is added to coordinator.xml
ex.


  
  "
  
   
   
  
  
   
   
 ;



input-check will have nested and/or/combine operation. It can have min and wait 
at operator or at date-in.
If input-check tag is missing then it consider to be old approach where all 
data dependency are needed.

2. Processing
input-check is converted into logical expression
(a&)||(c&)
We use jexl to parse the logical expression.

There are three phase in parsing.
phase 1 : only resolved dataset are parsed ( only current). 
phase 2 : once all current are resolved, then future/latest are parsed.
phase 3 : Doesn't do any filecheck, just return what is being parsed by phase1 
and phase2. Is used for EL functions


3. Storage.
if inputcheck is enable, push_missing_dependencies and missing_dependencies are 
serialized and stored in DB.
If then not then it's old approach, where they are stored in plan text. This is 
backward compatible.


Diffs (updated)
-

  core/pom.xml b063dab79415447a86c1a33f5c3f5304e0dffca0 
  core/src/main/java/org/apache/oozie/CoordinatorActionBean.java 
c3d4bb4d49eb25bdc4f7fe44c3fc0be678a66838 
  core/src/main/java/org/apache/oozie/ErrorCode.java 
6c1e3997c9a1cb0bb0de39d687a083af0a7b5f04 
  
core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java
 179dfbf3616e78b4992118fe7d243af9c6df5c57 
  
core/src/main/java/org/apache/oozie/command/coord/CoordActionUpdatePushMissingDependency.java
 4e1c5b3392358cb6b1e98e16e469310338f27fed 
  core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
131368a7ef248c2d6bf263fb1a8e01fbe94da97f 
  
core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java
 39e6ac15ce3a3ea7f2ed9178688537f7b1d7842d 
  
core/src/main/java/org/apache/oozie/command/coord/CoordPushDependencyCheckXCommand.java
 b05344d89e8df0e11fe69c1aa725d19a18eb0a2b 
  core/src/main/java/org/apache/oozie/coord/CoordELConstants.java 
f010a817fc900821c0e429fc16e1d3902a98d8bb 
  core/src/main/java/org/apache/oozie/coord/CoordELEvaluator.java 
8b2f4560ae66bbcd707a446382e647663ea67be1 
  core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java 
5d238663aa94f0dd55a9190b60bfe621439c7b53 
  core/src/main/java/org/apache/oozie/coord/CoordUtils.java 
94c69740618110ea180b188ab0c5a02db76f8b4d 
  core/src/main/java/org/apache/oozie/coord/SyncCoordAction.java 
44258eb5be40bf6769e32c8780117e8533d80d7e 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/AbstractCoordInputDependency.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependencies.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependenciesBuilder.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependenciesCheck.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependenciesChecker.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependency.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependencyCheck.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependencyCheckPhaseOne.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependencyCheckPhaseThree.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependencyCheckPhaseTwo.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependencyCheckPhaseValidate.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputDependencyFactory.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordInputInstance.java
 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  
core/src/main/java/org/apache/oozie/coord/input/dependency/CoordOldInputDependency.java

Re: Review Request 40157: OOZIE-2397: LAST_ONLY and NONE don't properly handle READY actions

2015-11-23 Thread Robert Kanter 


> On Nov. 23, 2015, 8:15 p.m., Purshotam Shah wrote:
> > core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java, 
> > line 778
> > 
> >
> > I guess we missing "end_of_duration". If end_of_duration is set we need 
> > to adjust start time.

I don't think I'm familiar with "end_of_duration".  What does that do?  How do 
I handle that?


- Robert


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


On Nov. 19, 2015, 5:41 a.m., Robert Kanter wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40157/
> ---
> 
> (Updated Nov. 19, 2015, 5:41 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2397
> https://issues.apache.org/jira/browse/OOZIE-2397
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2397
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/CoordinatorActionBean.java c3d4bb4 
>   core/src/main/java/org/apache/oozie/CoordinatorJobBean.java 3ec2eaf 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java
>  179dfbf 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionReadyXCommand.java
>  ad9cb12 
>   core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
> 131368a 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/CoordActionGetForInputCheckJPAExecutor.java
>  e58646b 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/CoordJobGetReadyActionsJPAExecutor.java
>  af81091 
>   core/src/main/java/org/apache/oozie/executor/jpa/CoordJobQueryExecutor.java 
> 45d2fc9 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordActionInputCheckXCommand.java
>  f78dafd 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordActionReadyXCommand.java
>  PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordCommandUtils.java 
> 652d792 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
>  77f5518 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordActionGetForInputCheckJPAExecutor.java
>  ca1d80a 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobGetReadyActionsJPAExecutor.java
>  c666b87 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobQueryExecutor.java
>  ee7ad6a 
>   core/src/test/java/org/apache/oozie/test/XDataTestCase.java e6a7d9c 
>   docs/src/site/twiki/CoordinatorFunctionalSpec.twiki faff37f 
> 
> Diff: https://reviews.apache.org/r/40157/diff/
> 
> 
> Testing
> ---
> 
> - Ran relevant unit tests
> - Verified in a cluster that it now has the correct behavior.  I had a 
> Coordinator with a concurrency of 1 and Coord Actions that took  longer than 
> the frequency.  This way, we'd have READY actions that should transition to 
> SKIPPED once the RUNNING action finished.
> 
> 
> Thanks,
> 
> Robert Kanter
> 
>

[jira] [Updated] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-23 Thread Mike Grimes (JIRA) 

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

Mike Grimes updated OOZIE-2185:
---
Attachment: OOZIE-2185-1.patch

> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Priority: Minor
>  Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch
>
>
> Currently, the oozie cli doesn't source any environment script.   Users may 
> wish to define environment variables such as OOZIE_URL outside of normal 
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh. 
>  This is somewhat confusing when users see hadoop commands sourcing 
> hadoop-env.sh, mapred-env.sh, etc.



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

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

2015-11-23 Thread Apache Jenkins Server 
See 

--
[...truncated 2521 lines...]
[INFO] 
[INFO] Building Apache Oozie WorkflowGenerator 4.3.0-SNAPSHOT
[INFO] 
Downloading: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/groups/snapshots/com/orange/links/gwt-links/1.3-SNAPSHOT/maven-metadata.xml



Downloading: 
https://repository.apache.org/content/groups/snapshots/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml


605/605 B   

Downloaded: 
http://gwt-links.googlecode.com/svn/repository/com/orange/links/gwt-links-parent/1.3-SNAPSHOT/maven-metadata.xml
 (605 B at 3.6 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
oozie-workflowgenerator ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-workflowgenerator ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-workflowgenerator ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 24 resources to ../../img
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
oozie-workflowgenerator ---
[INFO] Compiling 39 source files to 

[WARNING] 
:[243,30]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[270,30]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[271,26]
 [deprecation] TreeItem(String) in TreeItem has been deprecated
[WARNING] 
:[272,14]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[273,14]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[275,18]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[276,18]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[277,18]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[278,18]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[279,18]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING] 
:[280,18]
 [deprecation] addItem(String) in TreeItem has been deprecated
[WARNING]

[jira] [Updated] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-23 Thread Mike Grimes (JIRA) 

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

Mike Grimes updated OOZIE-2185:
---
Attachment: OOZIE-2185-2.patch

> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Priority: Minor
>  Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch, OOZIE-2185-2.patch
>
>
> Currently, the oozie cli doesn't source any environment script.   Users may 
> wish to define environment variables such as OOZIE_URL outside of normal 
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh. 
>  This is somewhat confusing when users see hadoop commands sourcing 
> hadoop-env.sh, mapred-env.sh, etc.



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

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

2015-11-23 Thread Apache Jenkins Server 
See 

--
[...truncated 8406 lines...]
[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: 

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

[jira] [Commented] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-23 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2185:
--

Testing JIRA OOZIE-2185

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: 1698
.Tests failed: 4
.Tests errors: 0

.The patch failed the following testcases:

.  testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
.  testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)
.  
testMessage_withMixedStatus(org.apache.oozie.command.coord.TestAbandonedCoordChecker)
.  testUpdateSLA(org.apache.oozie.sla.TestSLAService)

{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/2599/

> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Priority: Minor
>  Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch, OOZIE-2185-2.patch
>
>
> Currently, the oozie cli doesn't source any environment script.   Users may 
> wish to define environment variables such as OOZIE_URL outside of normal 
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh. 
>  This is somewhat confusing when users see hadoop commands sourcing 
> hadoop-env.sh, mapred-env.sh, etc.



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

[jira] [Commented] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-23 Thread Mike Grimes (JIRA) 

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

Mike Grimes commented on OOZIE-2185:


There really isn't any tests in place for these client scripts, so I didn't 
feel it was necessary to add them (also not sure where best place for these 
would be, if appropriate at all). Failed tests are unrelated and I think they 
were failing my patch anyways.

> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Priority: Minor
>  Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch, OOZIE-2185-2.patch
>
>
> Currently, the oozie cli doesn't source any environment script.   Users may 
> wish to define environment variables such as OOZIE_URL outside of normal 
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh. 
>  This is somewhat confusing when users see hadoop commands sourcing 
> hadoop-env.sh, mapred-env.sh, etc.



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

[jira] [Updated] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-23 Thread Mike Grimes (JIRA) 

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

Mike Grimes updated OOZIE-2185:
---
Attachment: (was: OOZIE-2185-1.patch)

> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Priority: Minor
>  Labels: client, feature, newbie
>
> Currently, the oozie cli doesn't source any environment script.   Users may 
> wish to define environment variables such as OOZIE_URL outside of normal 
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh. 
>  This is somewhat confusing when users see hadoop commands sourcing 
> hadoop-env.sh, mapred-env.sh, etc.



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

[jira] [Commented] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

2015-11-23 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2185:
--

Testing JIRA OOZIE-2185

Cleaning local git workspace



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



> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -
>
> Key: OOZIE-2185
> URL: https://issues.apache.org/jira/browse/OOZIE-2185
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Justice
>Priority: Minor
>  Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch
>
>
> Currently, the oozie cli doesn't source any environment script.   Users may 
> wish to define environment variables such as OOZIE_URL outside of normal 
> shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh. 
>  This is somewhat confusing when users see hadoop commands sourcing 
> hadoop-env.sh, mapred-env.sh, etc.



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

[jira] [Commented] (OOZIE-2402) oozie-setup.sh sharelib create takes a long time on large clusters

2015-11-23 Thread Illya Yalovyy (JIRA) 

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

Illya Yalovyy commented on OOZIE-2402:
--

[~rkanter], 
Could you please review this patch?

> oozie-setup.sh sharelib create takes a long time on large clusters
> --
>
> Key: OOZIE-2402
> URL: https://issues.apache.org/jira/browse/OOZIE-2402
> Project: Oozie
>  Issue Type: Improvement
>  Components: tools
>Affects Versions: 4.2.0
>Reporter: Illya Yalovyy
> Attachments: OOZIE-2402-1.patch
>
>
> When cluster has 256+ nodes it can take up to 5 minutes to create a sharelib. 
> Copy the tarball itself takes only around 10 seconds. It seems like 
> performance could be improved by loading files concurrently in many threads.



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