[jira] Subscription: Oozie Patch Available

2017-02-13 Thread jira 
Issue Subscription
Filter: Oozie Patch Available (86 issues)

Subscriber: ooziedaily

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

[jira] [Created] (OOZIE-2797) Cancellation of HCat Delegation Token

2017-02-13 Thread Satish Subhashrao Saley (JIRA) 
Satish Subhashrao Saley created OOZIE-2797:
--

 Summary: Cancellation of HCat Delegation Token
 Key: OOZIE-2797
 URL: https://issues.apache.org/jira/browse/OOZIE-2797
 Project: Oozie
  Issue Type: Bug
Reporter: Satish Subhashrao Saley
Assignee: Satish Subhashrao Saley


HCat delegation token does not get cancelled unless HCat cancels the token on 
its own after several days (i.e. depending on its configuration). 
Hive Action and Pig Action should cancel delegation token after completion. 

Currently, we can fix it by cancelling the tokens in finally block for Hive and 
Pig Action. I am putting patch for this.

But, a cleaner solution would be to have a class specifying APIs for 
cancellation and for each type of token, there would be a separate 
implementation. We can do it for Oozie 5.0.0. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2797) Cancellation of Delegation Tokens

2017-02-13 Thread Satish Subhashrao Saley (JIRA) 

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

Satish Subhashrao Saley updated OOZIE-2797:
---
Summary: Cancellation of Delegation Tokens  (was: Cancellation of HCat 
Delegation Token)

> Cancellation of Delegation Tokens
> -
>
> Key: OOZIE-2797
> URL: https://issues.apache.org/jira/browse/OOZIE-2797
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>
> HCat delegation token does not get cancelled unless HCat cancels the token on 
> its own after several days (i.e. depending on its configuration). 
> Hive Action and Pig Action should cancel delegation token after completion. 
> Currently, we can fix it by cancelling the tokens in finally block for Hive 
> and Pig Action. I am putting patch for this.
> But, a cleaner solution would be to have a class specifying APIs for 
> cancellation and for each type of token, there would be a separate 
> implementation. We can do it for Oozie 5.0.0. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2796) oozie.action.keep.action.dir not getting noticed

2017-02-13 Thread Attila Sasvari (JIRA) 

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

Attila Sasvari commented on OOZIE-2796:
---

[~zhengxb2005] thanks for the updated patch.

+1 (non-binding)

> oozie.action.keep.action.dir not getting noticed
> 
>
> Key: OOZIE-2796
> URL: https://issues.apache.org/jira/browse/OOZIE-2796
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Xiaobin Zheng
> Fix For: trunk
>
> Attachments: OOZIE-2796-1.patch, OOZIE-2796-2.patch, 
> OOZIE-2796-3.patch
>
>
> When trying to add following configuration entry:
> {code:xml}
> 
> oozie.action.keep.action.dir
> true
> 
> {code}
> to the application level configuration of {{workflow.xml}}, the workflow 
> directories are removed just after the workflow has finished.
> This should not be the case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2796) oozie.action.keep.action.dir not getting noticed

2017-02-13 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2796:
--

