[jira] [Updated] (OOZIE-1173) Refactor: use ParamChecker inXOozieClient

[abhishek bafna (JIRA)]

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

abhishek bafna updated OOZIE-1173:
--
Attachment: OOZIE-1173-01.patch

Fixed the testcases.

> Refactor: use ParamChecker inXOozieClient
> -
>
> Key: OOZIE-1173
> URL: https://issues.apache.org/jira/browse/OOZIE-1173
> Project: Oozie
>  Issue Type: Task
>  Components: client, core
>Reporter: jun aoki
>Assignee: abhishek bafna
>Priority: Trivial
>  Labels: newbie
> Fix For: 4.3.0
>
> Attachments: OOZIE-1173-00.patch, OOZIE-1173-01.patch
>
>
> In 
> [XOozieClient.java|http://svn.apache.org/viewvc/oozie/trunk/client/src/main/java/org/apache/oozie/client/XOozieClient.java?revision=1401367&view=markup],
>  you can find a piece of code like this and should be replaced with 
> ParamChecker.
> {code}
>  if (conf == null) {
> throw new IllegalArgumentException("conf cannot be null");
> }
> {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-2625  Drop workflowgenerator
https://issues.apache.org/jira/browse/OOZIE-2625
OOZIE-2623  Oozie should use a dummy OutputFormat
https://issues.apache.org/jira/browse/OOZIE-2623
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues.apache.org/jira/browse/OOZIE-2618
OOZIE-2617  Read properties files in action configurations
https://issues.apache.org/jira/browse/OOZIE-2617
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues.apache.org/jira/browse/OOZIE-2616
OOZIE-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues.apache.org/jira/browse/OOZIE-2606
OOZIE-2589  CompletedActionXCommand priority param is of no effect
https://issues.apache.org/jira/browse/OOZIE-2589
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues.apache.org/jira/browse/OOZIE-2588
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues.apache.org/jira/browse/OOZIE-2572
OOZIE-2571  Add scala.binary.version Maven property so that Scala 2.11 can be 
used
https://issues.apache.org/jira/browse/OOZIE-2571
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues.apache.org/jira/browse/OOZIE-2569
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues.apache.org/jira/browse/OOZIE-2564
OOZIE-2552  Update ActiveMQ version for security and other fixes
https://issues.apache.org/jira/browse/OOZIE-2552
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues.apache.org/jira/browse/OOZIE-2528
OOZIE-2521  Filter options are case sensitive for jobtye=bundle
https://issues.apache.org/jira/browse/OOZIE-2521
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues.apache.org/jira/browse/OOZIE-2518
OOZIE-2517  Add support for startCreatedTime and endCreatedTime filters for 
coord and bundles
https://issues.apache.org/jira/browse/OOZIE-2517
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues.apache.org/jira/browse/OOZIE-2513
OOZIE-2512  ShareLibservice returns incorrect path for jar
https://issues.apache.org/jira/browse/OOZIE-2512
OOZIE-2508  Documentation change for Coord action rerun [OOZIE-1735]
https://issues.apache.org/jira/browse/OOZIE-2508
OOZIE-2501  ZK reentrant lock doesn't work for few cases
https://issues.apache.org/jira/browse/OOZIE-2501
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues.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.apache.org/jira/browse/OOZIE-2499
OOZIE-2498  Oozie CallerId configuration for downstream components 
https://issues.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.apache.org/jira/browse/OOZIE-2495
OOZIE-2491  oozie acl cannot specify group,it does`t work
https://issues.ap

[jira] [Updated] (OOZIE-2081) WorkflowJob notification to include coordinator action id

[Azrael Seoeun (JIRA)]

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

Azrael Seoeun updated OOZIE-2081:
-
Attachment: OOZIE-2081.3.patch

Addressed comment.

> WorkflowJob notification to include coordinator action id 
> --
>
> Key: OOZIE-2081
> URL: https://issues.apache.org/jira/browse/OOZIE-2081
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Reporter: Venkatesan Ramachandran
>Assignee: Azrael Seoeun
> Fix For: 4.4.0
>
> Attachments: OOZIE-2081.1.patch, OOZIE-2081.2.patch, 
> OOZIE-2081.3.patch
>
>
> WorkflowJob notification to include parent_id (coordinator action id) if 
> present. This will help identify if a given workflow job is started by a 
> coordinator action.



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

[jira] [Commented] (OOZIE-2036) Drop support for Java 1.6

[abhishek bafna (JIRA)]

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

abhishek bafna commented on OOZIE-2036:
---

[~gezapeti] Similar to {{targetJavaVersion}} property, we should define one for 
{{sourceJavaVersion}}.

> Drop support for Java 1.6
> -
>
> Key: OOZIE-2036
> URL: https://issues.apache.org/jira/browse/OOZIE-2036
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Peter Cseh
> Fix For: 4.3.0
>
> Attachments: OOZIE-2036-001.patch
>
>
> Hadoop is planning on dropping support for JDK 6, which is EoL, with Hadoop 
> 2.7.  We should probably do the same in Oozie trunk.
> This task involves:
> - Only allow building on JDK 7+
> - Making the build target Java 7



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

[jira] [Commented] (OOZIE-2493) TestDistcpMain deletes action.xml from wrong filesystem

[abhishek bafna (JIRA)]

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

abhishek bafna commented on OOZIE-2493:
---

Thanks [~rkanter] for the review and committing to master.

> TestDistcpMain deletes action.xml from wrong filesystem
> ---
>
> Key: OOZIE-2493
> URL: https://issues.apache.org/jira/browse/OOZIE-2493
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: abhishek bafna
>Assignee: abhishek bafna
>  Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2493-02.patch, OOZIE-2493-03.patch, 
> OOZIE-2493.patch
>
>
> In the TestDistcpMain#testMain test case, it is deleting a file using HDFS 
> FileSystem instance which actually created on a local FileSystem.
> {code}
> // getting file hadoop system instance 
> FileSystem fs = getFileSystem();
> ...
> // creating a storing file on local file system
> File actionXml = new File(getTestCaseDir(), "action.xml");
> ...
> // Now trying to delete the file on hadoop file system
> fs.delete(new Path(getTestCaseDir(), "action.xml"), true);
> {code}



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

[jira] [Commented] (OOZIE-2036) Drop support for Java 1.6

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2036:
--

Testing JIRA OOZIE-2036

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: 1792
{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/3188/

> Drop support for Java 1.6
> -
>
> Key: OOZIE-2036
> URL: https://issues.apache.org/jira/browse/OOZIE-2036
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Peter Cseh
> Fix For: 4.3.0
>
> Attachments: OOZIE-2036-001.patch
>
>
> Hadoop is planning on dropping support for JDK 6, which is EoL, with Hadoop 
> 2.7.  We should probably do the same in Oozie trunk.
> This task involves:
> - Only allow building on JDK 7+
> - Making the build target Java 7



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

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

[Apache Jenkins Server]

See 

Changes:

[rkanter] OOZIE-2493 TestDistcpMain deletes action.xml from wrong filesystem

--
[...truncated 6253 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 2 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 (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-dist

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

[Purshotam Shah (JIRA)]

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

Purshotam Shah commented on OOZIE-2501:
---

Thanks [~pbacsko] I will go through your comments and if needed I will upload a 
new patch.

> 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
> 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] [Commented] (OOZIE-2501) ZK reentrant lock doesn't work for few cases

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2501:
-

Please see my review comments before you commit regarding tests. You might want 
to consider them.

> 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
> 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)

Re: Review Request 47837: OOZIE-2501 ZK reentrant lock doesn't work for few cases

[Peter Bacsko]

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




core/src/test/java/org/apache/oozie/lock/TestMemoryLocks.java (line 29)


Keep in mind that I'm going to make heavy changes in this class, you might 
want to incorporate them.

See: https://issues.apache.org/jira/browse/OOZIE-2584



core/src/test/java/org/apache/oozie/lock/TestMemoryLocks.java (line 339)


Why two distinct variables?



core/src/test/java/org/apache/oozie/lock/TestMemoryLocks.java (line 342)


extract magic number to a constant



core/src/test/java/org/apache/oozie/lock/TestMemoryLocks.java (line 350)


I understand the purpose of this, but System.gc() is very dodgy especially 
in a test. 

I think if you want to test the fact that you use a Guava-based map with 
weak values, you're better off checking types. Guava-specific map is 
MapMakerInternalMap and the field that determines the "strength" of the values 
is valueStrength. It's not nice to access a package-private field with 
reflection but I think it's more acceptable and predictable than System.gc().



core/src/test/java/org/apache/oozie/lock/TestMemoryLocks.java (line 372)


Why does the method start with an underscore? Because of JUnit? Could be 
just simply checkLockRelease().



core/src/test/java/org/apache/oozie/service/TestZKLocksService.java (line 30)


This class suffers from the same problem as TestMemoryLocks, except that 
tests sleep for 1000ms which makes them less prone to errors. We might want to 
create a new JIRA to fix all these Thread.sleep() stuff.



core/src/test/java/org/apache/oozie/service/TestZKLocksService.java (line 524)


See my comments in TestMemoryLocksService



core/src/test/java/org/apache/oozie/service/TestZKLocksService.java (line 553)


Again, method naming


- Peter Bacsko


On aug. 3, 2016, 4:56 du, Purshotam Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47837/
> ---
> 
> (Updated aug. 3, 2016, 4:56 du)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2501
> https://issues.apache.org/jira/browse/OOZIE-2501
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2501 ZK reentrant lock doesn't work for few cases
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/command/wf/ActionStartXCommand.java 
> 41f4430f69cb7a9b132a4000c3e5c8aa7573c0a0 
>   core/src/main/java/org/apache/oozie/lock/MemoryLocks.java 
> 7d65ac0e24a62086732ec91fc24f89b62469451d 
>   core/src/main/java/org/apache/oozie/service/MemoryLocksService.java 
> d7c6a89fd47a219b2ec8ea4fe0caf05dc008943b 
>   core/src/main/java/org/apache/oozie/service/ZKLocksService.java 
> 952b90d5dfbfeccf4600238f75885c792709ffc7 
>   core/src/test/java/org/apache/oozie/lock/TestMemoryLocks.java 
> 61fec19b346748b22df1b58f014c32b1c04c8c1f 
>   core/src/test/java/org/apache/oozie/service/TestZKLocksService.java 
> d1acadfff36fff637fb9ccb8e3feffb24248c792 
> 
> Diff: https://reviews.apache.org/r/47837/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Purshotam Shah
> 
>

[jira] [Commented] (OOZIE-2625) Drop workflowgenerator

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2625:
--

Testing JIRA OOZIE-2625

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: 1792
.Tests failed: 5
.Tests errors: 2

.The patch failed the following testcases:

.  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/3187/

> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2625.001.patch, OOZIE-2625.002.patch
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

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

[Apache Jenkins Server]

See 

--
[...truncated 6487 lines...]
[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 (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.t

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

[Apache Jenkins Server]

See 

--
[...truncated 8111 lines...]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-tools 
---
[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 2 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 (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INF

[jira] [Commented] (OOZIE-2569) Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2569:
--

Testing JIRA OOZIE-2569

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:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{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} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher 
> ---
>
> Key: OOZIE-2569
> URL: https://issues.apache.org/jira/browse/OOZIE-2569
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: abhishek bafna
>Assignee: abhishek bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2569-00.patch, OOZIE-2569-02.patch, 
> OOZIE-2569-03.patch
>
>
> Oozie Spark action requires yarn-site, core-site, hdfs-site and mapred-site 
> to be present in the classpath for launching the spark applications. 
> Currently we manually copy these files into oozie spark sharelib.
> Until it is fixed through the spark, we can copy the 
> {{oozie.action.conf.xml}} file as yarn-site, core-site, hdfs-site and 
> mapred-site, which will avoid manual steps of copying those files.



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

[jira] [Comment Edited] (OOZIE-2566) TestCoordActionInputCheckXCommand.testCoordActionInputCheckXCommandUniqueness() is flaky

[Robert Kanter (JIRA)]

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

Robert Kanter edited comment on OOZIE-2566 at 8/3/16 9:23 PM:
--

I read through the test.  It seems very brittle.  There's non-atomic access to 
a {{long}} and there's multiple cases of reliance on perfect timing.

I think this test needs a more major refactoring.  I'd have to think about it 
some more, but maybe something with some fancier synchronization objects like 
what you did in OOZIE-2584.


was (Author: rkanter):
I read through the test.  It seems very brittle.  There's non-atomic access to 
a {{long}} and there's multiple cases of reliance on perfect timing.

I'd have to think about it some more, but I think this test needs a more major 
refactoring.  Maybe something with some fancier synchronization objects like 
what you did in OOZIE-2584.

> TestCoordActionInputCheckXCommand.testCoordActionInputCheckXCommandUniqueness()
>  is flaky
> 
>
> Key: OOZIE-2566
> URL: https://issues.apache.org/jira/browse/OOZIE-2566
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>
> The testcase testCoordActionInputCheckXCommandUniqueness is unstable.
> We add three XCommands with the same actionId (entityKeys are different) into 
> the CallableQueueService. Only the first XCommand is expected to run.
> The reason why sometimes either the 2nd or 3rd XCommand executes is because 
> as soon as the first starts to run, its removed from the {{uniqueCallables}} 
> map immediately. If the first scheduled task runs quickly, then either the 
> 2nd or 3rd XCommand has the chance to get scheduled.
> Step by step:
> 1. Schedule first XCommand
> 2. XCommand is added to {{uniqueCallables}}
> 3. Schedule second XCommand
> 4. First XCommand starts to run in the thread pool and removes itself from 
> {{uniqueCallables}} (see {{CallableWrapper.run()}})
> 5. Second XCommand can successfully add itself to {{uniqueCallables}}
> 6. Second XCommand starts to run
> Please clarify whether this is the expected behavior of CallableQueueService.
> If not, then moving {{removeFromUniqueCallables()}} to the finally block 
> solves the problem.



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

[jira] [Commented] (OOZIE-2566) TestCoordActionInputCheckXCommand.testCoordActionInputCheckXCommandUniqueness() is flaky

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2566:
--

I read through the test.  It seems very brittle.  There's non-atomic access to 
a {{long}} and there's multiple cases of reliance on perfect timing.

I'd have to think about it some more, but I think this test needs a more major 
refactoring.  Maybe something with some fancier synchronization objects like 
what you did in OOZIE-2584.

> TestCoordActionInputCheckXCommand.testCoordActionInputCheckXCommandUniqueness()
>  is flaky
> 
>
> Key: OOZIE-2566
> URL: https://issues.apache.org/jira/browse/OOZIE-2566
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>
> The testcase testCoordActionInputCheckXCommandUniqueness is unstable.
> We add three XCommands with the same actionId (entityKeys are different) into 
> the CallableQueueService. Only the first XCommand is expected to run.
> The reason why sometimes either the 2nd or 3rd XCommand executes is because 
> as soon as the first starts to run, its removed from the {{uniqueCallables}} 
> map immediately. If the first scheduled task runs quickly, then either the 
> 2nd or 3rd XCommand has the chance to get scheduled.
> Step by step:
> 1. Schedule first XCommand
> 2. XCommand is added to {{uniqueCallables}}
> 3. Schedule second XCommand
> 4. First XCommand starts to run in the thread pool and removes itself from 
> {{uniqueCallables}} (see {{CallableWrapper.run()}})
> 5. Second XCommand can successfully add itself to {{uniqueCallables}}
> 6. Second XCommand starts to run
> Please clarify whether this is the expected behavior of CallableQueueService.
> If not, then moving {{removeFromUniqueCallables()}} to the finally block 
> solves the problem.



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

[jira] [Commented] (OOZIE-2036) Drop support for Java 1.6

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2036:
--

If you look at Cloudera's Oozie pom, we have {{}} and 
{{}}.  We can do something like that.  
https://github.com/cloudera/oozie/blob/cdh5-4.1.0_5.8.0/pom.xml#L47-L48

> Drop support for Java 1.6
> -
>
> Key: OOZIE-2036
> URL: https://issues.apache.org/jira/browse/OOZIE-2036
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Peter Cseh
> Fix For: 4.3.0
>
> Attachments: OOZIE-2036-001.patch
>
>
> Hadoop is planning on dropping support for JDK 6, which is EoL, with Hadoop 
> 2.7.  We should probably do the same in Oozie trunk.
> This task involves:
> - Only allow building on JDK 7+
> - Making the build target Java 7



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

[jira] [Commented] (OOZIE-2036) Drop support for Java 1.6

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2036:
---

Sure thing. I'm also wondering if we could use {{targetJavaVersion}} in more 
places inside the poms.
Maybe we should introduce a separate {{minJavaVersion}} too, so later version 
bums are easier.


> Drop support for Java 1.6
> -
>
> Key: OOZIE-2036
> URL: https://issues.apache.org/jira/browse/OOZIE-2036
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Peter Cseh
> Fix For: 4.3.0
>
> Attachments: OOZIE-2036-001.patch
>
>
> Hadoop is planning on dropping support for JDK 6, which is EoL, with Hadoop 
> 2.7.  We should probably do the same in Oozie trunk.
> This task involves:
> - Only allow building on JDK 7+
> - Making the build target Java 7



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

[jira] [Commented] (OOZIE-2451) Oozie mail action fails due to the Null pointer exception

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2451:
--

CM puts it somewhere under /var/run/cloudera-scm-process or something like 
that.  You can also get to it by looking at the Oozie Server instance Process 
in CM itself.

> Oozie mail action fails due to the Null pointer exception
> -
>
> Key: OOZIE-2451
> URL: https://issues.apache.org/jira/browse/OOZIE-2451
> Project: Oozie
>  Issue Type: Bug
>  Components: action, core, workflow
>Affects Versions: 4.1.0
> Environment: CDH 5.5.1
>Reporter: Ming Hsuan Tu
>
> The workflow is as follows
> {code:xml}
> 
>   
>   m...@example.com
>   ${app_name} in ${date} failed
>   The workflow ${wf:id()} had issues and was killed.
>   
>   
>   
>   
> {code}
> but the mail action just threw up the NULL pointer exception and no other 
> logs can be found.
> I have configured the smtp server correctly.
> This issues occurred when I upgrade to CDH 5.5.1 from CDH 5.4.6.
> Thank you. 



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

[jira] [Commented] (OOZIE-2036) Drop support for Java 1.6

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2036:
--

The patch looks good to me, but we're going to have to rebase it a little after 
OOZIE-2625 gets in (it removes the workflowgenerator stuff), so let's hold off 
until then.

> Drop support for Java 1.6
> -
>
> Key: OOZIE-2036
> URL: https://issues.apache.org/jira/browse/OOZIE-2036
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Peter Cseh
> Fix For: 4.3.0
>
> Attachments: OOZIE-2036-001.patch
>
>
> Hadoop is planning on dropping support for JDK 6, which is EoL, with Hadoop 
> 2.7.  We should probably do the same in Oozie trunk.
> This task involves:
> - Only allow building on JDK 7+
> - Making the build target Java 7



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

[jira] [Updated] (OOZIE-2036) Drop support for Java 1.6

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2036:
--
Attachment: OOZIE-2036-001.patch

Submitted patch v1.

> Drop support for Java 1.6
> -
>
> Key: OOZIE-2036
> URL: https://issues.apache.org/jira/browse/OOZIE-2036
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Peter Cseh
> Fix For: 4.3.0
>
> Attachments: OOZIE-2036-001.patch
>
>
> Hadoop is planning on dropping support for JDK 6, which is EoL, with Hadoop 
> 2.7.  We should probably do the same in Oozie trunk.
> This task involves:
> - Only allow building on JDK 7+
> - Making the build target Java 7



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

[jira] [Assigned] (OOZIE-2036) Drop support for Java 1.6

[Peter Cseh (JIRA)]

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

Peter Cseh reassigned OOZIE-2036:
-

Assignee: Peter Cseh

> Drop support for Java 1.6
> -
>
> Key: OOZIE-2036
> URL: https://issues.apache.org/jira/browse/OOZIE-2036
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Peter Cseh
> Fix For: 4.3.0
>
> Attachments: OOZIE-2036-001.patch
>
>
> Hadoop is planning on dropping support for JDK 6, which is EoL, with Hadoop 
> 2.7.  We should probably do the same in Oozie trunk.
> This task involves:
> - Only allow building on JDK 7+
> - Making the build target Java 7



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

[jira] [Updated] (OOZIE-2493) TestDistcpMain deletes action.xml from wrong filesystem

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-2493:
-
Summary: TestDistcpMain deletes action.xml from wrong filesystem  (was: 
TestDiscp leaves action.xml behind on local filesystem)

> TestDistcpMain deletes action.xml from wrong filesystem
> ---
>
> Key: OOZIE-2493
> URL: https://issues.apache.org/jira/browse/OOZIE-2493
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: abhishek bafna
>Assignee: abhishek bafna
>  Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2493-02.patch, OOZIE-2493-03.patch, 
> OOZIE-2493.patch
>
>
> In the TestDistcpMain#testMain test case, it is deleting a file using HDFS 
> FileSystem instance which actually created on a local FileSystem.
> {code}
> // getting file hadoop system instance 
> FileSystem fs = getFileSystem();
> ...
> // creating a storing file on local file system
> File actionXml = new File(getTestCaseDir(), "action.xml");
> ...
> // Now trying to delete the file on hadoop file system
> fs.delete(new Path(getTestCaseDir(), "action.xml"), true);
> {code}



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

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

[Apache Jenkins Server]

See 

--
[...truncated 8158 lines...]
[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 (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apa

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2501:
--

Testing JIRA OOZIE-2501

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 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{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: 1796
.Tests failed: 3
.Tests errors: 0

.The patch failed the following testcases:

.  
testBundleRerunInPausedWithError(org.apache.oozie.command.bundle.TestBundleRerunXCommand)
.  
testBundleStatusNotTransitionFromKilled(org.apache.oozie.service.TestStatusTransitService)
.  
testBundleStatusCoordSubmitFails(org.apache.oozie.service.TestStatusTransitService)

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

> 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
> 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  curre

[jira] [Commented] (OOZIE-2569) Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2569:
--

Testing JIRA OOZIE-2569

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:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{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: 1792
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testBundleRerunInPausedWithError(org.apache.oozie.command.bundle.TestBundleRerunXCommand)

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

> Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher 
> ---
>
> Key: OOZIE-2569
> URL: https://issues.apache.org/jira/browse/OOZIE-2569
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: abhishek bafna
>Assignee: abhishek bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2569-00.patch, OOZIE-2569-02.patch, 
> OOZIE-2569-03.patch
>
>
> Oozie Spark action requires yarn-site, core-site, hdfs-site and mapred-site 
> to be present in the classpath for launching the spark applications. 
> Currently we manually copy these files into oozie spark sharelib.
> Until it is fixed through the spark, we can copy the 
> {{oozie.action.conf.xml}} file as yarn-site, core-site, hdfs-site and 
> mapred-site, which will avoid manual steps of copying those files.



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

[jira] [Commented] (OOZIE-2493) TestDiscp leaves action.xml behind on local filesystem

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2493:
--

Oh, I understand now.  I didn't read all of the code context.  Deleting the 
file in TestDistcpMain should be fine.
+1 on the 003 patch.

I'd rather not cleanup the testcasedir because it can be helpful for debugging 
unit test failures.



> TestDiscp leaves action.xml behind on local filesystem
> --
>
> Key: OOZIE-2493
> URL: https://issues.apache.org/jira/browse/OOZIE-2493
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: abhishek bafna
>Assignee: abhishek bafna
>  Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2493-02.patch, OOZIE-2493-03.patch, 
> OOZIE-2493.patch
>
>
> In the TestDistcpMain#testMain test case, it is deleting a file using HDFS 
> FileSystem instance which actually created on a local FileSystem.
> {code}
> // getting file hadoop system instance 
> FileSystem fs = getFileSystem();
> ...
> // creating a storing file on local file system
> File actionXml = new File(getTestCaseDir(), "action.xml");
> ...
> // Now trying to delete the file on hadoop file system
> fs.delete(new Path(getTestCaseDir(), "action.xml"), true);
> {code}



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

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

[Apache Jenkins Server]

See 

--
[...truncated 8151 lines...]
[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 (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-1173) Refactor: use ParamChecker inXOozieClient

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1173:
--

Testing JIRA OOZIE-1173

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:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{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: 1792
.Tests failed: 7
.Tests errors: 2

.The patch failed the following testcases:

.  testSomeMethods(org.apache.oozie.client.TestWorkflowXClient)
.  testSubmitMR(org.apache.oozie.client.TestWorkflowXClient)
.  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/3182/

> Refactor: use ParamChecker inXOozieClient
> -
>
> Key: OOZIE-1173
> URL: https://issues.apache.org/jira/browse/OOZIE-1173
> Project: Oozie
>  Issue Type: Task
>  Components: client, core
>Reporter: jun aoki
>Assignee: abhishek bafna
>Priority: Trivial
>  Labels: newbie
> Fix For: 4.3.0
>
> Attachments: OOZIE-1173-00.patch
>
>
> In 
> [XOozieClient.java|http://svn.apache.org/viewvc/oozie/trunk/client/src/main/java/org/apache/oozie/client/XOozieClient.java?revision=1401367&view=markup],
>  you can find a piece of code like this and should be replaced with 
> ParamChecker.
> {code}
>  if (conf == null) {
> throw new IllegalArgumentException("conf cannot be null");
> }
> {code}



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

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

[Apache Jenkins Server]

See 

Changes:

[rkanter] OOZIE-2574 Oozie to support replication-enabled mysql urls

[rkanter] OOZIE-2496 Testcase failure due to environment specific line.separator

--
[...truncated 8140 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] 

[jira] [Updated] (OOZIE-2625) Drop workflowgenerator

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-2625:
-
Attachment: (was: OOZIE-2625.002.patch)

> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2625.001.patch, OOZIE-2625.002.patch
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

[jira] [Updated] (OOZIE-2625) Drop workflowgenerator

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-2625:
-
Attachment: OOZIE-2625.002.patch

There's some png files being deleted, so I needed to generate with 
{{--binary}}.  Let's try again.  I'll also update the Jenkins job to not run 
with {{-Pwfgen}}.

> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2625.001.patch, OOZIE-2625.002.patch, 
> OOZIE-2625.002.patch
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

Re: Review Request 48678: OOZIE-2569 : Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher

[Abhishek Bafna]

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

(Updated Aug. 3, 2016, 8:09 p.m.)


Review request for oozie.


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


Repository: oozie-git


Description
---

Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
97355fd 
  core/src/main/resources/oozie-default.xml 6a9d5c4 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
fb190d6 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/ShellMain.java 
c4a6e9b 
  sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java 
3acaef9 

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


Testing
---

manual testing done.


Thanks,

Abhishek Bafna

[jira] [Updated] (OOZIE-2569) Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher

[abhishek bafna (JIRA)]

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

abhishek bafna updated OOZIE-2569:
--
Attachment: OOZIE-2569-03.patch

Updated the patch with default as {{false}}.

> Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher 
> ---
>
> Key: OOZIE-2569
> URL: https://issues.apache.org/jira/browse/OOZIE-2569
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: abhishek bafna
>Assignee: abhishek bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2569-00.patch, OOZIE-2569-02.patch, 
> OOZIE-2569-03.patch
>
>
> Oozie Spark action requires yarn-site, core-site, hdfs-site and mapred-site 
> to be present in the classpath for launching the spark applications. 
> Currently we manually copy these files into oozie spark sharelib.
> Until it is fixed through the spark, we can copy the 
> {{oozie.action.conf.xml}} file as yarn-site, core-site, hdfs-site and 
> mapred-site, which will avoid manual steps of copying those files.



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

[jira] [Comment Edited] (OOZIE-2493) TestDiscp leaves action.xml behind on local filesystem

[abhishek bafna (JIRA)]

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

abhishek bafna edited comment on OOZIE-2493 at 8/3/16 7:56 PM:
---

[~rkanter] I looked into the classes inheriting from the {{MainTestCase}}. 
Except {{TestDistcpMain}}, all the others are writing into the {{action.xml}} 
just once, so they are not performing the {{delete}} operation on the file. 
Because, It is performing two tests in a single testcase.

Essentially the problem is, after the testcase is completed, in the 
{{tearDown}} method we are just resetting the {{XTestCase#testCaseDir}}, 
instead we should be removing the content of the directory then might set it to 
null. Same goes for the {{XFsTestCase#tearDown}}. Let me know what do you thing 
about this approach.


was (Author: abhishekbafna):
[~rkanter] I looked into the classes inheriting from the {{MainTestCase}}. 
Except {{TestDistcpMain}}, all the others are writing into the {{action.xml}} 
just once, so they are not performing the {{delete}} operation on the file.

Essentially the problem is, after the testcase is completed, in the 
{{tearDown}} method we are just resetting the {{XTestCase#testCaseDir}}, 
instead we should be removing the content of the directory then might set it to 
null. Same goes for the {{XFsTestCase#tearDown}}. Let me know what do you thing 
about this approach.

> TestDiscp leaves action.xml behind on local filesystem
> --
>
> Key: OOZIE-2493
> URL: https://issues.apache.org/jira/browse/OOZIE-2493
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: abhishek bafna
>Assignee: abhishek bafna
>  Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2493-02.patch, OOZIE-2493-03.patch, 
> OOZIE-2493.patch
>
>
> In the TestDistcpMain#testMain test case, it is deleting a file using HDFS 
> FileSystem instance which actually created on a local FileSystem.
> {code}
> // getting file hadoop system instance 
> FileSystem fs = getFileSystem();
> ...
> // creating a storing file on local file system
> File actionXml = new File(getTestCaseDir(), "action.xml");
> ...
> // Now trying to delete the file on hadoop file system
> fs.delete(new Path(getTestCaseDir(), "action.xml"), true);
> {code}



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

[jira] [Commented] (OOZIE-2493) TestDiscp leaves action.xml behind on local filesystem

[abhishek bafna (JIRA)]

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

abhishek bafna commented on OOZIE-2493:
---

[~rkanter] I looked into the classes inheriting from the {{MainTestCase}}. 
Except {{TestDistcpMain}}, all the others are writing into the {{action.xml}} 
just once, so they are not performing the {{delete}} operation on the file.

Essentially the problem is, after the testcase is completed, in the 
{{tearDown}} method we are just resetting the {{XTestCase#testCaseDir}}, 
instead we should be removing the content of the directory then might set it to 
null. Same goes for the {{XFsTestCase#tearDown}}. Let me know what do you thing 
about this approach.

> TestDiscp leaves action.xml behind on local filesystem
> --
>
> Key: OOZIE-2493
> URL: https://issues.apache.org/jira/browse/OOZIE-2493
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: abhishek bafna
>Assignee: abhishek bafna
>  Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2493-02.patch, OOZIE-2493-03.patch, 
> OOZIE-2493.patch
>
>
> In the TestDistcpMain#testMain test case, it is deleting a file using HDFS 
> FileSystem instance which actually created on a local FileSystem.
> {code}
> // getting file hadoop system instance 
> FileSystem fs = getFileSystem();
> ...
> // creating a storing file on local file system
> File actionXml = new File(getTestCaseDir(), "action.xml");
> ...
> // Now trying to delete the file on hadoop file system
> fs.delete(new Path(getTestCaseDir(), "action.xml"), true);
> {code}



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

[jira] [Commented] (OOZIE-2588) Support getting credentials for same cluster hcat when credentials config is empty

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2588:
--

Testing JIRA OOZIE-2588

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:red}-1{color} the patch contains 4 line(s) with trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{color:red}-1{color} the patch seems to introduce 2 new javac warning(s)
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Support getting credentials for same cluster hcat when credentials config is 
> empty
> --
>
> Key: OOZIE-2588
> URL: https://issues.apache.org/jira/browse/OOZIE-2588
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Attachments: OOZIE-2588-1.patch, OOZIE-2588-2.patch, 
> OOZIE-2588-3.patch, OOZIE-2588-4.patch, OOZIE-2588-5.patch, 
> OOZIE-2588-6.patch, OOZIE-2588-7.patch, OOZIE-2588-8.patch
>
>
> Oozie should get credentials for the same cluster hcat when 
> hcat.metastore.uri and hcat.metastore.principal are not specified. It will 
> eliminate lot of trouble for the users.



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

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

[Apache Jenkins Server]

See 

--
[...truncated 8322 lines...]
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-tools 
---
[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 2 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 (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro 

[jira] [Commented] (OOZIE-2625) Drop workflowgenerator

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2625:
--

Testing JIRA OOZIE-2625

Cleaning local git workspace



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



> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2625.001.patch, OOZIE-2625.002.patch
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

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

[Apache Jenkins Server]

See 

--
[...truncated 2453 lines...]
[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-tools 
---
[INFO] Compiling 2 source files to 

[WARNING] 
:[156,20]
 [deprecation] getConf() in Services has been deprecated
[WARNING] 
:[158,20]
 [deprecation] getConf() in Services has been deprecated
[WARNING] 
:[166,37]
 [deprecation] getConf() in Services has been deprecated
[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 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Compiling 6 source files to 

[WARNING] 
:[196,20]
 [deprecation] getConf() in Services has been deprecated
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oozie-mini ---
[INFO] Deleting 

[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] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie WorkflowGenerator 4.3.0-SNAPSHOT
[INFO] 
[WARNING] The POM for com.orange.links:gwt-links:jar:1.3-SNAPSHOT is missing, 
no dependency information available
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  0.893 s]
[INFO] Apache Oozie Hadoop Utils .. SUCCESS [  1.443 s]
[INFO] Apache Oozie Hadoop Distcp hadoop-1-4.3.0-SNAPSHOT . SUCCESS [  0.062 s]
[INFO] Apache Oozie Hadoop Auth hadoop-1-4.3.0-SNAPSHOT ... SUCCESS [  0.168 s]
[INFO] Apache Oozie Hadoop Libs ... SUCCESS [  0.022 s]
[INFO] Apache Oozie Client  SUCCESS [  5.473 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  2.655 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  3.045 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  1.160 s]
[INFO] Apache Oozie Core .. SUCCESS [ 25.693 s]
[INFO] Apache Oozie Share Lib Streaming ... SUCC

[jira] [Commented] (OOZIE-1402) Increase retry interval for non-progressing coordinator action with fix value

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1402:
--

Testing JIRA OOZIE-1402

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:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{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} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> Increase retry interval for non-progressing coordinator action with fix value
> -
>
> Key: OOZIE-1402
> URL: https://issues.apache.org/jira/browse/OOZIE-1402
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: trunk
>Reporter: Mona Chitnis
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Fix For: 4.3.0
>
> Attachments: OOZIE-1402-1.patch, OOZIE-1402-2.patch, 
> OOZIE-1402-3.patch, OOZIE-1402-amend-1.patch, OOZIE-1402-amend-2.patch
>
>
> Currently every coordinator action is retried to check data directory in the
> next minute. 
> We could make it better by waiting longer for coordinator action that is not
> progressing (i.e. find no new directory) for repeated retries
> The waiting time should start from 1 minute for X retries. Then the action
> should wait for 2 minutes. After X retries it should wait for 3. The same way
> it will go to some max-wait-time and stay there until timeout



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

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

[Apache Jenkins Server]

See 

--
[...truncated 8104 lines...]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-tools 
---
[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 2 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 (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INF

Re: [SCOPE] Oozie 4.3.0 Release

[Rohini Palaniswamy]

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.

If there is any jira, someone would like to include in 4.3.0 please update
the jira.

Regards,
Rohini

On Wed, Aug 3, 2016 at 11:44 AM, Rohini Palaniswamy  wrote:

> Unset the open ones without sending emails. Will update the resolved,
> closed and Patch Available ones sending emails.
>
> Regards,
> Rohini
>
> On Wed, Aug 3, 2016 at 11:36 AM, Robert Kanter 
> wrote:
>
>> Ya, let's unset those remaining open trunk ones.  I agree, we need to put
>> in some effort to clean out old JIRAs and to review Patch Available JIRAs.
>>
>> Also, I just created OOZIE-2625 to drop workflowgenerator.  We can discuss
>> the issue more there, but I listed a few reasons on OOZIE-2625 about why.
>>
>> - Robert
>>
>> On Wed, Aug 3, 2016 at 9:21 AM, Rohini Palaniswamy <
>> rohini.adi...@gmail.com>
>> wrote:
>>
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Oozie%20AND%20fixVersion%3D%20%22trunk%22%20and%20status%20%3D%20open%20ORDER%20BY%20resolution%20ASC%2C%20status%20DESC&startIndex=50
>> >
>> > These are jiras open and marked trunk. Should we unset fix version on
>> these
>> > or mark them for next release? Don't see majority of them being worked
>> on
>> > even for next release. We need to do bug scrub and close many of these
>> some
>> > time.
>> >
>> > > Instead
>> > of deleting "trunk", I think we're better off just renaming it to the
>> > release number.
>> >  There is some amount of relabeling either way. If we go with unsetting
>> fix
>> > version, then we can as well delete trunk. Also, I did create a 4.4.0
>> > yesterday to move some of the patch available jiras from 4.3.0.
>> >
>> >
>> > On Wed, Aug 3, 2016 at 8:59 AM, Rohini Palaniswamy <
>> > rohini.adi...@gmail.com>
>> > wrote:
>> >
>> > > I think it would be better to send out email for the bulk change. If
>> > there
>> > > are any issues or jiras wrongly marked someone can respond. We do that
>> > with
>> > > Pig and there are always couple of jiras that folks come back with
>> > feedback
>> > > on pulling back to release.
>> > >
>> > >
>> > > On Wed, Aug 3, 2016 at 8:07 AM, Robert Kanter 
>> > > wrote:
>> > >
>> > >> Abhishek, next time you do a bulk change, please remember to tell it
>> not
>> > >> to
>> > >> send out an email for every change :)
>> > >>
>> > >> On Tue, Aug 2, 2016 at 4:28 PM, Robert Kanter 
>> > >> wrote:
>> > >>
>> > >> > Rohini, that sounds good to me.  Especially because we're on
>> "master"
>> > >> > branch but "trunk" version in JIRA and it gets a little confusing.
>> > >> Instead
>> > >> > of deleting "trunk", I think we're better off just renaming it to
>> the
>> > >> > release number.  Otherwise, we'll have to re-label any current
>> "trunk"
>> > >> > fields.  We can use 4.4.0 for now, but I imagine that the next
>> release
>> > >> > might end up being 5.0.0 (with Oozie on Yarn); we can always
>> rename it
>> > >> > later.
>> > >> >
>> > >> > I'm not sure if there's a specific rule here, but I suppose we
>> should
>> > >> > probably have a vote in the private list to make things official as
>> > >> this is
>> > >> > a release-management-related change.  Can you send an email?
>> > >> >
>> > >> > Abhishek, thanks for putting this all together.  I think Rohini's
>> > >> > suggestion of updating the JIRAs is the right next step.  You're
>> > >> probably
>> > >> > best off using the bulk change feature instead of doing each JIRA
>> > >> > individually.  I should have time to do a bunch of reviews this
>> week,
>> > >> I've
>> > >> > actually already started.  I should have some time to continue
>> doing
>> > >> more
>> > >> > reviews.  As a general thing, we've been pretty slow about getting
>> > these
>> > >> > done :(
>> > >> >
>> > >> > - Robert
>> > >> >
>> > >> > On Tue, Aug 2, 2016 at 4:25 PM, Rohini Palaniswamy <
>> > >> > rohini.adi...@gmail.com> wrote:
>> > >> >
>> > >> >> I also did mark some of the enhancement jiras that Satish was
>> working
>> > >> on
>> > >> >> and which might take time to review to 4.4.0
>> > >> >>
>> > >> >> Regards,
>> > >> >> Rohini
>> > >> >>
>> > >> >> On Tue, Aug 2, 2016 at 3:01 PM, Rohini Palaniswamy <
>> > >> >> rohini.adi...@gmail.com>
>> > >> >> wrote:
>> > >> >>
>> > >> >> > Abhishek,
>> > >> >> > Can you mark all jiras already committed to trunk as 4.3.0
>> and
>> > >> those
>> > >> >> > planned in the scope document as 4.3.0? This will help filter on
>> > >> those
>> > >> >> > and review instead of referring to a google doc. I can pick up
>> > 10-15
>> > >> >> > jiras for review end of this week. We should try to get
>> maj

[jira] [Updated] (OOZIE-2342) Coordinator docs still mention old SLA system

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2342:
--
 Assignee: Satish Subhashrao Saley
Affects Version/s: (was: trunk)
Fix Version/s: 4.3.0

> Coordinator docs still mention old SLA system
> -
>
> Key: OOZIE-2342
> URL: https://issues.apache.org/jira/browse/OOZIE-2342
> Project: Oozie
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Robert Kanter
>Assignee: Satish Subhashrao Saley
> Fix For: 4.3.0
>
>
> The Coordinator docs page still mentions the old SLA system, which requires 
> the Yahoo! grid thing.  
> We should do one of the following:
> # Replace this with updated examples that use the new SLA system
> # Add a big note that this is deprecated and link to the newer SLA docs page
> # Remove the section; we already document the new SLA system elsewhere.
> http://oozie.apache.org/docs/4.2.0/CoordinatorFunctionalSpec.html#a12._SLA_Handling



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

[jira] [Updated] (OOZIE-2364) Remove deprecated SLAEventBean and related code

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2364:
--
 Assignee: Satish Subhashrao Saley
Fix Version/s: 4.3.0

> Remove deprecated SLAEventBean and related code
> ---
>
> Key: OOZIE-2364
> URL: https://issues.apache.org/jira/browse/OOZIE-2364
> Project: Oozie
>  Issue Type: Task
>Reporter: Rohini Palaniswamy
>Assignee: Satish Subhashrao Saley
>  Labels: newbie
> Fix For: 4.3.0
>
>
>   With new SLAService feature which uses different tables, the old SLA_EVENTS 
> table is not used anymore. Need to remove all code related to it and drop 
> that table as well.



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

[jira] [Commented] (OOZIE-2625) Drop workflowgenerator

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2625:
---

+1

> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2625.001.patch, OOZIE-2625.002.patch
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

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

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1396:
--
Fix Version/s: (was: trunk)

> 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
>
> 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] [Updated] (OOZIE-2087) Spark test fails on ubuntu

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2087:
--
Fix Version/s: (was: trunk)

> Spark test fails on ubuntu
> --
>
> Key: OOZIE-2087
> URL: https://issues.apache.org/jira/browse/OOZIE-2087
> Project: Oozie
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: pavan kumar kolamuri
>
> Currently, TestSparkMain runs org.apache.spark.examples.mllib.JavaALS. Looks 
> like this has dependency on libgfortran3 package and fails. Even in the 
> pre-commit builds, none of the spark tests run and the build fails 
> https://builds.apache.org/job/oozie-trunk-precommit-build/2120/consoleFull



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

[jira] [Updated] (OOZIE-1464) fix SQL statements in OozieDBCLI for upgrade

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1464:
--
Fix Version/s: (was: trunk)

> fix SQL statements in OozieDBCLI for upgrade 
> -
>
> Key: OOZIE-1464
> URL: https://issues.apache.org/jira/browse/OOZIE-1464
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ryota Egashira
>Assignee: Ryota Egashira
>
> - ddlQueries.add("UPDATE WF_ACTIONS SET error_message_temp=error_message");
> + ddlQueries.add("UPDATE WF_ACTIONS SET 
> error_message_temp=dbms_lob.substr(error_message,4000,1)");



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

[jira] [Comment Edited] (OOZIE-2569) Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley edited comment on OOZIE-2569 at 8/3/16 6:57 PM:


I think we would have it as false by default because with hadoop-2, tarballs 
are used for client side *-site.xmls.  Rohini's comment 
[here|https://issues.apache.org/jira/browse/OOZIE-2343?focusedCommentId=14717181&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14717181].


was (Author: satishsaley):
I think we need to have it as false by default because with hadoop-2, tarballs 
are used for client side *-site.xmls.  Rohini's comment 
[here|https://issues.apache.org/jira/browse/OOZIE-2343?focusedCommentId=14717181&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14717181].

> Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher 
> ---
>
> Key: OOZIE-2569
> URL: https://issues.apache.org/jira/browse/OOZIE-2569
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: abhishek bafna
>Assignee: abhishek bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2569-00.patch, OOZIE-2569-02.patch
>
>
> Oozie Spark action requires yarn-site, core-site, hdfs-site and mapred-site 
> to be present in the classpath for launching the spark applications. 
> Currently we manually copy these files into oozie spark sharelib.
> Until it is fixed through the spark, we can copy the 
> {{oozie.action.conf.xml}} file as yarn-site, core-site, hdfs-site and 
> mapred-site, which will avoid manual steps of copying those files.



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

[jira] [Updated] (OOZIE-2454) Oozie Doc has a wrongly named property called oozie.coord.workflow.notification.url

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2454:
--
Fix Version/s: (was: trunk)

> Oozie Doc has a wrongly named property called 
> oozie.coord.workflow.notification.url
> ---
>
> Key: OOZIE-2454
> URL: https://issues.apache.org/jira/browse/OOZIE-2454
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 4.1.0
>Reporter: Ferenc Denes
>Priority: Trivial
>  Labels: documentation, newbie
> Attachments: OOZIE-2454-1.patch
>
>
> The following doc for coordinator notification 
> https://oozie.apache.org/docs/4.1.0/CoordinatorFunctionalSpec.html#a15._Coordinator_Notifications
>  called oozie.coord.workflow.notification.url. It should be 
> oozie.coord.notification.url.



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

[jira] [Updated] (OOZIE-2451) Oozie mail action fails due to the Null pointer exception

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2451:
--
Fix Version/s: (was: trunk)

> Oozie mail action fails due to the Null pointer exception
> -
>
> Key: OOZIE-2451
> URL: https://issues.apache.org/jira/browse/OOZIE-2451
> Project: Oozie
>  Issue Type: Bug
>  Components: action, core, workflow
>Affects Versions: 4.1.0
> Environment: CDH 5.5.1
>Reporter: Ming Hsuan Tu
>
> The workflow is as follows
> {code:xml}
> 
>   
>   m...@example.com
>   ${app_name} in ${date} failed
>   The workflow ${wf:id()} had issues and was killed.
>   
>   
>   
>   
> {code}
> but the mail action just threw up the NULL pointer exception and no other 
> logs can be found.
> I have configured the smtp server correctly.
> This issues occurred when I upgrade to CDH 5.5.1 from CDH 5.4.6.
> Thank you. 



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

[jira] [Updated] (OOZIE-1810) Workflow cannot get into Failed state when kill control node cannot resolve variable in message

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1810:
--
Fix Version/s: (was: trunk)

> Workflow cannot get into Failed state when kill control node cannot resolve 
> variable in message 
> 
>
> Key: OOZIE-1810
> URL: https://issues.apache.org/jira/browse/OOZIE-1810
> Project: Oozie
>  Issue Type: Bug
>Reporter: Bing Jiang
>Assignee: Azrael Seoeun
> Attachments: OOZIE-1810.2.patch, OOZIE-1810.patch, OOZIE-1890.3.patch
>
>
> workflow.xml==
> 
> 
> 
> ${TryError} error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> There is no definition about ${TryError} in job.properties.
> Workflow job are stuck at RUNNING state, and it is always trying to resolve 
> the variable [TryError] in kill action's message.
> ==Exception from oozie log 
> ACTION[-*-oozie-wrkf-W@fail] XException, 
> org.apache.oozie.command.CommandException: E0729: Kill node message [fail]
>   at 
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:292)
>   at 
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:66)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:280)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:722)
> Caused by: javax.servlet.jsp.el.ELException: variable [TryError] cannot be 
> resolved
>   at 
> org.apache.oozie.util.ELEvaluator$Context.resolveVariable(ELEvaluator.java:106)
>   at org.apache.commons.el.NamedValue.evaluate(NamedValue.java:124)
>   at 
> org.apache.commons.el.ExpressionString.evaluate(ExpressionString.java:114)
>   at 
> org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:274)
>   at 
> org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:190)
>   at org.apache.oozie.util.ELEvaluator.evaluate(ELEvaluator.java:203)
>   at 
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:277)
>   ... 6 more
> ===
> when it runs into  the resolve error upon control nodes' message, oozie 
> action should enter into Failed state as soon as possible.



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

[jira] [Updated] (OOZIE-819) Interrupt map doesn't have unique set of commands for a given jobid

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-819:
-
Fix Version/s: (was: trunk)
   (was: 3.2.0)

> Interrupt map doesn't have unique set of commands for a given jobid
> ---
>
> Key: OOZIE-819
> URL: https://issues.apache.org/jira/browse/OOZIE-819
> Project: Oozie
>  Issue Type: Bug
>Reporter: Virag Kothari
>Assignee: Virag Kothari
>
> This jira proposes to fix the following issues
> 1) Interrupt map should have unique values of interrupt commands for a given 
> job id
> 2) Fix the usage of 'used' implementation in Xcommand
> 3) Remove white spaces for interrupt property in oozie-default. This is 
> similar to issue identified in oozie-797. 



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

[jira] [Updated] (OOZIE-2357) CoordRerun should queue CoordPushDependencyCheckXCommand if there is push dependencies

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2357:
--
Fix Version/s: (was: trunk)

> CoordRerun should queue CoordPushDependencyCheckXCommand if there is push 
> dependencies
> --
>
> Key: OOZIE-2357
> URL: https://issues.apache.org/jira/browse/OOZIE-2357
> Project: Oozie
>  Issue Type: Bug
>Reporter: Kailong Sheng
>Assignee: Kailong Sheng
> Attachments: OOZIE-2357.patch
>
>




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

[jira] [Updated] (OOZIE-1213) Missing version number for clover and findbugs plugins causes maven build WARNING

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1213:
--
Fix Version/s: (was: trunk)

> Missing version number for clover and findbugs plugins causes maven build 
> WARNING
> -
>
> Key: OOZIE-1213
> URL: https://issues.apache.org/jira/browse/OOZIE-1213
> Project: Oozie
>  Issue Type: Task
>Affects Versions: trunk
>Reporter: jun aoki
>Priority: Minor
>  Labels: newbie
> Attachments: OOZIE-1213.patch-0
>
>
> {code}
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.oozie.test:oozie-mini:jar:3.4.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for 
> com.atlassian.maven.plugins:maven-clover2-plugin is missing. @ 
> org.apache.oozie:oozie-main:3.4.0-SNAPSHOT, 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/pom.xml, 
> line 742, column 21
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.mojo:findbugs-maven-plugin is missing. @ 
> org.apache.oozie:oozie-main:3.4.0-SNAPSHOT, 
> /home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/pom.xml, 
> line 751, column 21
> [WARNING] 
> {code}
> can be found in the precommit build log
> e.g. https://builds.apache.org/job/oozie-trunk-precommit-build/319/consoleFull
> The main pom should define a version for the both plugins.



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

[jira] [Updated] (OOZIE-2220) lib/* and extra_lib/* should be included in oozie-setup.ps1 and ooziedb.cmd classpath

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2220:
--
Fix Version/s: (was: trunk)

> lib/* and extra_lib/* should be included in oozie-setup.ps1 and ooziedb.cmd 
> classpath
> -
>
> Key: OOZIE-2220
> URL: https://issues.apache.org/jira/browse/OOZIE-2220
> Project: Oozie
>  Issue Type: Bug
>Reporter: Bowen Zhang
>




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

[jira] [Updated] (OOZIE-2099) Add test-patch support for patches generated without --no-prefix

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2099:
--
Fix Version/s: (was: trunk)

> Add test-patch support for patches generated without --no-prefix
> 
>
> Key: OOZIE-2099
> URL: https://issues.apache.org/jira/browse/OOZIE-2099
> Project: Oozie
>  Issue Type: Bug
>  Components: tools
>Reporter: Suresh Srinivas
>Assignee: Suresh Srinivas
> Attachments: OOZIE-2099.patch, OOZIE-2099.v2.patch
>
>




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

[jira] [Updated] (OOZIE-1551) Change hadoop-2 profile to use 2.2.0

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1551:
--
Fix Version/s: (was: trunk)
   4.1.0

> Change hadoop-2 profile to use 2.2.0
> 
>
> Key: OOZIE-1551
> URL: https://issues.apache.org/jira/browse/OOZIE-1551
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: trunk, 4.0.1
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1551.patch, OOZIE-1551.patch, OOZIE-1551.patch, 
> OOZIE-1551.patch, OOZIE-1551_branch-4.patch, sharedlib_pig_pom_exclusion.patch
>
>
> We should change the hadoop-2 profile to use 2.2.0 (GA) instead of 
> 2.2.0-SNAPSHOT now that its been released.



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

[jira] [Commented] (OOZIE-2569) Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-2569:


I think we need to have it as false by default because with hadoop-2, tarballs 
are used for client side *-site.xmls.  Rohini's comment 
[here|https://issues.apache.org/jira/browse/OOZIE-2343?focusedCommentId=14717181&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14717181].

> Adding yarn-site, core-site, hdfs-site and mapred-site into spark launcher 
> ---
>
> Key: OOZIE-2569
> URL: https://issues.apache.org/jira/browse/OOZIE-2569
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: abhishek bafna
>Assignee: abhishek bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2569-00.patch, OOZIE-2569-02.patch
>
>
> Oozie Spark action requires yarn-site, core-site, hdfs-site and mapred-site 
> to be present in the classpath for launching the spark applications. 
> Currently we manually copy these files into oozie spark sharelib.
> Until it is fixed through the spark, we can copy the 
> {{oozie.action.conf.xml}} file as yarn-site, core-site, hdfs-site and 
> mapred-site, which will avoid manual steps of copying those files.



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

[jira] [Updated] (OOZIE-2236) Need to package hive-hcatalog-server-extensions.jar in the hcatalog sharelib

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2236:
--
Fix Version/s: (was: trunk)

> Need to package hive-hcatalog-server-extensions.jar in the hcatalog sharelib
> 
>
> Key: OOZIE-2236
> URL: https://issues.apache.org/jira/browse/OOZIE-2236
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: OOZIE-2236.patch
>
>
> We used to package hive-hcatalog-server-extensions-.jar with 
> hcatalog sharelib which is depended on by upstream projects like Falcon.   We 
> have to add it back as it became unavailable after the latest POM changes



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

[jira] [Updated] (OOZIE-1514) Rerunning a coordinator with no input dependencies puts actions in WAITING instead of READY and proceeding

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1514:
--
Fix Version/s: (was: trunk)

> Rerunning a coordinator with no input dependencies puts actions in WAITING 
> instead of READY and proceeding
> --
>
> Key: OOZIE-1514
> URL: https://issues.apache.org/jira/browse/OOZIE-1514
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.0
>Reporter: Mona Chitnis
>Assignee: Bowen Zhang
>Priority: Blocker
> Fix For: 4.0.0
>
> Attachments: oozie-1514.patch, oozie-1514.patch
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Following issue reported by Bowen:
>  
> {quote}
> rerun oozie coordinator action that has no data dependency will make the 
> action stuck in "WAITING" forever.
> The issue has to do with the change introduced in 
> coordActionInputCheckXCommand. The rerun action will fail this if statement:
> if (!nonExistListStr.equals(missingDeps))
> since nonExistListStr and missingDeps are both empty strings. Once it fails 
> the if statement, isChangeDependency is still
> set to false and the status change to "READY" will not be persisted since we 
> will call CoordActionUpdateForModifiedTimeJPAExecutor instead of 
> CoordActionUpdateForInputCheckJPAExecutor in the updateCoordAction method.
> the Action is in "WAITING" stage forever.
> {quote}



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

[jira] [Updated] (OOZIE-1565) OOZIE-1481 should only affect v2 of the API, not v1

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1565:
--
Fix Version/s: (was: trunk)
   4.1.0

> OOZIE-1481 should only affect v2 of the API, not v1
> ---
>
> Key: OOZIE-1565
> URL: https://issues.apache.org/jira/browse/OOZIE-1565
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: trunk, 4.0.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1565.patch
>
>
> OOZIE-1481 changed the behavior of the v1 API such that when getting coord 
> info, specifying {{len=0}} now returns 0 actions instead of all actions.  
> Also, on the REST call, not specifying any {{len}} parameter is interpreted 
> by the Oozie server as {{len=0}}.  
> This is a logically backwards incompatible change.  We should keep this 
> change in the v2 API, but change the v1 API back to the original (incorrect) 
> behavior.  



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

[jira] [Updated] (OOZIE-1630) operations fail when path doesn't have scheme

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1630:
--
Fix Version/s: (was: trunk)
   4.1.0

>  operations fail when path doesn't have scheme
> ---
>
> Key: OOZIE-1630
> URL: https://issues.apache.org/jira/browse/OOZIE-1630
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ryota Egashira
>Assignee: Ryota Egashira
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1630-v3.patch
>
>
> hitting exception "Scheme not present in uri 
> /user//test_hbase_workflow/output" when doing something like  ="/user//test_hbase_workflow/output"/>.  it should default to hdfs when 
> no scheme specified considering typical use case, also use default namenode 
> if not specified. 



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

[jira] [Updated] (OOZIE-1542) When extjs isn't installed, the web UI is unhelpfully blank

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1542:
--
Fix Version/s: (was: trunk)
   4.1.0

> When extjs isn't installed, the web UI is unhelpfully blank
> ---
>
> Key: OOZIE-1542
> URL: https://issues.apache.org/jira/browse/OOZIE-1542
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk, 4.0.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Minor
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1542.patch, OOZIE-1542.patch
>
>
> When extjs isn't installed, the web UI page is currently unhelpfully blank 
> (it has the oozie logo and docs link).  In the past (when it used to be an 
> html page instead of a jsp page) it had some text to let the user know that 
> they have to install extjs to see the UI.  
> It would be good to put back the same or similar text; otherwise, users may 
> be confused why they can't see the UI if they forget to install extjs.



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

[jira] [Updated] (OOZIE-1626) pig action pop-up is not working properly in UI

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1626:
--
Fix Version/s: (was: trunk)
   4.1.0

> pig action pop-up is not working properly in UI
> ---
>
> Key: OOZIE-1626
> URL: https://issues.apache.org/jira/browse/OOZIE-1626
> Project: Oozie
>  Issue Type: Bug
>Reporter: Ryota Egashira
>Assignee: Purshotam Shah
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1626-v1.patch, OOZIE-1626-v2.patch, 
> OOZIE-1626-v3.patch, OOZIE-1626.patch, OOZIE-1626.patch
>
>
> pop-up doesn't show up when pig job failed and externalChildIDs is "null" (as 
> string)



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

[jira] [Updated] (OOZIE-1582) Bump up Tomcat version to 6.0.37

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1582:
--
Fix Version/s: (was: trunk)
   4.1.0

> Bump up Tomcat version to 6.0.37
> 
>
> Key: OOZIE-1582
> URL: https://issues.apache.org/jira/browse/OOZIE-1582
> Project: Oozie
>  Issue Type: Bug
>  Components: security
>Affects Versions: trunk, 4.0.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1582.patch
>
>
> Tomcat 6.0.37 fixes two security issues 
> (http://tomcat.apache.org/security-6.html).  We should upgrade from 6.0.36 to 
> incorporate them.



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

[jira] [Updated] (OOZIE-2410) Fork collections-generic

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2410:
--
Fix Version/s: (was: trunk)

> Fork collections-generic
> 
>
> Key: OOZIE-2410
> URL: https://issues.apache.org/jira/browse/OOZIE-2410
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Critical
> Attachments: OOZIE-2410.001.patch, security-fixes.patch
>
>
> The Jung library used by the {{GraphGenerator}} code is using an old fork of 
> Commons-Collections which added generics.  There was recently a security bug 
> in Commons-Collections (COLLECTIONS-580).  The fork we're using hasn't been 
> updated since 2010 and is dead, so it won't get the security fix 
> (Commons-Collections 3.2.2 or 4.1).  While Oozie isn't currently vulnerable 
> to an attack due to this, it would be good to patch this just to be safe.  
> Unfortunately, the best way to fix this is to fork the fork, which isn't 
> super great.  Anyway, we can make a new "oozie-collections-generic" module 
> with the collections-generic code + the security fixes applied.
> In the long run, we should implement OOZIE-2406, which will completely 
> rewrite the {{GraphGenerator}} (there's a number of other downsides with the 
> current implementation listed there), at which time we can remove this new 
> module.



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

[jira] [Updated] (OOZIE-1563) colt jar includes GPL licence

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1563:
--
Fix Version/s: (was: trunk)
   4.1.0

> colt jar includes GPL licence
> -
>
> Key: OOZIE-1563
> URL: https://issues.apache.org/jira/browse/OOZIE-1563
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk, 4.0.1
>Reporter: Bowen Zhang
>Assignee: Robert Kanter
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1563.patch
>
>
> I believe the colt jar is introduced in the SLA feature. The "Hep" class 
> inside the jar has GPL licence which restricts the usage and distribution of 
> oozie. 



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

[jira] [Updated] (OOZIE-1670) Workflow kill command doesn't kill child job for map-reduce action.

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1670:
--
Fix Version/s: (was: trunk)
   4.1.0

> Workflow kill command doesn't kill child job for map-reduce action.
> ---
>
> Key: OOZIE-1670
> URL: https://issues.apache.org/jira/browse/OOZIE-1670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Critical
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1670.patch
>
>




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

[jira] [Updated] (OOZIE-1284) oozie.service.SchemaService.wf.ext.schemas in oozie-site is missing some newer xsd files

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1284:
--
Fix Version/s: (was: trunk)
   4.1.0

> oozie.service.SchemaService.wf.ext.schemas in oozie-site is missing some 
> newer xsd files
> 
>
> Key: OOZIE-1284
> URL: https://issues.apache.org/jira/browse/OOZIE-1284
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1284.patch
>
>
> In oozie-site.xml, we have the following listed under 
> {{oozie.service.SchemaService.wf.ext.schemas}}:
> {noformat}
> shell-action-0.1.xsd
> shell-action-0.2.xsd
> email-action-0.1.xsd
> hive-action-0.2.xsd
> hive-action-0.3.xsd
> sqoop-action-0.2.xsd
> sqoop-action-0.3.xsd
> ssh-action-0.1.xsd
> distcp-action-0.1.xsd
> {noformat}
> It's missing the following xsd files:
> {noformat}
> distcp-action-0.2.xsd
> hive-action-0.4.xsd
> shell-action-0.3.xsd
> sqoop-action-0.4.xsd
> {noformat}
> If I recall correctly, this will cause Oozie to reject workflows using those 
> versions of those extension action schemas.  



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

[jira] [Updated] (OOZIE-1484) Error in DB upgrade when error message exceeds 4K characters

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1484:
--
Fix Version/s: (was: trunk)

> Error in DB upgrade when error message exceeds 4K characters
> 
>
> Key: OOZIE-1484
> URL: https://issues.apache.org/jira/browse/OOZIE-1484
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk, 4.0.0
>Reporter: Ryota Egashira
>Assignee: Ryota Egashira
> Fix For: 4.0.0
>
> Attachments: OOZIE-1484-v2.patch, OOZIE-1484.patch
>
>




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

[jira] [Updated] (OOZIE-1872) TestCoordActionInputCheckXCommand.testActionInputCheckLatestActionCreationTime is failing for past couple of builds

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1872:
--
Fix Version/s: (was: trunk)

> TestCoordActionInputCheckXCommand.testActionInputCheckLatestActionCreationTime
>  is failing for past couple of builds
> ---
>
> Key: OOZIE-1872
> URL: https://issues.apache.org/jira/browse/OOZIE-1872
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Affects Versions: trunk, 4.1.0
>Reporter: Rohini Palaniswamy
>Assignee: Mona Chitnis
> Fix For: 4.1.0
>
> Attachments: OOZIE-1872-1.patch
>
>
> https://builds.apache.org/job/oozie-trunk-precommit-build/1291/testReport/junit/org.apache.oozie.command.coord/TestCoordActionInputCheckXCommand/testActionInputCheckLatestActionCreationTime/



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

[jira] [Updated] (OOZIE-2625) Drop workflowgenerator

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-2625:
-
Attachment: OOZIE-2625.002.patch

Somehow I did my grepping wrong and missed those.  Here's an updated 002 patch.

> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2625.001.patch, OOZIE-2625.002.patch
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

[jira] [Updated] (OOZIE-1756) hadoop-auth version is wrong if profile isn't selected

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1756:
--
Fix Version/s: (was: trunk)
   4.1.0

> hadoop-auth version is wrong if profile isn't selected
> --
>
> Key: OOZIE-1756
> URL: https://issues.apache.org/jira/browse/OOZIE-1756
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: trunk, 4.0.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1756.patch, OOZIE-1756.patch
>
>
> In the hadooplibs for the non-sepecified version of hadoop (e.g. if you build 
> with no profile (i.e. Hadoop 1) and look at the hadoop-2 sharelib), it will 
> have the wrong version of the hadoop-auth jar.



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

[jira] [Updated] (OOZIE-1736) Switch to Hadoop 2.3.0 for the hadoop-2 profile

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1736:
--
Fix Version/s: (was: trunk)
   4.1.0

> Switch to Hadoop 2.3.0 for the hadoop-2 profile
> ---
>
> Key: OOZIE-1736
> URL: https://issues.apache.org/jira/browse/OOZIE-1736
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk, 4.0.1
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1736.patch, OOZIE-1736_branch-4.0.patch
>
>
> We should update the "hadoop-2" profile to use Hadoop 2.3.0 instead of 2.2.0. 
>  Y! has done some QE runs on it and I also just tried all of the unit tests.



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

[jira] [Updated] (OOZIE-1573) coord:tzOffset() gives incorrect offset for daylight saving timezones

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1573:
--
Fix Version/s: (was: trunk)
   4.1.0

> coord:tzOffset() gives incorrect offset for daylight saving timezones
> -
>
> Key: OOZIE-1573
> URL: https://issues.apache.org/jira/browse/OOZIE-1573
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Rohini Palaniswamy
> Fix For: 4.1.0, 4.0.1
>
> Attachments: OOZIE-1573-1.patch, OOZIE-1573-1.patch
>
>
> Case 1:
> Daily job run through oozie bundle
> Coordinator time Zone: UTC
> Dataset timezone: America/New_York
> Start Time: 2013-10-13T00:00Z
> End Time: 2013-10-14T00:00Z
> Return from tzOffset() function: 4 hrs (which is correct)
> Case 2:
> Daily job run through oozie bundle
> Coordinator time Zone: UTC
> Dataset timezone: America/New_York
> Start Time: 2012-11-13T00:00Z
> End Time: 2012-11-14T00:00Z
> Return from tzOffset() function: 4 hrs (which is not correct as difference 
> between GMT and America/New_York timezone should be 5 hrs).



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

[jira] [Updated] (OOZIE-1376) Extending Oozie ACLs like admin groups and proxy users to support both groups and users

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1376:
--
Fix Version/s: (was: trunk)
   4.4.0

> Extending Oozie ACLs like admin groups and proxy users to support both groups 
> and users
> ---
>
> Key: OOZIE-1376
> URL: https://issues.apache.org/jira/browse/OOZIE-1376
> Project: Oozie
>  Issue Type: Improvement
>  Components: security
>Affects Versions: trunk
>Reporter: Kai Zheng
>Assignee: Kai Zheng
>  Labels: Security
> Fix For: 4.4.0
>
> Attachments: OOZIE-1376.patch
>
>
> Currently Oozie relevant ACLs supports only users in some case or only groups 
> in other case, which is not consistent with other components like Hadoop, 
> HBase and Hive. Supporting both users and groups in ACLs can simplify the 
> admin configuration work, and also help implement more advanced access 
> control such as RBAC based on the ACLs scheme. For example RBAC can simply 
> translate role privilege into corresponding ACLs with the users and groups 
> assigned to the role.



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

[jira] [Updated] (OOZIE-1369) OozieDBCLI code should not hardcode the Oozie table filenames

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1369:
--
Fix Version/s: (was: trunk)
   4.4.0

> OozieDBCLI code should not hardcode the Oozie table filenames
> -
>
> Key: OOZIE-1369
> URL: https://issues.apache.org/jira/browse/OOZIE-1369
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Mona Chitnis
> Fix For: 4.4.0
>
> Attachments: OOZIE-1369-2.patch, OOZIE-1369.patch
>
>
> The code in OozieDBCLI reads from the persistence.xml file to know the code 
> files declaring all the tables and schemas. The method 
> createMappingToolArguments() then should not duplicate and hardcode those 
> filenames again. persistence.xml should be the singular place to specify 
> openjpa tables and schema to avoid having to track 2 places



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

[jira] [Updated] (OOZIE-2081) WorkflowJob notification to include coordinator action id

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2081:
--
Fix Version/s: (was: 4.0.1)
   (was: 4.1.0)
   (was: trunk)
   4.4.0

> WorkflowJob notification to include coordinator action id 
> --
>
> Key: OOZIE-2081
> URL: https://issues.apache.org/jira/browse/OOZIE-2081
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Reporter: Venkatesan Ramachandran
>Assignee: Azrael Seoeun
> Fix For: 4.4.0
>
> Attachments: OOZIE-2081.1.patch, OOZIE-2081.2.patch
>
>
> WorkflowJob notification to include parent_id (coordinator action id) if 
> present. This will help identify if a given workflow job is started by a 
> coordinator action.



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

[jira] [Updated] (OOZIE-1636) OOZIE_SYS table engine should be innodb

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1636:
--
Fix Version/s: (was: 4.1.0)
   (was: trunk)
   4.4.0

> OOZIE_SYS table engine should be innodb
> ---
>
> Key: OOZIE-1636
> URL: https://issues.apache.org/jira/browse/OOZIE-1636
> Project: Oozie
>  Issue Type: Improvement
>  Components: tools
>Affects Versions: trunk, 4.1.0
>Reporter: Jayesh
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: OOZIE-1636.patch
>
>
> All oozie table are created with engine set to innodb explicitly but 
> OOZIE_SYS table does not have engine specified which defaults to whatever 
> mysql default engine is, which could be myisam sometimes.
> This could be easily missed and create problem while taking database backup.
> so this ticket is for specifying engine innodb for OOZIE_SYS explicitly while 
> creating oozie.sql



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

[jira] [Updated] (OOZIE-2589) CompletedActionXCommand priority param is of no effect

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2589:
--
Fix Version/s: (was: trunk)
   4.4.0

> CompletedActionXCommand priority param is of no effect
> --
>
> Key: OOZIE-2589
> URL: https://issues.apache.org/jira/browse/OOZIE-2589
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk
>Reporter: Linflytang
>  Labels: patch
> Fix For: 4.4.0
>
> Attachments: 0001-Fixed-CompletedActionXCommand-priority-param.patch
>
>
> CompletedActionXCommand priority param is hard coding with 1, but create the 
> action with 2 (HIGH_PRIORITY).
> patch:https://github.com/apache/oozie/pull/20/files



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

[jira] [Updated] (OOZIE-1232) GroupsService should be able to reference Hadoop configurations in Hadoop configuration folder (such as /etc/hadoop/conf)

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1232:
--
Fix Version/s: (was: trunk)
   4.4.0

> GroupsService should be able to reference Hadoop configurations in Hadoop 
> configuration folder (such as /etc/hadoop/conf)
> -
>
> Key: OOZIE-1232
> URL: https://issues.apache.org/jira/browse/OOZIE-1232
> Project: Oozie
>  Issue Type: Improvement
>  Components: security
>Affects Versions: trunk
>Reporter: Kai Zheng
>Assignee: Kai Zheng
>  Labels: GroupsService, hadoop-conf
> Fix For: 4.4.0
>
> Attachments: OOZIE-1232-v2.patch, OOZIE-1232.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Oozie GroupsService wraps Hadoop user groups mapping to get groups for user, 
> which requires to reference Hadoop configurations, especially the properties 
> related to groups mapping provider (such as LdapGroupsMapping).
> To avoid replication of such configurations into oozie-site.xml, mechanism is 
> needed to configure the Hadoop configurations folder (often mentioned 
> hadoop-conf) for the service, as HadoopAccessorService currently does.
> Such work can be done per Service, as HadoopAccessorService, but would it be 
> better to avoid code changes or similar work when other Service also needs to 
> do that in future.



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

[jira] [Updated] (OOZIE-1599) Cache the list of available timezones from the admin servlet

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1599:
--
Fix Version/s: (was: trunk)
   4.4.0

> Cache the list of available timezones from the admin servlet
> 
>
> Key: OOZIE-1599
> URL: https://issues.apache.org/jira/browse/OOZIE-1599
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Sreepathi Prasanna
>  Labels: newbie
> Fix For: 4.4.0
>
> Attachments: OOZIE-1599.patch.1
>
>
> The admin servlet has a call that returns a list of available timezones.  On 
> startup, it prepares a list of GMT offsets (e.g. "GMT-12:00", "GMT-11:00", 
> etc), which is only generated once.  But the rest of the timezones (e.g. 
> "America/Los_Angeles", etc) are processed from {{TimeZone}} every time the 
> admin servlet is asked for the list.  
> We should refactor this to generate/process the entire list either the first 
> time its called or at startup and then simply return the {{JSONArray}} when 
> the admin servlet is asked for the list.  



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

[jira] [Updated] (OOZIE-2618) Include hive-common in hive-beeline as compile component for hive-server2 (hive2 action)

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2618:
--
Fix Version/s: (was: trunk)
   4.4.0

> Include hive-common in hive-beeline as compile component for hive-server2 
> (hive2 action)
> 
>
> Key: OOZIE-2618
> URL: https://issues.apache.org/jira/browse/OOZIE-2618
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: trunk
>Reporter: Taklon Stephen Wu
>  Labels: maven, patch
> Fix For: 4.4.0
>
> Attachments: OOZIE-2618-1.patch
>
>
> OOZIE-1876 has excluded hive-common in hive-beeline and isn’t compatible with 
> hive version which is higher than 0.13.1. This change adds hive-common as 
> part of the dependency for hive-beeline and submodules of it can be used 
> beeline correctly.



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

[jira] [Updated] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1860:
--
Fix Version/s: (was: trunk)
   4.4.0

> Oozie job mapper launch fails due to null value returned from action file
> -
>
> Key: OOZIE-1860
> URL: https://issues.apache.org/jira/browse/OOZIE-1860
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Osadchiy Artem
> Fix For: 4.4.0
>
> Attachments: OOZIE-1860.patch, action.log, oozie.log
>
>
> Certain oozie workflows fail at launch mapper stage when the id retrieved 
> from the recovery action file returns a null value.
> Logs attached below



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

[jira] [Updated] (OOZIE-1676) Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1676:
--
Fix Version/s: (was: trunk)
   4.4.0

> Instrumentation and Configuration over the REST API and Web UI should include 
> all Oozie servers
> ---
>
> Key: OOZIE-1676
> URL: https://issues.apache.org/jira/browse/OOZIE-1676
> Project: Oozie
>  Issue Type: Improvement
>  Components: HA
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: OOZIE-1676.patch, OOZIE-1676.patch, OOZIE-1676.patch, 
> OOZIE-1676.patch, screenshot.jpg, screenshot2.jpg
>
>
> This isn't that important, but it would be good if we updated the REST API 
> and Web UI to return the instrumentation and configuration for each Oozie 
> server when HA is being used.  As it stands, each time you refresh the page 
> (and are going through the load balancer), you'll get the 
> instrumentation/configuration for a different server, which are not identical 
> and there isn't really a way to tell which server they came from.  This 
> should be a new version of the REST API (v3) because it would change the 
> return format to be an array of servers with their 
> instrumentation/configuration info.  
> The backend of this would have the contacted Oozie server simply ask each of 
> the other Oozie servers for their instrumentation or configuration and 
> combine them all (with the name of each server) into the response.



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

[jira] [Updated] (OOZIE-1579) Add basic HTTP auth to Oozie CLI

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1579:
--
Fix Version/s: (was: trunk)
   4.4.0

> Add basic HTTP auth to Oozie CLI
> 
>
> Key: OOZIE-1579
> URL: https://issues.apache.org/jira/browse/OOZIE-1579
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Reporter: David Wannemacher
>Assignee: David Wannemacher
> Fix For: 4.4.0
>
> Attachments: OOZIE-1579.trunk.2.patch, OOZIE-1579.trunk.patch
>
>
> This proposed change adds Basic HTTP Auth functionality to the Oozie CLI. 
> This would never be used in a usual Oozie installation because Oozie servers 
> support token-based authentication: Pseudo/Simple Auth and Kerberos.
> Basic HTTP Auth is needed in the Oozie CLI for when the Oozie service is 
> placed behind a gateway that uses Basic HTTP Auth over SSL. It is assumed 
> that the Oozie service is running with authorization turned off, because the 
> gateway is handling authorization. Once the user authenticates himself to the 
> gateway, the request is forwarded through the gateway to the oozie service.
> This had to be implemented outside of the custom authentication framework 
> provided by Oozie because basic auth requires adding a request property to 
> each connection created. It's completely possible that there is a cleaner way 
> of implementing this, if so please let me know!
> Two additions were implemented in the CLI:
> * Indication to use Basic Auth. This is done by specifying BASIC as the 
> argument to the -auth argument.
> * Configuration of Basic Auth.
> ** Introduction of -username and -password command line arguments.
> ** If the auth mode is BASIC, only -username is provided, and the 
> OOZIEPASSWORD environment variable is set, the OOZIEPASSWORD environment 
> variable will be used for the password.
> ** If mode is BASIC and only -username is provided, and OOZIEPASSWORD is 
> undefined, the user will be prompted for the password, and the shell 
> facilities for masking input will be used.



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

[jira] [Updated] (OOZIE-1779) Add parent-id as a filter option

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1779:
--
Fix Version/s: (was: trunk)
   4.4.0

> Add parent-id as a filter option
> 
>
> Key: OOZIE-1779
> URL: https://issues.apache.org/jira/browse/OOZIE-1779
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Mona Chitnis
>Assignee: Azrael Seoeun
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: OOZIE-1779.1.patch, OOZIE-1779.2.patch
>
>
> Currently filtering options on jobs list are
> name, user, group, status, frequency and time-unit. 
> With increasing usage of coordinators and bundles, adding parent-id should be 
> useful instead of always searching top-down from parent to child.



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

[jira] [Updated] (OOZIE-2427) With Kerberos enabled, the authentication failure for the javascript resources under /ext-2.2

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-2427:
--
Fix Version/s: (was: trunk)
   4.4.0

> With Kerberos enabled, the authentication failure for the javascript 
> resources under /ext-2.2 
> --
>
> Key: OOZIE-2427
> URL: https://issues.apache.org/jira/browse/OOZIE-2427
> Project: Oozie
>  Issue Type: Bug
>  Components: security
>Affects Versions: 4.2.0
>Reporter: Gao Zhong Liang
> Fix For: 4.4.0
>
> Attachments: OOZIE-2427.patch
>
>
> With the kerberos authentication enabled, failed to load Oozie console due to 
> the authentication failure of the javascript resource under /ext-2.2. Go back 
> the Oozie log, the following error messages found:
> 21 05:50:42,771 DEBUG AuthenticationFilter:529 - SERVER[**] Request 
> [http://**:11000/oozie/ext-2.2/examples/grid/RowExpander.js?doAs=sam] user 
> [knox] authenticated
> 2015-12-21 05:50:42,772 DEBUG AuthenticationFilter:517 - SERVER[**] Request 
> [http://**:11000/oozie/ext-2.2/examples/grid/RowExpander.js?doAs=sam] 
> triggering authentication
> 2015-12-21 05:50:42,772 DEBUG AuthenticationFilter:517 - SERVER[**] Request 
> [http://**:11000/oozie/ext-2.2/examples/grid/RowExpander.js?doAs=sam] 
> triggering authentication
> 2015-12-21 05:50:42,774 DEBUG AuthenticationFilter:564 - SERVER[**] 
> Authentication exception: GSSException: Failure unspecified at GSS-API level 
> (Mechanism level: Request is a replay (34))
> org.apache.hadoop.security.authentication.client.AuthenticationException: 
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Request 
> is a replay (34))
> at 
> org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler.authenticate(KerberosAuthenticationHandler.java:398)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:519)
>   
> Based on the analysis, the issue should related to is related to the jira  
> HADOOP-8830: 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter might 
> be called twice, causing kerberos replay errors
> https://issues.apache.org/jira/browse/HADOOP-8830
> 1. Current oozie leverages Hadoop for the authentication.
> 2. Based on the resouce difference, it defines the filter for the  
> authentication, but for some resources such as some js under ext-2.2, they 
> are always authenticated twice, the reason is beacuse oozie has the following 
> filter definition:
>  
> 
> authenticationfilter
> *.js
> 
> 
> authenticationfilter
> /ext-2.2/*
> 
> With the issue in HADOOP-8830, the final authentication is failure, so we 
> finally get the error 403 in browser(which directly causes the console 
> disabled).
>  
> 3. For 2),  it just hit the issue in Jira HADOOP-8830, if the oozie's debug 
> mode is enabled, logs clearly show that. 



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

[jira] [Commented] (OOZIE-2625) Drop workflowgenerator

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2625:
---

There are references in some other files
distro/pom.xml 
src/main/assemblies/distro.xml
distro/src/main/bin/oozie-setup.sh

> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2625.001.patch
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

Re: [SCOPE] Oozie 4.3.0 Release

[Rohini Palaniswamy]

Unset the open ones without sending emails. Will update the resolved,
closed and Patch Available ones sending emails.

Regards,
Rohini

On Wed, Aug 3, 2016 at 11:36 AM, Robert Kanter  wrote:

> Ya, let's unset those remaining open trunk ones.  I agree, we need to put
> in some effort to clean out old JIRAs and to review Patch Available JIRAs.
>
> Also, I just created OOZIE-2625 to drop workflowgenerator.  We can discuss
> the issue more there, but I listed a few reasons on OOZIE-2625 about why.
>
> - Robert
>
> On Wed, Aug 3, 2016 at 9:21 AM, Rohini Palaniswamy <
> rohini.adi...@gmail.com>
> wrote:
>
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Oozie%20AND%20fixVersion%3D%20%22trunk%22%20and%20status%20%3D%20open%20ORDER%20BY%20resolution%20ASC%2C%20status%20DESC&startIndex=50
> >
> > These are jiras open and marked trunk. Should we unset fix version on
> these
> > or mark them for next release? Don't see majority of them being worked on
> > even for next release. We need to do bug scrub and close many of these
> some
> > time.
> >
> > > Instead
> > of deleting "trunk", I think we're better off just renaming it to the
> > release number.
> >  There is some amount of relabeling either way. If we go with unsetting
> fix
> > version, then we can as well delete trunk. Also, I did create a 4.4.0
> > yesterday to move some of the patch available jiras from 4.3.0.
> >
> >
> > On Wed, Aug 3, 2016 at 8:59 AM, Rohini Palaniswamy <
> > rohini.adi...@gmail.com>
> > wrote:
> >
> > > I think it would be better to send out email for the bulk change. If
> > there
> > > are any issues or jiras wrongly marked someone can respond. We do that
> > with
> > > Pig and there are always couple of jiras that folks come back with
> > feedback
> > > on pulling back to release.
> > >
> > >
> > > On Wed, Aug 3, 2016 at 8:07 AM, Robert Kanter 
> > > wrote:
> > >
> > >> Abhishek, next time you do a bulk change, please remember to tell it
> not
> > >> to
> > >> send out an email for every change :)
> > >>
> > >> On Tue, Aug 2, 2016 at 4:28 PM, Robert Kanter 
> > >> wrote:
> > >>
> > >> > Rohini, that sounds good to me.  Especially because we're on
> "master"
> > >> > branch but "trunk" version in JIRA and it gets a little confusing.
> > >> Instead
> > >> > of deleting "trunk", I think we're better off just renaming it to
> the
> > >> > release number.  Otherwise, we'll have to re-label any current
> "trunk"
> > >> > fields.  We can use 4.4.0 for now, but I imagine that the next
> release
> > >> > might end up being 5.0.0 (with Oozie on Yarn); we can always rename
> it
> > >> > later.
> > >> >
> > >> > I'm not sure if there's a specific rule here, but I suppose we
> should
> > >> > probably have a vote in the private list to make things official as
> > >> this is
> > >> > a release-management-related change.  Can you send an email?
> > >> >
> > >> > Abhishek, thanks for putting this all together.  I think Rohini's
> > >> > suggestion of updating the JIRAs is the right next step.  You're
> > >> probably
> > >> > best off using the bulk change feature instead of doing each JIRA
> > >> > individually.  I should have time to do a bunch of reviews this
> week,
> > >> I've
> > >> > actually already started.  I should have some time to continue doing
> > >> more
> > >> > reviews.  As a general thing, we've been pretty slow about getting
> > these
> > >> > done :(
> > >> >
> > >> > - Robert
> > >> >
> > >> > On Tue, Aug 2, 2016 at 4:25 PM, Rohini Palaniswamy <
> > >> > rohini.adi...@gmail.com> wrote:
> > >> >
> > >> >> I also did mark some of the enhancement jiras that Satish was
> working
> > >> on
> > >> >> and which might take time to review to 4.4.0
> > >> >>
> > >> >> Regards,
> > >> >> Rohini
> > >> >>
> > >> >> On Tue, Aug 2, 2016 at 3:01 PM, Rohini Palaniswamy <
> > >> >> rohini.adi...@gmail.com>
> > >> >> wrote:
> > >> >>
> > >> >> > Abhishek,
> > >> >> > Can you mark all jiras already committed to trunk as 4.3.0
> and
> > >> those
> > >> >> > planned in the scope document as 4.3.0? This will help filter on
> > >> those
> > >> >> > and review instead of referring to a google doc. I can pick up
> > 10-15
> > >> >> > jiras for review end of this week. We should try to get majority
> of
> > >> >> patches
> > >> >> > in the next 10 days and branch by Aug 12th. You can then use the
> > 3rd
> > >> >> week
> > >> >> > for any pending critical issues and rolling the release
> candidate.
> > >> >> >
> > >> >> > Robert,
> > >> >> >   I am thinking, that we should get rid of the trunk version and
> > use
> > >> >> > release numbers when committing from the beginning like all other
> > >> >> projects
> > >> >> > do. Unnecessary step to change from trunk to release version for
> > >> every
> > >> >> > release. If folks are in agreement, then will delete the trunk
> > >> version
> > >> >> > altogether. Does that require a mail to private?
> > >> >> >
> > >> >> > Regards,
> > >> >> > Rohini
> > >> >> >
> > >> >> > On Fri, Jul

[jira] [Updated] (OOZIE-2625) Drop workflowgenerator

[Robert Kanter (JIRA)]

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

Robert Kanter updated OOZIE-2625:
-
Attachment: OOZIE-2625.001.patch

The patch removes the {{wfgen}} profile from the root pom and deletes the 
{{workflowgenerator}} directory.  As far as I can tell, that's all we need to 
do; the workflow generator was pretty self-contained.

> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2625.001.patch
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

[jira] [Updated] (OOZIE-1402) Increase retry interval for non-progressing coordinator action with fix value

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy updated OOZIE-1402:
--
Fix Version/s: (was: trunk)
   4.3.0

> Increase retry interval for non-progressing coordinator action with fix value
> -
>
> Key: OOZIE-1402
> URL: https://issues.apache.org/jira/browse/OOZIE-1402
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: trunk
>Reporter: Mona Chitnis
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Fix For: 4.3.0
>
> Attachments: OOZIE-1402-1.patch, OOZIE-1402-2.patch, 
> OOZIE-1402-3.patch, OOZIE-1402-amend-1.patch, OOZIE-1402-amend-2.patch
>
>
> Currently every coordinator action is retried to check data directory in the
> next minute. 
> We could make it better by waiting longer for coordinator action that is not
> progressing (i.e. find no new directory) for repeated retries
> The waiting time should start from 1 minute for X retries. Then the action
> should wait for 2 minutes. After X retries it should wait for 3. The same way
> it will go to some max-wait-time and stay there until timeout



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

Re: [SCOPE] Oozie 4.3.0 Release

[Robert Kanter]

Ya, let's unset those remaining open trunk ones.  I agree, we need to put
in some effort to clean out old JIRAs and to review Patch Available JIRAs.

Also, I just created OOZIE-2625 to drop workflowgenerator.  We can discuss
the issue more there, but I listed a few reasons on OOZIE-2625 about why.

- Robert

On Wed, Aug 3, 2016 at 9:21 AM, Rohini Palaniswamy 
wrote:

>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Oozie%20AND%20fixVersion%3D%20%22trunk%22%20and%20status%20%3D%20open%20ORDER%20BY%20resolution%20ASC%2C%20status%20DESC&startIndex=50
>
> These are jiras open and marked trunk. Should we unset fix version on these
> or mark them for next release? Don't see majority of them being worked on
> even for next release. We need to do bug scrub and close many of these some
> time.
>
> > Instead
> of deleting "trunk", I think we're better off just renaming it to the
> release number.
>  There is some amount of relabeling either way. If we go with unsetting fix
> version, then we can as well delete trunk. Also, I did create a 4.4.0
> yesterday to move some of the patch available jiras from 4.3.0.
>
>
> On Wed, Aug 3, 2016 at 8:59 AM, Rohini Palaniswamy <
> rohini.adi...@gmail.com>
> wrote:
>
> > I think it would be better to send out email for the bulk change. If
> there
> > are any issues or jiras wrongly marked someone can respond. We do that
> with
> > Pig and there are always couple of jiras that folks come back with
> feedback
> > on pulling back to release.
> >
> >
> > On Wed, Aug 3, 2016 at 8:07 AM, Robert Kanter 
> > wrote:
> >
> >> Abhishek, next time you do a bulk change, please remember to tell it not
> >> to
> >> send out an email for every change :)
> >>
> >> On Tue, Aug 2, 2016 at 4:28 PM, Robert Kanter 
> >> wrote:
> >>
> >> > Rohini, that sounds good to me.  Especially because we're on "master"
> >> > branch but "trunk" version in JIRA and it gets a little confusing.
> >> Instead
> >> > of deleting "trunk", I think we're better off just renaming it to the
> >> > release number.  Otherwise, we'll have to re-label any current "trunk"
> >> > fields.  We can use 4.4.0 for now, but I imagine that the next release
> >> > might end up being 5.0.0 (with Oozie on Yarn); we can always rename it
> >> > later.
> >> >
> >> > I'm not sure if there's a specific rule here, but I suppose we should
> >> > probably have a vote in the private list to make things official as
> >> this is
> >> > a release-management-related change.  Can you send an email?
> >> >
> >> > Abhishek, thanks for putting this all together.  I think Rohini's
> >> > suggestion of updating the JIRAs is the right next step.  You're
> >> probably
> >> > best off using the bulk change feature instead of doing each JIRA
> >> > individually.  I should have time to do a bunch of reviews this week,
> >> I've
> >> > actually already started.  I should have some time to continue doing
> >> more
> >> > reviews.  As a general thing, we've been pretty slow about getting
> these
> >> > done :(
> >> >
> >> > - Robert
> >> >
> >> > On Tue, Aug 2, 2016 at 4:25 PM, Rohini Palaniswamy <
> >> > rohini.adi...@gmail.com> wrote:
> >> >
> >> >> I also did mark some of the enhancement jiras that Satish was working
> >> on
> >> >> and which might take time to review to 4.4.0
> >> >>
> >> >> Regards,
> >> >> Rohini
> >> >>
> >> >> On Tue, Aug 2, 2016 at 3:01 PM, Rohini Palaniswamy <
> >> >> rohini.adi...@gmail.com>
> >> >> wrote:
> >> >>
> >> >> > Abhishek,
> >> >> > Can you mark all jiras already committed to trunk as 4.3.0 and
> >> those
> >> >> > planned in the scope document as 4.3.0? This will help filter on
> >> those
> >> >> > and review instead of referring to a google doc. I can pick up
> 10-15
> >> >> > jiras for review end of this week. We should try to get majority of
> >> >> patches
> >> >> > in the next 10 days and branch by Aug 12th. You can then use the
> 3rd
> >> >> week
> >> >> > for any pending critical issues and rolling the release candidate.
> >> >> >
> >> >> > Robert,
> >> >> >   I am thinking, that we should get rid of the trunk version and
> use
> >> >> > release numbers when committing from the beginning like all other
> >> >> projects
> >> >> > do. Unnecessary step to change from trunk to release version for
> >> every
> >> >> > release. If folks are in agreement, then will delete the trunk
> >> version
> >> >> > altogether. Does that require a mail to private?
> >> >> >
> >> >> > Regards,
> >> >> > Rohini
> >> >> >
> >> >> > On Fri, Jul 29, 2016 at 3:38 AM, Abhishek Bafna <
> >> bafna.i...@gmail.com>
> >> >> > wrote:
> >> >> >
> >> >> >> Hi All,
> >> >> >>
> >> >> >> As we prepared a Oozie 4.3.0 scope document <
> >> >> >>
> >> >>
> >>
> https://docs.google.com/document/d/1E1vGTul0hrWC4R8EgCRkO3ZmGNT5GmFsuHQZmrT63Ow/edit#heading=h.w9ycxfry7sfu
> >> >> >
> >> >> >> and listed all the things which we wanted to include in the
> release.
> >> >> In the
> >> >> >> last few days, I spent some time and reviewed some of the 

[jira] [Commented] (OOZIE-2625) Drop workflowgenerator

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-2625:
---

+1. I was just about to mail dev@ on this to ask we drop it or comment building 
it. Don't think anyone is using it.

> Drop workflowgenerator
> --
>
> Key: OOZIE-2625
> URL: https://issues.apache.org/jira/browse/OOZIE-2625
> Project: Oozie
>  Issue Type: Task
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
>
> I propose we drop the workflowgenerator for the following reasons:
> # It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which 
> is hosted on googlecode, which is down now, so it's causing a lot of build 
> failures:
> {code}
> [ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
> com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
> http://gwt-links.googlecode.com/svn/repository was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> gwt-links has elapsed or updates are forced -> [Help 1]
> {code}
> # It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
> maintaining it or testing it (as far as I know).  It surely lacks newer 
> features like Spark Action support.
> # Other UI editors, such as Hue, are more widely adopted, better maintained, 
> and easier to use/install.



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

[jira] [Created] (OOZIE-2625) Drop workflowgenerator

[Robert Kanter (JIRA)]

Robert Kanter created OOZIE-2625:


 Summary: Drop workflowgenerator
 Key: OOZIE-2625
 URL: https://issues.apache.org/jira/browse/OOZIE-2625
 Project: Oozie
  Issue Type: Task
Reporter: Robert Kanter
Assignee: Robert Kanter
 Fix For: 4.3.0


I propose we drop the workflowgenerator for the following reasons:
# It relies on the {{gwt-links}} dependency from {{com.orange.links}}, which is 
hosted on googlecode, which is down now, so it's causing a lot of build 
failures:
{code}
[ERROR] Failed to execute goal on project oozie-workflowgenerator: Could not 
resolve dependencies for project 
org.apache.oozie:oozie-workflowgenerator:war:4.3.0-SNAPSHOT: Failure to find 
com.orange.links:gwt-links:jar:1.3-SNAPSHOT in 
http://gwt-links.googlecode.com/svn/repository was cached in the local 
repository, resolution will not be reattempted until the update interval of 
gwt-links has elapsed or updates are forced -> [Help 1]
{code}
# It hasn't been really updated in 3 or 4 years now.  Nobody is actively 
maintaining it or testing it (as far as I know).  It surely lacks newer 
features like Spark Action support.
# Other UI editors, such as Hue, are more widely adopted, better maintained, 
and easier to use/install.



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

[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2496:
--

+1

GWT is only used for the workflowgenerator, which nobody's really updated in at 
least 3 years.  Looks like gwt-links comes from googlecode.com, which is down 
now.  I'll create a JIRA proposing we drop workflowgenerator.

> Testcase failure due to environment specific line.separator value
> -
>
> Key: OOZIE-2496
> URL: https://issues.apache.org/jira/browse/OOZIE-2496
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
> Environment: Windows
>Reporter: abhishek bafna
>Assignee: abhishek bafna
>  Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2496-01.patch, OOZIE-2496-02.patch, 
> OOZIE-2496-03.patch
>
>
> The "line.separator" returns operating system specific line separator. The 
> following testcase uses hard coded "\n" while comparing the return values in 
> the assertion, which makes them to fail on the windows environment.
> {noformat}
> org.apache.oozie.client.TestOozieCLI#testOozieStatus
> org.apache.oozie.client.TestOozieCLI#testServerBuildVersion
> org.apache.oozie.client.TestOozieCLI#testClientBuildVersion
> {noformat}
> In the following testcase, we are using "line.separator" where as 
> _TimestampedMessageParser_ sends the logs after appending "\n".
> {noformat}
> org.apache.oozie.util.TestXLogUserFilterParam#testloglevel_DEBUF_INFO
> org.apache.oozie.util.TestXLogUserFilterParam#testloglevel_Error
> org.apache.oozie.util.TestXLogUserFilterParam#testTextSearch
> {noformat}



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

[jira] [Resolved] (OOZIE-1176) DISCLAIMER.txt talks about incubator status

[abhishek bafna (JIRA)]

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

abhishek bafna resolved OOZIE-1176.
---
   Resolution: Duplicate
Fix Version/s: (was: trunk)
   4.3.0

> DISCLAIMER.txt talks about incubator status
> ---
>
> Key: OOZIE-1176
> URL: https://issues.apache.org/jira/browse/OOZIE-1176
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Udai Kiran Potluri
>Priority: Trivial
>  Labels: newbie
> Fix For: 4.3.0
>
>
> The DISCLAIMER.txt file in the root dir talks about Oozie being in incubator 
> status and gives the http://incubator.apache.org/oozie url.  
> We should either update the disclaimer (is there a standard Apache disclaimer 
> that should go here?) or simply delete the file.  



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

[jira] [Commented] (OOZIE-2602) Upgrade oozie to pig 0.16.0

[Jaydeep Vishwakarma (JIRA)]

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

Jaydeep Vishwakarma commented on OOZIE-2602:


[~nperiwal], Please trigger the patch.

> Upgrade oozie to pig 0.16.0
> ---
>
> Key: OOZIE-2602
> URL: https://issues.apache.org/jira/browse/OOZIE-2602
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Narayan Periwal
>Assignee: Narayan Periwal
> Fix For: 4.3.0
>
> Attachments: oozie-2602.patch
>
>
> Currently the pig version in Oozie is 0.12.1 
> We can upgrade oozie to pig 0.16.0



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