Testing JIRA OOZIE-2796

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
{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: 1877
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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

> oozie.action.keep.action.dir not getting noticed
> 
>
> Key: OOZIE-2796
> URL: https://issues.apache.org/jira/browse/OOZIE-2796
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Xiaobin Zheng
> Fix For: trunk
>
> Attachments: OOZIE-2796-1.patch, OOZIE-2796-2.patch, 
> OOZIE-2796-3.patch
>
>
> When trying to add following configuration entry:
> {code:xml}
> 
> oozie.action.keep.action.dir
> true
> 
> {code}
> to the application level configuration of {{workflow.xml}}, the workflow 
> directories are removed just after the workflow has finished.
> This should not be the case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

2017-02-13 Thread Apache Jenkins Server 
See

[jira] [Updated] (OOZIE-2796) oozie.action.keep.action.dir not getting noticed

2017-02-13 Thread Xiaobin Zheng (JIRA) 

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

Xiaobin Zheng updated OOZIE-2796:
-
Attachment: OOZIE-2796-3.patch

Thx for the feedback [~asasvari]! And thx for help verifying it as well!

I updated the patch as per your comments: the initialization of mocks needed 
are moved into @Before method so that they gets cleaned up for each test case; 
I also split the test cases into different unit tests as you suggested.

> oozie.action.keep.action.dir not getting noticed
> 
>
> Key: OOZIE-2796
> URL: https://issues.apache.org/jira/browse/OOZIE-2796
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Xiaobin Zheng
> Fix For: trunk
>
> Attachments: OOZIE-2796-1.patch, OOZIE-2796-2.patch, 
> OOZIE-2796-3.patch
>
>
> When trying to add following configuration entry:
> {code:xml}
> 
> oozie.action.keep.action.dir
> true
> 
> {code}
> to the application level configuration of {{workflow.xml}}, the workflow 
> directories are removed just after the workflow has finished.
> This should not be the case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2795) Create lib directory or symlink for Oozie CLI during packaging

2017-02-13 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2795:
--

Testing JIRA OOZIE-2795

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:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
{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/3646/

> Create lib directory or symlink for Oozie CLI during packaging
> --
>
> Key: OOZIE-2795
> URL: https://issues.apache.org/jira/browse/OOZIE-2795
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Peter Cseh
> Attachments: OOZIE-2795-001.patch, OOZIE-2795-002.patch, 
> OOZIE-2795-003.patch
>
>
> After creating an Oozie distro, lib directory is not present in the distro 
> directory (e.g. oozie-4.4.0-SNAPSHOT) in the generated tar.gz .
>  
> As a consequence, first run of theOozie CLI will fail if one tries to execute 
> it prior to server start:
> {noformat}
> $ bin/oozie
> unzip:  cannot find or open 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war,
>  
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.zip
>  or 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.ZIP.
> mv: rename 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib/*.jar
>  to 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/*.jar:
>  No such file or directory
> rmdir: 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib:
>  No such file or directory
> rmdir: 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF:
>  No such file or directory
> Error: Could not find or load main class org.apache.oozie.cli.OozieCLI
> {noformat}
> If you start the server first however, a symlink is created (see 
> {{bin/oozie-jetty-server.sh}}), and this error will not be visible.
> Earlier {{bin/oozie}} created this library by extracting it from the WAR file 
> used for Tomcat. Comment in the script:
>

[jira] [Commented] (OOZIE-2796) oozie.action.keep.action.dir not getting noticed

2017-02-13 Thread Attila Sasvari (JIRA) 

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

Attila Sasvari commented on OOZIE-2796:
---

Thanks for the patch [~zhengxb2005]. 
- I executed the {{TestWfEndXCommand}} test, and it passed. It's nice to see 
Mockito in the test!
- I also tested on a pseudo Hadoop cluster that your solution works: 
if {{oozie.action.keep.action.dir=false}} was specified in {{job.properties}}, 
wf directory got deleted; and in case of {{oozie.action.keep.action.dir=true}}, 
wf dir was not deleted. 

Some minor comments:
- In WfEndXCommand you could simplify the else part.  Instead of:
{code}
else {
  if (keepActionDir) {
LOG.debug("oozie.action.keep.action.dir is set to true");
  }
  else {
LOG.debug("Tmp dir doesn't exist :" + wfDirPath);
  }
}   
{code}
You could:
{code}
else if (keepActionDir) {
  LOG.debug("oozie.action.keep.action.dir is set to true");
}
else {
  LOG.debug("Tmp dir doesn't exist :" + wfDirPath);
}   
{code}
(-1 nested if-else)

- In the {{TestWfEndXCommand}} test I would:
-- use JUnit annotations (@BeforeClass, @AfterClass, @Test, etc.),
-- extract multiple test cases (using names similar to the comments that 
explain what is being tested) instead of testing everything in one method.

> oozie.action.keep.action.dir not getting noticed
> 
>
> Key: OOZIE-2796
> URL: https://issues.apache.org/jira/browse/OOZIE-2796
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Xiaobin Zheng
> Fix For: trunk
>
> Attachments: OOZIE-2796-1.patch, OOZIE-2796-2.patch
>
>
> When trying to add following configuration entry:
> {code:xml}
> 
> oozie.action.keep.action.dir
> true
> 
> {code}
> to the application level configuration of {{workflow.xml}}, the workflow 
> directories are removed just after the workflow has finished.
> This should not be the case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2718) Improve -dryrun for bundles

2017-02-13 Thread Abhishek Bafna (JIRA) 

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

Abhishek Bafna commented on OOZIE-2718:
---

The output of the bundle dryrun prints {{***coordJob after parsing: *** ... 
etc}} where as it outputs parsed bundle. 
[Here|https://github.com/apache/oozie/blob/master/client/src/main/java/org/apache/oozie/cli/OozieCLI.java#L1005]

Also, add a section like 
https://oozie.apache.org/docs/4.3.0/DG_CommandLineTool.html#Dryrun_of_Workflow_Job
 for Bundle.

> Improve -dryrun for bundles
> ---
>
> Key: OOZIE-2718
> URL: https://issues.apache.org/jira/browse/OOZIE-2718
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Xiaobin Zheng
> Attachments: OOZIE-2718-1.patch, OOZIE-2718-2.patch, 
> OOZIE-2718-3.patch, OOZIE-2718-4.patch
>
>
> When trying to do a -dryrun for Oozie:
> {code}
> error:
> Error: E1310 : E1310: Bundle Job submission Error: [null]
> {code}
> The 
> [documentation|https://oozie.apache.org/docs/4.2.0/DG_CommandLineTool.html#Dryrun_of_Coordinator_Job]
>  states that dryruns are working for workflows and coordinators.
> {quote}
> "Dryrun a workflow (since 3.3.2) or coordinator (since 2.0) job without 
> actually executing it"
> {quote}
> The easy fix is to document that it does not work and create an appropriate 
> error message for it. It's also possible to add support for bundle dryruns. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (OOZIE-2795) Create lib directory or symlink for Oozie CLI during packaging

2017-02-13 Thread Peter Cseh (JIRA) 

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

Peter Cseh edited comment on OOZIE-2795 at 2/13/17 11:17 AM:
-

Thanks for the review and the updated patch [~asasvari]!



was (Author: gezapeti):
Thanks for the review [~asasvari]!

# replaced lib folder from client's to server's lib
# changed some scripts to not depend on war


> Create lib directory or symlink for Oozie CLI during packaging
> --
>
> Key: OOZIE-2795
> URL: https://issues.apache.org/jira/browse/OOZIE-2795
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Peter Cseh
> Attachments: OOZIE-2795-001.patch, OOZIE-2795-002.patch
>
>
> After creating an Oozie distro, lib directory is not present in the distro 
> directory (e.g. oozie-4.4.0-SNAPSHOT) in the generated tar.gz .
>  
> As a consequence, first run of theOozie CLI will fail if one tries to execute 
> it prior to server start:
> {noformat}
> $ bin/oozie
> unzip:  cannot find or open 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war,
>  
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.zip
>  or 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.ZIP.
> mv: rename 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib/*.jar
>  to 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/*.jar:
>  No such file or directory
> rmdir: 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib:
>  No such file or directory
> rmdir: 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF:
>  No such file or directory
> Error: Could not find or load main class org.apache.oozie.cli.OozieCLI
> {noformat}
> If you start the server first however, a symlink is created (see 
> {{bin/oozie-jetty-server.sh}}), and this error will not be visible.
> Earlier {{bin/oozie}} created this library by extracting it from the WAR file 
> used for Tomcat. Comment in the script:
> {noformat}
> #Create lib directory from war if lib doesn't exist 
> {noformat}
> We could create a symlink to embedded-oozie-server/webapp/WEB-INF/lib/ or 
> copy that directory. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2795) Create lib directory or symlink for Oozie CLI during packaging

2017-02-13 Thread Peter Cseh (JIRA) 

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

Peter Cseh updated OOZIE-2795:
--
Attachment: OOZIE-2795-002.patch

Thanks for the review [~asasvari]!

# replaced lib folder from client's to server's lib
# changed some scripts to not depend on war


> Create lib directory or symlink for Oozie CLI during packaging
> --
>
> Key: OOZIE-2795
> URL: https://issues.apache.org/jira/browse/OOZIE-2795
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Peter Cseh
> Attachments: OOZIE-2795-001.patch, OOZIE-2795-002.patch
>
>
> After creating an Oozie distro, lib directory is not present in the distro 
> directory (e.g. oozie-4.4.0-SNAPSHOT) in the generated tar.gz .
>  
> As a consequence, first run of theOozie CLI will fail if one tries to execute 
> it prior to server start:
> {noformat}
> $ bin/oozie
> unzip:  cannot find or open 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war,
>  
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.zip
>  or 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.ZIP.
> mv: rename 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib/*.jar
>  to 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/*.jar:
>  No such file or directory
> rmdir: 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib:
>  No such file or directory
> rmdir: 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF:
>  No such file or directory
> Error: Could not find or load main class org.apache.oozie.cli.OozieCLI
> {noformat}
> If you start the server first however, a symlink is created (see 
> {{bin/oozie-jetty-server.sh}}), and this error will not be visible.
> Earlier {{bin/oozie}} created this library by extracting it from the WAR file 
> used for Tomcat. Comment in the script:
> {noformat}
> #Create lib directory from war if lib doesn't exist 
> {noformat}
> We could create a symlink to embedded-oozie-server/webapp/WEB-INF/lib/ or 
> copy that directory. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2795) Create lib directory or symlink for Oozie CLI during packaging

2017-02-13 Thread Attila Sasvari (JIRA) 

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

Attila Sasvari updated OOZIE-2795:
--
Attachment: OOZIE-2795-002.patch

new patch with proposed changes

Tests I performed on a pseudo Hadoop 2.6.0:

{code}
# Create distro
$ bin/mkdistro.sh -DskipTests -Dhadoop.version=2.6.0 -Puber 
$ cd distro/target/oozie-4.4.0-SNAPSHOT-distro/oozie-4.4.0-SNAPSHOT 

# Install sharelib
$ bin/oozie-setup.sh sharelib create -fs hdfs://localhost:9000 -locallib 
oozie-sharelib-*.tar.gz

# Start Oozie server
$ bin/oozied.sh start

# Get status 
$ bin/oozie admin -oozie http://localhost:11000/oozie -status 
{code}


> Create lib directory or symlink for Oozie CLI during packaging
> --
>
> Key: OOZIE-2795
> URL: https://issues.apache.org/jira/browse/OOZIE-2795
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Peter Cseh
> Attachments: OOZIE-2795-001.patch, OOZIE-2795-002.patch
>
>
> After creating an Oozie distro, lib directory is not present in the distro 
> directory (e.g. oozie-4.4.0-SNAPSHOT) in the generated tar.gz .
>  
> As a consequence, first run of theOozie CLI will fail if one tries to execute 
> it prior to server start:
> {noformat}
> $ bin/oozie
> unzip:  cannot find or open 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war,
>  
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.zip
>  or 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.ZIP.
> mv: rename 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib/*.jar
>  to 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/*.jar:
>  No such file or directory
> rmdir: 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib:
>  No such file or directory
> rmdir: 
> /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF:
>  No such file or directory
> Error: Could not find or load main class org.apache.oozie.cli.OozieCLI
> {noformat}
> If you start the server first however, a symlink is created (see 
> {{bin/oozie-jetty-server.sh}}), and this error will not be visible.
> Earlier {{bin/oozie}} created this library by extracting it from the WAR file 
> used for Tomcat. Comment in the script:
> {noformat}
> #Create lib directory from war if lib doesn't exist 
> {noformat}
> We could create a symlink to embedded-oozie-server/webapp/WEB-INF/lib/ or 
> copy that directory. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)