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

2014-11-18 Thread Apache Jenkins Server 
See 

--
[...truncated 32451 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-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.2.0-SNAPSHOT
[INFO] 
[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] 
[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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 

[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.2.0-SNAPSHOT
[INFO] 
[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] 
[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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 

[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.41/bin/apache-tomcat-6.0.41.tar.gz
  [get] To: 

...

[jira] [Commented] (OOZIE-1983) Add spark action executor

2014-11-18 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-1983:
--

Testing JIRA OOZIE-1983

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:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:red}-1{color} the patch seems to introduce 4 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}
.Tests run: 1556
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testMessage_withMixedStatus(org.apache.oozie.command.coord.TestAbandonedCoordChecker)

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

> Add spark action executor
> -
>
> Key: OOZIE-1983
> URL: https://issues.apache.org/jira/browse/OOZIE-1983
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Shwetha G S
>Assignee: pavan kumar kolamuri
>  Labels: spark
> Fix For: trunk
>
> Attachments: OOZIE-1983v2.patch, OOZIE-1983v3.patch, 
> OOZIE-1983v4.patch, spark-actionv1.patch
>
>




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

[jira] Subscription: Oozie Patch Available

2014-11-18 Thread jira 
Issue Subscription
Filter: Oozie Patch Available (45 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2069  RecoveryService reads incorrect configuration 
https://issues.apache.org/jira/browse/OOZIE-2069
OOZIE-2065  Oozie returns incorrect total action for coord dryrun
https://issues.apache.org/jira/browse/OOZIE-2065
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
OOZIE-2055  PauseTransitService does not proceed forward if any job has issue 
https://issues.apache.org/jira/browse/OOZIE-2055
OOZIE-2053  Change old HCatalog API
https://issues.apache.org/jira/browse/OOZIE-2053
OOZIE-2051  Allows multiple default action configuration files per action
https://issues.apache.org/jira/browse/OOZIE-2051
OOZIE-2044  ssh action succeed with a not exists command which should be fail.
https://issues.apache.org/jira/browse/OOZIE-2044
OOZIE-2035  NotificationXCommand should support proxy
https://issues.apache.org/jira/browse/OOZIE-2035
OOZIE-2029  Workflow re-run with RERUN_FAIL_NODES=true should re-run only the 
failed nodes of the sub-workflow
https://issues.apache.org/jira/browse/OOZIE-2029
OOZIE-2024  Confusing message when a job can't be looked up by 
JavaActionExecutor
https://issues.apache.org/jira/browse/OOZIE-2024
OOZIE-1983  Add spark action executor
https://issues.apache.org/jira/browse/OOZIE-1983
OOZIE-1980  Sql error should not fail coord job
https://issues.apache.org/jira/browse/OOZIE-1980
OOZIE-1977  Display patch analysis issues
https://issues.apache.org/jira/browse/OOZIE-1977
OOZIE-1936  Queuedump command should display queue information for all server.
https://issues.apache.org/jira/browse/OOZIE-1936
OOZIE-1931  Admin command to print all locks held by server(s)
https://issues.apache.org/jira/browse/OOZIE-1931
OOZIE-1927  Use StoreStatusFilter for WorkflowsJobGetJPAExecutor 
https://issues.apache.org/jira/browse/OOZIE-1927
OOZIE-1922  MemoryLocksService fails if lock is acquired multiple times in same 
thread and released
https://issues.apache.org/jira/browse/OOZIE-1922
OOZIE-1918  ActionXCommand refactoring for code reuse
https://issues.apache.org/jira/browse/OOZIE-1918
OOZIE-1889  Convert NamedNativeQueries to JPQL
https://issues.apache.org/jira/browse/OOZIE-1889
OOZIE-1884  ZKJobsConcurrencyService.checkJobIdForServer fails if jobs length > 
7
https://issues.apache.org/jira/browse/OOZIE-1884
OOZIE-1876  use pom properties rather than specific version numbers in the pom 
files of hbaselibs, hcataloglibs, sharelib, etc 
https://issues.apache.org/jira/browse/OOZIE-1876
OOZIE-1860  Oozie job mapper launch fails due to null value returned from 
action file
https://issues.apache.org/jira/browse/OOZIE-1860
OOZIE-1855  TestPriorityDelayQueue#testPoll failed intermittently in Jenkins
https://issues.apache.org/jira/browse/OOZIE-1855
OOZIE-1829  URIHandlerService doesn't support URI schemes with query strings 
but no path segment
https://issues.apache.org/jira/browse/OOZIE-1829
OOZIE-1816  LogInfo uses action name instead of id
https://issues.apache.org/jira/browse/OOZIE-1816
OOZIE-1810  Workflow cannot get into Failed state when kill control node cannot 
resolve variable in message 
https://issues.apache.org/jira/browse/OOZIE-1810
OOZIE-1802  Support workflow action log
https://issues.apache.org/jira/browse/OOZIE-1802
OOZIE-1793  Improve find bugs reporting for Oozie
https://issues.apache.org/jira/browse/OOZIE-1793
OOZIE-1782  Workflow path not found is thrown as SC_UNAUTHORIZED
https://issues.apache.org/jira/browse/OOZIE-1782
OOZIE-1779  Add parent-id as a filter option
https://issues.apache.org/jira/browse/OOZIE-1779
OOZIE-1705  Enable gc logs and print thread id in logs
https://issues.apache.org/jira/browse/OOZIE-1705
OOZIE-1688  New configuration to specify server-server authentication type.
https://issues.apache.org/jira/browse/OOZIE-1688
OOZIE-1676  Instrumentation and Configuration over the REST API and Web UI 
should include all Oozie servers
https://issues.apache.org/jira/browse/OOZIE-1676
OOZIE-1654  Fix typo (inteval to interval)
https://issues.apache.org/jira/browse/OOZIE-1654
OOZIE-1638  Action retry does not use default retry max count.
https://issues.apache.org/jira/browse/OOZIE-1638
OOZIE-1636  OOZIE_SYS table engine should be innodb
https://issues.apache.org/jira/browse/OOZIE-1636
OOZIE-1624  Exclusion pattern for sharelib.
https://issues.apache.org/jira/browse/OOZIE-1624
OOZIE-1599  Cache the list of available timezones from the admin servlet
https://issues.apache.o

[jira] [Commented] (OOZIE-1983) Add spark action executor

2014-11-18 Thread pavan kumar kolamuri (JIRA) 

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

pavan kumar kolamuri commented on OOZIE-1983:
-

[~rkanter]   Patch updated can you please check 

> Add spark action executor
> -
>
> Key: OOZIE-1983
> URL: https://issues.apache.org/jira/browse/OOZIE-1983
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Shwetha G S
>Assignee: pavan kumar kolamuri
>  Labels: spark
> Fix For: trunk
>
> Attachments: OOZIE-1983v2.patch, OOZIE-1983v3.patch, 
> OOZIE-1983v4.patch, spark-actionv1.patch
>
>




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

Re: Review Request 27614: OOZIE-1983 Add spark action executor in oozie

2014-11-18 Thread pavan kumar kolamuri 

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

(Updated Nov. 19, 2014, 5:43 a.m.)


Review request for oozie and shwethags.


Changes
---

Fixed based on comments .


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


Repository: oozie-git


Description
---

Add spark action executor in oozie. Spark jobs can be run using oozie 


Diffs (updated)
-

  client/src/main/java/org/apache/oozie/cli/OozieCLI.java 9c2d14b 
  client/src/main/resources/spark-action-0.1.xsd PRE-CREATION 
  core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
PRE-CREATION 
  core/src/main/resources/oozie-default.xml 17155a1 
  docs/src/site/twiki/DG_SparkActionExtension.twiki PRE-CREATION 
  docs/src/site/twiki/index.twiki c8ba742 
  pom.xml 1e79186 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/JavaMain.java 
8b8135a 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
8cfefbb 
  sharelib/pom.xml aa479a8 
  sharelib/spark/pom.xml PRE-CREATION 
  sharelib/spark/src/main/java/org.apache.oozie.action.hadoop/SparkMain.java 
PRE-CREATION 
  
sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkActionExecutor.java
 PRE-CREATION 
  
sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkMain.java 
PRE-CREATION 
  src/main/assemblies/sharelib.xml 4a46b90 
  webapp/pom.xml 35776c5 

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


Testing
---

Both unit testing and end to end testing done


Thanks,

pavan kumar kolamuri

[jira] [Updated] (OOZIE-1983) Add spark action executor

2014-11-18 Thread pavan kumar kolamuri (JIRA) 

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

pavan kumar kolamuri updated OOZIE-1983:

Attachment: OOZIE-1983v4.patch

> Add spark action executor
> -
>
> Key: OOZIE-1983
> URL: https://issues.apache.org/jira/browse/OOZIE-1983
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Shwetha G S
>Assignee: pavan kumar kolamuri
>  Labels: spark
> Fix For: trunk
>
> Attachments: OOZIE-1983v2.patch, OOZIE-1983v3.patch, 
> OOZIE-1983v4.patch, spark-actionv1.patch
>
>




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

Re: Review Request 27614: OOZIE-1983 Add spark action executor in oozie

2014-11-18 Thread pavan kumar kolamuri 


> On Nov. 19, 2014, 2:01 a.m., Robert Kanter wrote:
> > Looks good overall.  I just had some minor, mostly trivial, comments this 
> > time.
> > 
> > I'm sure you've done some testing.  Have you made sure that a Spark job 
> > that fails is properly handled?

Yes i have tested end to end , yes it was handled when spark job fails even the 
workflow will fail.


> On Nov. 19, 2014, 2:01 a.m., Robert Kanter wrote:
> > core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java, 
> > lines 85-86
> > 
> >
> > Please use curly braces around the if statement.  It's very easy for 
> > someone later to accidently mess something up here otherwise

Ok


> On Nov. 19, 2014, 2:01 a.m., Robert Kanter wrote:
> > sharelib/spark/pom.xml, lines 31-32
> > 
> >
> > I know this is silly, but capitalize 's' in Spark

Done


> On Nov. 19, 2014, 2:01 a.m., Robert Kanter wrote:
> > sharelib/spark/pom.xml, line 45
> > 
> >
> > In that case, can we add a property to the root pom so we can set the 
> > version there and reference it here?  That way we're less likely to forget 
> > about this in the future.
> > 
> > e.g.
> > ${spark.guava.version}

Sure will use this


> On Nov. 19, 2014, 2:01 a.m., Robert Kanter wrote:
> > sharelib/spark/src/main/java/org.apache.oozie.action.hadoop/SparkMain.java, 
> > line 45
> > 
> >
> > Can you add the below print statement here like we do in most of the 
> > other actions?
> > 
> > e.g.
> > System.out.println();
> > System.out.println("Oozie Spark action configuration");
> > 
> > System.out.println("=");
> > System.out.println();

will add


> On Nov. 19, 2014, 2:01 a.m., Robert Kanter wrote:
> > sharelib/spark/src/main/java/org.apache.oozie.action.hadoop/SparkMain.java, 
> > line 93
> > 
> >
> > Can you add the below print statement here like we do in most of the 
> > other actions?
> > 
> > 
> > System.out.println("=");
> > System.out.println();
> > System.out.println(">>> Invoking Spark class now >>>");
> > System.out.println();
> > System.out.flush();

will add


- pavan kumar


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


On Nov. 13, 2014, 6:49 a.m., pavan kumar kolamuri wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27614/
> ---
> 
> (Updated Nov. 13, 2014, 6:49 a.m.)
> 
> 
> Review request for oozie and shwethags.
> 
> 
> Bugs: OOZIE-1983
> https://issues.apache.org/jira/browse/OOZIE-1983
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Add spark action executor in oozie. Spark jobs can be run using oozie 
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 9c2d14b 
>   client/src/main/resources/spark-action-0.1.xsd PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
> PRE-CREATION 
>   core/src/main/resources/oozie-default.xml 17155a1 
>   docs/src/site/twiki/DG_SparkActionExtension.twiki PRE-CREATION 
>   docs/src/site/twiki/index.twiki c8ba742 
>   pom.xml 1e79186 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/JavaMain.java 
> 8b8135a 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
> 8cfefbb 
>   sharelib/pom.xml aa479a8 
>   sharelib/spark/pom.xml PRE-CREATION 
>   sharelib/spark/src/main/java/org.apache.oozie.action.hadoop/SparkMain.java 
> PRE-CREATION 
>   
> sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkActionExecutor.java
>  PRE-CREATION 
>   
> sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkMain.java
>  PRE-CREATION 
>   src/main/assemblies/sharelib.xml 4a46b90 
>   webapp/pom.xml 35776c5 
> 
> Diff: https://reviews.apache.org/r/27614/diff/
> 
> 
> Testing
> ---
> 
> Both unit testing and end to end testing done
> 
> 
> Thanks,
> 
> pavan kumar kolamuri
> 
>

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

2014-11-18 Thread Apache Jenkins Server 
See 

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

[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.2.0-SNAPSHOT
[INFO] 
[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] 
[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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 

[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.2.0-SNAPSHOT
[INFO] 
[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] 
[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] 
[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 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 

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

...

[jira] [Commented] (OOZIE-2069) RecoveryService reads incorrect configuration

2014-11-18 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-2069:
--

Testing JIRA OOZIE-2069

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: 1556
{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/2096/

> RecoveryService reads incorrect configuration 
> --
>
> Key: OOZIE-2069
> URL: https://issues.apache.org/jira/browse/OOZIE-2069
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
> Attachments: OOZIE-2069-V1.patch
>
>
>   This causes a lot of duplicate coordinators to be created for a submitted 
> bundle. Found by [~mchiang_4w...@yahoo.com] with the regression tests.



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

vote result release oozie 4.1.0 (candidate 1)

2014-11-18 Thread bowen zhang 
Hi folks,Oozie 4.1.0 has passed the vote. 
the vote tally is:+1 --> 3 votes from oozie PMC (binding), 3 votes from oozie 
committers (non-binding), 0 votes from oozie contributors-1 --> 0 votes0 --> 0 
votes
If there are no other concerns or issues, then RC1 will be the official 
oozie-4.1.0 release.Bowen

Re: VOTE Release Oozie 4.1.0 (candidate 1)

2014-11-18 Thread bowen zhang 
+1
  From: Robert Kanter 
 To: "dev@oozie.apache.org" ; bowen zhang 
 
 Sent: Tuesday, November 18, 2014 5:04 PM
 Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
   
The hadoop-2, hadoop-3, and hadoop-0.23 profiles set the pig classifier and 
sqoop classifier.  As long as the user uses the same hadoop profile as what 
they are running against, the sharelib will have the right pig and sqoop jars.  
e.g. If deploying with Hadoop 2, they should use the hadoop-2 profile.  If they 
deploy with hadoop-1 and use the hadoop-2 profile, the sharelib will be wrong, 
but that's expected.  


On Tue, Nov 18, 2014 at 1:23 PM, bowen zhang  
wrote:

I guess we might need to document the fact for pig to run with hadoop-2, you 
need "-Dpig.classifier=2" as a maven command line option

      From: Rohini Palaniswamy 
 To: "dev@oozie.apache.org" 
Cc: bowen zhang 
 Sent: Tuesday, November 18, 2014 3:27 AM
 Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)

+1



On Tue, Nov 18, 2014 at 2:36 AM, Ryota Egashira <
egash...@yahoo-inc.com.invalid> wrote:

> +1
> -Built release artifact successfully
> -ran couple of example jobs on single-node setting, which succeeded.
>
> Ryota
>
> On 11/17/14, 5:10 PM, "Robert Kanter"  wrote:
>
> >+1
> >
> >- downloaded release artifacts
> >- built with Hadoop 1.1.1 (though ran against Hadoop 1.2.0) and ran a few
> >of the examples.
> >- built with Hadoop 2.3.0 (though ran against Hadoop some 2.7.0-SNAPSHOT)
> >and ran a few of the examples.  There's something wrong with my Hadoop 2
> >setup, but as far as I could tell, Oozie was working properly.
> >
> >- One thing: the release-log says that 4.1 is unrelated.  That should be
> >removed.  While you're at it, please also fix that for 4.0.1, I apparently
> >forgot to do that too :)
> >
> >- (And the key issue that was already mentioned should be fixed)
> >
> >
> >On Mon, Nov 17, 2014 at 11:18 AM, Mohammad Islam
> > >> wrote:
> >
> >> Sorry Bowen for the delay.I'm looking into this , I never tried that.
> >> Regards,Mohammad
> >>
> >>      On Monday, November 17, 2014 9:58 AM, bowen zhang
> >>  wrote:
> >>
> >>
> >>  Hi Mohammad,I think the KEY issue is the reason Mona has problem
> >>signing
> >> the page since I cannot commit my key to the repo. Can you resolve this
> >> ASAP?Thanks,Bowen
> >>
> >>      From: Mona Chitnis 
> >>  To: "dev@oozie.apache.org" ; bowen zhang <
> >> bowenzhang...@yahoo.com>
> >>  Sent: Monday, November 17, 2014 9:15 AM
> >>  Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
> >>
> >> Downloaded the tarball, built and installed Oozie (-DskipTests) and ran
> >>an
> >> example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that.
> >> Was unable to verify the md5 and gpg signatures. I dont find the key
> >>used
> >> for signing the page in the list of public keys on the KEYS page. Please
> >> let me know if I'm missing the right procedure.
> >> Regards, Mona Chitnis
> >>
> >>
> >>
> >>
> >>    On Monday, November 17, 2014 8:08 AM, Shwetha GS <
> >> shwetha...@inmobi.com> wrote:
> >>
> >>
> >>  +1
> >>
> >> On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang <
> >> bowenzhang...@yahoo.com.invalid> wrote:
> >>
> >> > Hi,
> >> >
> >> > I have created a build for Oozie 4.1.0, candidate 1.
> >> >
> >> > Keys to verify the signature of the release artifact are available at
> >> >
> >> >  http://www.apache.org/dist/oozie/KEYS
> >> >
> >> > Please download, test, and try it out:
> >> >
> >> >  http://people.apache.org/~bzhang/oozie-4.1.0-rc1
> >> >
> >> > The release, md5 signature, gpg signature, and rat report can all
> >> > be found at the above address.
> >> >
> >> > Vote closes on Monday EOD, the 17th.
> >> >
> >> > Bowen
> >> >
> >>
> >> --
> >> _
> >> The information contained in this communication is intended solely for
> >>the
> >> use of the individual or entity to whom it is addressed and others
> >> authorized to receive it. It may contain confidential or legally
> >>privileged
> >> information. If you are not the intended recipient you are hereby
> >>notified
> >> that any disclosure, copying, distribution or taking any action in
> >>reliance
> >> on the contents of this information is strictly prohibited and may be
> >> unlawful. If you have received this communication in error, please
> >>notify
> >> us immediately by responding to this email and then delete it from your
> >> system. The firm is neither liable for the proper and complete
> >>transmission
> >> of the information contained in this communication nor for any delay in
> >>its
> >> receipt.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
>


 

[jira] [Commented] (OOZIE-1983) Add spark action executor

2014-11-18 Thread Robert Kanter (JIRA) 

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

Robert Kanter commented on OOZIE-1983:
--

Just added more comments to RB.

> Add spark action executor
> -
>
> Key: OOZIE-1983
> URL: https://issues.apache.org/jira/browse/OOZIE-1983
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Shwetha G S
>Assignee: pavan kumar kolamuri
>  Labels: spark
> Fix For: trunk
>
> Attachments: OOZIE-1983v2.patch, OOZIE-1983v3.patch, 
> spark-actionv1.patch
>
>




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

Re: Review Request 27614: OOZIE-1983 Add spark action executor in oozie

2014-11-18 Thread Robert Kanter 

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


Looks good overall.  I just had some minor, mostly trivial, comments this time.

I'm sure you've done some testing.  Have you made sure that a Spark job that 
fails is properly handled?


core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java


Please use curly braces around the if statement.  It's very easy for 
someone later to accidently mess something up here otherwise



sharelib/spark/pom.xml


I know this is silly, but capitalize 's' in Spark



sharelib/spark/pom.xml


In that case, can we add a property to the root pom so we can set the 
version there and reference it here?  That way we're less likely to forget 
about this in the future.

e.g.
${spark.guava.version}



sharelib/spark/src/main/java/org.apache.oozie.action.hadoop/SparkMain.java


Can you add the below print statement here like we do in most of the other 
actions?

e.g.
System.out.println();
System.out.println("Oozie Spark action configuration");

System.out.println("=");
System.out.println();



sharelib/spark/src/main/java/org.apache.oozie.action.hadoop/SparkMain.java


Can you add the below print statement here like we do in most of the other 
actions?


System.out.println("=");
System.out.println();
System.out.println(">>> Invoking Spark class now >>>");
System.out.println();
System.out.flush();


- Robert Kanter


On Nov. 13, 2014, 6:49 a.m., pavan kumar kolamuri wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27614/
> ---
> 
> (Updated Nov. 13, 2014, 6:49 a.m.)
> 
> 
> Review request for oozie and shwethags.
> 
> 
> Bugs: OOZIE-1983
> https://issues.apache.org/jira/browse/OOZIE-1983
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Add spark action executor in oozie. Spark jobs can be run using oozie 
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 9c2d14b 
>   client/src/main/resources/spark-action-0.1.xsd PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
> PRE-CREATION 
>   core/src/main/resources/oozie-default.xml 17155a1 
>   docs/src/site/twiki/DG_SparkActionExtension.twiki PRE-CREATION 
>   docs/src/site/twiki/index.twiki c8ba742 
>   pom.xml 1e79186 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/JavaMain.java 
> 8b8135a 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
> 8cfefbb 
>   sharelib/pom.xml aa479a8 
>   sharelib/spark/pom.xml PRE-CREATION 
>   sharelib/spark/src/main/java/org.apache.oozie.action.hadoop/SparkMain.java 
> PRE-CREATION 
>   
> sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkActionExecutor.java
>  PRE-CREATION 
>   
> sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkMain.java
>  PRE-CREATION 
>   src/main/assemblies/sharelib.xml 4a46b90 
>   webapp/pom.xml 35776c5 
> 
> Diff: https://reviews.apache.org/r/27614/diff/
> 
> 
> Testing
> ---
> 
> Both unit testing and end to end testing done
> 
> 
> Thanks,
> 
> pavan kumar kolamuri
> 
>

[jira] [Created] (OOZIE-2070) reduce number of HCatalog access for coord latest check

2014-11-18 Thread Ryota Egashira (JIRA) 
Ryota Egashira created OOZIE-2070:
-

 Summary: reduce number of HCatalog access for coord latest check
 Key: OOZIE-2070
 URL: https://issues.apache.org/jira/browse/OOZIE-2070
 Project: Oozie
  Issue Type: Bug
Reporter: Ryota Egashira
Assignee: Ryota Egashira


in coord:latest resolution, currently Oozie accesses HCatalog every time to 
check existence of partition corresponding to each timestamp,  which overloads 
HCatalog server when no partition available and check all the way to 
initial-instance. even worse, this could continue to happen every 
CoordActionInputCheck interval.   
This jira is to do latest check in batch to reduce access to HCatalog.  



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

Re: VOTE Release Oozie 4.1.0 (candidate 1)

2014-11-18 Thread Robert Kanter 
The hadoop-2, hadoop-3, and hadoop-0.23 profiles set the pig classifier and
sqoop classifier.  As long as the user uses the same hadoop profile as what
they are running against, the sharelib will have the right pig and sqoop
jars.  e.g. If deploying with Hadoop 2, they should use the hadoop-2
profile.  If they deploy with hadoop-1 and use the hadoop-2 profile, the
sharelib will be wrong, but that's expected.

On Tue, Nov 18, 2014 at 1:23 PM, bowen zhang <
bowenzhang...@yahoo.com.invalid> wrote:

> I guess we might need to document the fact for pig to run with hadoop-2,
> you need "-Dpig.classifier=2" as a maven command line option
>
>   From: Rohini Palaniswamy 
>  To: "dev@oozie.apache.org" 
> Cc: bowen zhang 
>  Sent: Tuesday, November 18, 2014 3:27 AM
>  Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
>
> +1
>
>
>
> On Tue, Nov 18, 2014 at 2:36 AM, Ryota Egashira <
> egash...@yahoo-inc.com.invalid> wrote:
>
> > +1
> > -Built release artifact successfully
> > -ran couple of example jobs on single-node setting, which succeeded.
> >
> > Ryota
> >
> > On 11/17/14, 5:10 PM, "Robert Kanter"  wrote:
> >
> > >+1
> > >
> > >- downloaded release artifacts
> > >- built with Hadoop 1.1.1 (though ran against Hadoop 1.2.0) and ran a
> few
> > >of the examples.
> > >- built with Hadoop 2.3.0 (though ran against Hadoop some
> 2.7.0-SNAPSHOT)
> > >and ran a few of the examples.  There's something wrong with my Hadoop 2
> > >setup, but as far as I could tell, Oozie was working properly.
> > >
> > >- One thing: the release-log says that 4.1 is unrelated.  That should be
> > >removed.  While you're at it, please also fix that for 4.0.1, I
> apparently
> > >forgot to do that too :)
> > >
> > >- (And the key issue that was already mentioned should be fixed)
> > >
> > >
> > >On Mon, Nov 17, 2014 at 11:18 AM, Mohammad Islam
> > > > >> wrote:
> > >
> > >> Sorry Bowen for the delay.I'm looking into this , I never tried that.
> > >> Regards,Mohammad
> > >>
> > >>  On Monday, November 17, 2014 9:58 AM, bowen zhang
> > >>  wrote:
> > >>
> > >>
> > >>  Hi Mohammad,I think the KEY issue is the reason Mona has problem
> > >>signing
> > >> the page since I cannot commit my key to the repo. Can you resolve
> this
> > >> ASAP?Thanks,Bowen
> > >>
> > >>  From: Mona Chitnis 
> > >>  To: "dev@oozie.apache.org" ; bowen zhang <
> > >> bowenzhang...@yahoo.com>
> > >>  Sent: Monday, November 17, 2014 9:15 AM
> > >>  Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
> > >>
> > >> Downloaded the tarball, built and installed Oozie (-DskipTests) and
> ran
> > >>an
> > >> example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that.
> > >> Was unable to verify the md5 and gpg signatures. I dont find the key
> > >>used
> > >> for signing the page in the list of public keys on the KEYS page.
> Please
> > >> let me know if I'm missing the right procedure.
> > >> Regards, Mona Chitnis
> > >>
> > >>
> > >>
> > >>
> > >>On Monday, November 17, 2014 8:08 AM, Shwetha GS <
> > >> shwetha...@inmobi.com> wrote:
> > >>
> > >>
> > >>  +1
> > >>
> > >> On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang <
> > >> bowenzhang...@yahoo.com.invalid> wrote:
> > >>
> > >> > Hi,
> > >> >
> > >> > I have created a build for Oozie 4.1.0, candidate 1.
> > >> >
> > >> > Keys to verify the signature of the release artifact are available
> at
> > >> >
> > >> >  http://www.apache.org/dist/oozie/KEYS
> > >> >
> > >> > Please download, test, and try it out:
> > >> >
> > >> >  http://people.apache.org/~bzhang/oozie-4.1.0-rc1
> > >> >
> > >> > The release, md5 signature, gpg signature, and rat report can all
> > >> > be found at the above address.
> > >> >
> > >> > Vote closes on Monday EOD, the 17th.
> > >> >
> > >> > Bowen
> > >> >
> > >>
> > >> --
> > >> _
> > >> The information contained in this communication is intended solely for
> > >>the
> > >> use of the individual or entity to whom it is addressed and others
> > >> authorized to receive it. It may contain confidential or legally
> > >>privileged
> > >> information. If you are not the intended recipient you are hereby
> > >>notified
> > >> that any disclosure, copying, distribution or taking any action in
> > >>reliance
> > >> on the contents of this information is strictly prohibited and may be
> > >> unlawful. If you have received this communication in error, please
> > >>notify
> > >> us immediately by responding to this email and then delete it from
> your
> > >> system. The firm is neither liable for the proper and complete
> > >>transmission
> > >> of the information contained in this communication nor for any delay
> in
> > >>its
> > >> receipt.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> >
> >
>
>
>
>

[jira] [Updated] (OOZIE-2068) Configuration as part of sharelib

2014-11-18 Thread Purshotam Shah (JIRA) 

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

Purshotam Shah updated OOZIE-2068:
--
Summary: Configuration as part of sharelib  (was: sharelib support for conf)

> Configuration as part of sharelib
> -
>
> Key: OOZIE-2068
> URL: https://issues.apache.org/jira/browse/OOZIE-2068
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>




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

[jira] [Assigned] (OOZIE-2068) Configuration as part of sharelib

2014-11-18 Thread Purshotam Shah (JIRA) 

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

Purshotam Shah reassigned OOZIE-2068:
-

Assignee: Purshotam Shah

> Configuration as part of sharelib
> -
>
> Key: OOZIE-2068
> URL: https://issues.apache.org/jira/browse/OOZIE-2068
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>




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

[jira] [Updated] (OOZIE-2069) RecoveryService reads incorrect configuration

2014-11-18 Thread Rohini Palaniswamy (JIRA) 

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

Rohini Palaniswamy updated OOZIE-2069:
--
Description:   This causes a lot of duplicate coordinators to be created 
for a submitted bundle. Found by [~mchiang_4w...@yahoo.com] with the regression 
tests.
Summary: RecoveryService reads incorrect configuration   (was: 
RecoveryService reads incorrect configuration)

+1. Thanks Puru for figuring this one out. Simple fix but you had to spend a 
lot of time to figure out the cause.

> RecoveryService reads incorrect configuration 
> --
>
> Key: OOZIE-2069
> URL: https://issues.apache.org/jira/browse/OOZIE-2069
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
> Attachments: OOZIE-2069-V1.patch
>
>
>   This causes a lot of duplicate coordinators to be created for a submitted 
> bundle. Found by [~mchiang_4w...@yahoo.com] with the regression tests.



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

[jira] [Commented] (OOZIE-2069) RecoveryService reads incorrect configuration

2014-11-18 Thread Purshotam Shah (JIRA) 

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

Purshotam Shah commented on OOZIE-2069:
---

Minor fix, doesn't need UTC.

> RecoveryService reads incorrect configuration
> -
>
> Key: OOZIE-2069
> URL: https://issues.apache.org/jira/browse/OOZIE-2069
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
> Attachments: OOZIE-2069-V1.patch
>
>




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

[jira] [Updated] (OOZIE-2069) RecoveryService reads incorrect configuration

2014-11-18 Thread Purshotam Shah (JIRA) 

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

Purshotam Shah updated OOZIE-2069:
--
Attachment: OOZIE-2069-V1.patch

> RecoveryService reads incorrect configuration
> -
>
> Key: OOZIE-2069
> URL: https://issues.apache.org/jira/browse/OOZIE-2069
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
> Attachments: OOZIE-2069-V1.patch
>
>




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

[jira] [Assigned] (OOZIE-2069) RecoveryService reads incorrect configuration

2014-11-18 Thread Purshotam Shah (JIRA) 

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

Purshotam Shah reassigned OOZIE-2069:
-

Assignee: Purshotam Shah

> RecoveryService reads incorrect configuration
> -
>
> Key: OOZIE-2069
> URL: https://issues.apache.org/jira/browse/OOZIE-2069
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
> Attachments: OOZIE-2069-V1.patch
>
>




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

[jira] [Created] (OOZIE-2069) RecoveryService reads incorrect configuration

2014-11-18 Thread Purshotam Shah (JIRA) 
Purshotam Shah created OOZIE-2069:
-

 Summary: RecoveryService reads incorrect configuration
 Key: OOZIE-2069
 URL: https://issues.apache.org/jira/browse/OOZIE-2069
 Project: Oozie
  Issue Type: Bug
Reporter: Purshotam Shah






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

[jira] [Updated] (OOZIE-1770) Create Oozie Application Master for YARN

2014-11-18 Thread Robert Kanter (JIRA) 

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

Robert Kanter updated OOZIE-1770:
-
Attachment: oya.patch
oya-rm-screenshot.jpg

We did the code against CDH, but I was able to port it back over to Apache 
trunk without conflicts other than pom changes.  I decided that it was better 
to make this available sooner rather than spend too much time spiffying it up.

Here’s a brief overview of the design:
Oozie has an unmanaged AM “pool” that it uses for submitting jobs.  We need a 
pool because we have to create an AM for each user that submits a job (we 
adapted some code from Llama).  When Oozie wants to submit a job, instead of 
submitting an MR launcher job, it can create/get one of these AM’s and use it 
to create a Yarn container, and then run the launcher in that container.  
During our testing, we were using a Java action that launches a simple MR job.  
In the screenshot below, you can see that we have the one “OozieServer” AM, and 
then 3 MAPREDUCE applications, from when we ran the workflow 3 times.  The 
OozieServer AM was reused each time to submit the MR jobs, and there’s no 
longer a Launcher Job.
!oya-rm-screenshot.jpg!

Given that this was more of a proof-of-concept and we didn’t have a lot of 
time, we didn’t redo the launcher code.  It still uses LauncherMapper; I just 
hacked in some extra methods for running it outside of a map task so we could 
run it in the container.  This is definitely an area where we can improve 
things a lot.  One major thing to keep in mind is that the container gives us a 
Shell; right now, we’re then starting a JVM to run the LauncherMapper code, but 
it probably would make sense to see if we can skip the JVM and run most actions 
directly in the shell.

Interestingly, running a Container that doesn’t do much (e.g. a “Hello World” 
Java action), runs so fast, that Oozie is now the bottleneck.  The callback 
comes in before the action has a chance to transition to RUNNING, so Oozie 
complains.  We fixed this by adding a delay.  We’ll probably want to improve 
this.

I had to remove MR1 support, obviously.  This greatly simplifies the build 
because we don’t need hadooplibs anymore.  I also had to up the Hadoop version 
to 2.4.0+ from 2.3.0.

We can probably get rid of this eventually, but for now, I made it so that if 
you set {{ooze.use.jobclient.launch=true}} in oozie-site, Oozie will use the 
old MR launcher job behavior instead of the container behavior.

Here’s a to do list of things that need to be fixed or improved:
- The container currently runs as the Yarn user regardless of who submitted the 
workflow.  So, permissions-wise, workflows only work if you submit them as the 
Yarn user.  
- The shell action should not start a JVM
- Actions should be refactored/cleaned-up/simplified to not need all the stuff 
LauncherMapper is doing
-- Regardless of whether or not we still start a JVM, there’s a bunch 
of stuff LauncherMapper does that we should get rid of or simplify or change
-- The Shell action definitely doesn’t need a JVM; once the user 
problem is fixed, it should also finally run as the proper user!
- The NMToken expires after 10-15min and you can’t submit containers anymore 
from the AM’s in the AM pool
- The Oozie kill command still expects an MR job and doesn’t work; it needs to 
use the container id
- The status checking code is pretty hacky.  I modified it to check the 
container status, but it doesn’t check if the job actually failed or not
- The callback is pretty hacky.  The Launcher’s MR AM was sending the callback 
to Oozie before.  I had to make the container do this now
-- It may make sense to come up with a different mechanism for this
- I haven’t tried any recovery stuff or Oozie HA
- I had to add two columns: one to store node Id host and one to store node Id 
port.  OozieDBCLI needs to be updated to create these during an upgrade.  
Creating a new database works fine though because OpenJPA handles it.
- We’ve only tested with the Java action.  Most of the other actions should 
work with some minor tweaking (need to set expected extra env vars, etc).  The 
MR action probably won’t work because of the swapping optimization; it probably 
makes sense to get rid of that.

The oya.patch has all of the changes.

> Create Oozie Application Master for YARN
> 
>
> Key: OOZIE-1770
> URL: https://issues.apache.org/jira/browse/OOZIE-1770
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Bowen Zhang
>Assignee: Bowen Zhang
> Attachments: oya-rm-screenshot.jpg, oya.patch
>
>
> After the first release of oozie on hadoop 2, it will be good if users can 
> set execution engine in oozie conf, be it YARN AM or traditional MR. We can 
> target this for post oozie 4.1 release.



-

Re: VOTE Release Oozie 4.1.0 (candidate 1)

2014-11-18 Thread bowen zhang 
I guess we might need to document the fact for pig to run with hadoop-2, you 
need "-Dpig.classifier=2" as a maven command line option

  From: Rohini Palaniswamy 
 To: "dev@oozie.apache.org"  
Cc: bowen zhang  
 Sent: Tuesday, November 18, 2014 3:27 AM
 Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
   
+1



On Tue, Nov 18, 2014 at 2:36 AM, Ryota Egashira <
egash...@yahoo-inc.com.invalid> wrote:

> +1
> -Built release artifact successfully
> -ran couple of example jobs on single-node setting, which succeeded.
>
> Ryota
>
> On 11/17/14, 5:10 PM, "Robert Kanter"  wrote:
>
> >+1
> >
> >- downloaded release artifacts
> >- built with Hadoop 1.1.1 (though ran against Hadoop 1.2.0) and ran a few
> >of the examples.
> >- built with Hadoop 2.3.0 (though ran against Hadoop some 2.7.0-SNAPSHOT)
> >and ran a few of the examples.  There's something wrong with my Hadoop 2
> >setup, but as far as I could tell, Oozie was working properly.
> >
> >- One thing: the release-log says that 4.1 is unrelated.  That should be
> >removed.  While you're at it, please also fix that for 4.0.1, I apparently
> >forgot to do that too :)
> >
> >- (And the key issue that was already mentioned should be fixed)
> >
> >
> >On Mon, Nov 17, 2014 at 11:18 AM, Mohammad Islam
> > >> wrote:
> >
> >> Sorry Bowen for the delay.I'm looking into this , I never tried that.
> >> Regards,Mohammad
> >>
> >>      On Monday, November 17, 2014 9:58 AM, bowen zhang
> >>  wrote:
> >>
> >>
> >>  Hi Mohammad,I think the KEY issue is the reason Mona has problem
> >>signing
> >> the page since I cannot commit my key to the repo. Can you resolve this
> >> ASAP?Thanks,Bowen
> >>
> >>      From: Mona Chitnis 
> >>  To: "dev@oozie.apache.org" ; bowen zhang <
> >> bowenzhang...@yahoo.com>
> >>  Sent: Monday, November 17, 2014 9:15 AM
> >>  Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
> >>
> >> Downloaded the tarball, built and installed Oozie (-DskipTests) and ran
> >>an
> >> example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that.
> >> Was unable to verify the md5 and gpg signatures. I dont find the key
> >>used
> >> for signing the page in the list of public keys on the KEYS page. Please
> >> let me know if I'm missing the right procedure.
> >> Regards, Mona Chitnis
> >>
> >>
> >>
> >>
> >>    On Monday, November 17, 2014 8:08 AM, Shwetha GS <
> >> shwetha...@inmobi.com> wrote:
> >>
> >>
> >>  +1
> >>
> >> On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang <
> >> bowenzhang...@yahoo.com.invalid> wrote:
> >>
> >> > Hi,
> >> >
> >> > I have created a build for Oozie 4.1.0, candidate 1.
> >> >
> >> > Keys to verify the signature of the release artifact are available at
> >> >
> >> >  http://www.apache.org/dist/oozie/KEYS
> >> >
> >> > Please download, test, and try it out:
> >> >
> >> >  http://people.apache.org/~bzhang/oozie-4.1.0-rc1
> >> >
> >> > The release, md5 signature, gpg signature, and rat report can all
> >> > be found at the above address.
> >> >
> >> > Vote closes on Monday EOD, the 17th.
> >> >
> >> > Bowen
> >> >
> >>
> >> --
> >> _
> >> The information contained in this communication is intended solely for
> >>the
> >> use of the individual or entity to whom it is addressed and others
> >> authorized to receive it. It may contain confidential or legally
> >>privileged
> >> information. If you are not the intended recipient you are hereby
> >>notified
> >> that any disclosure, copying, distribution or taking any action in
> >>reliance
> >> on the contents of this information is strictly prohibited and may be
> >> unlawful. If you have received this communication in error, please
> >>notify
> >> us immediately by responding to this email and then delete it from your
> >> system. The firm is neither liable for the proper and complete
> >>transmission
> >> of the information contained in this communication nor for any delay in
> >>its
> >> receipt.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
>

Re: VOTE Release Oozie 4.1.0 (candidate 1)

2014-11-18 Thread bowen zhang 
Hi folks,I have one last concern about oozie-pig workflow. The user is free to 
build oozie.war with both hadoop-1 and hadoop-2 jars. However, how can a user 
build sharelib pig with the right pig classifier with the right hadoop cluster? 
I don't think the user can go into pom.xml to change the version of pig 
classifier. Or do we expect the user to pass the value via command line when 
doing maven install?thanks,Bowen

  From: Rohini Palaniswamy 
 To: "dev@oozie.apache.org"  
Cc: bowen zhang  
 Sent: Tuesday, November 18, 2014 3:27 AM
 Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
   
+1



On Tue, Nov 18, 2014 at 2:36 AM, Ryota Egashira <
egash...@yahoo-inc.com.invalid> wrote:

> +1
> -Built release artifact successfully
> -ran couple of example jobs on single-node setting, which succeeded.
>
> Ryota
>
> On 11/17/14, 5:10 PM, "Robert Kanter"  wrote:
>
> >+1
> >
> >- downloaded release artifacts
> >- built with Hadoop 1.1.1 (though ran against Hadoop 1.2.0) and ran a few
> >of the examples.
> >- built with Hadoop 2.3.0 (though ran against Hadoop some 2.7.0-SNAPSHOT)
> >and ran a few of the examples.  There's something wrong with my Hadoop 2
> >setup, but as far as I could tell, Oozie was working properly.
> >
> >- One thing: the release-log says that 4.1 is unrelated.  That should be
> >removed.  While you're at it, please also fix that for 4.0.1, I apparently
> >forgot to do that too :)
> >
> >- (And the key issue that was already mentioned should be fixed)
> >
> >
> >On Mon, Nov 17, 2014 at 11:18 AM, Mohammad Islam
> > >> wrote:
> >
> >> Sorry Bowen for the delay.I'm looking into this , I never tried that.
> >> Regards,Mohammad
> >>
> >>      On Monday, November 17, 2014 9:58 AM, bowen zhang
> >>  wrote:
> >>
> >>
> >>  Hi Mohammad,I think the KEY issue is the reason Mona has problem
> >>signing
> >> the page since I cannot commit my key to the repo. Can you resolve this
> >> ASAP?Thanks,Bowen
> >>
> >>      From: Mona Chitnis 
> >>  To: "dev@oozie.apache.org" ; bowen zhang <
> >> bowenzhang...@yahoo.com>
> >>  Sent: Monday, November 17, 2014 9:15 AM
> >>  Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
> >>
> >> Downloaded the tarball, built and installed Oozie (-DskipTests) and ran
> >>an
> >> example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that.
> >> Was unable to verify the md5 and gpg signatures. I dont find the key
> >>used
> >> for signing the page in the list of public keys on the KEYS page. Please
> >> let me know if I'm missing the right procedure.
> >> Regards, Mona Chitnis
> >>
> >>
> >>
> >>
> >>    On Monday, November 17, 2014 8:08 AM, Shwetha GS <
> >> shwetha...@inmobi.com> wrote:
> >>
> >>
> >>  +1
> >>
> >> On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang <
> >> bowenzhang...@yahoo.com.invalid> wrote:
> >>
> >> > Hi,
> >> >
> >> > I have created a build for Oozie 4.1.0, candidate 1.
> >> >
> >> > Keys to verify the signature of the release artifact are available at
> >> >
> >> >  http://www.apache.org/dist/oozie/KEYS
> >> >
> >> > Please download, test, and try it out:
> >> >
> >> >  http://people.apache.org/~bzhang/oozie-4.1.0-rc1
> >> >
> >> > The release, md5 signature, gpg signature, and rat report can all
> >> > be found at the above address.
> >> >
> >> > Vote closes on Monday EOD, the 17th.
> >> >
> >> > Bowen
> >> >
> >>
> >> --
> >> _
> >> The information contained in this communication is intended solely for
> >>the
> >> use of the individual or entity to whom it is addressed and others
> >> authorized to receive it. It may contain confidential or legally
> >>privileged
> >> information. If you are not the intended recipient you are hereby
> >>notified
> >> that any disclosure, copying, distribution or taking any action in
> >>reliance
> >> on the contents of this information is strictly prohibited and may be
> >> unlawful. If you have received this communication in error, please
> >>notify
> >> us immediately by responding to this email and then delete it from your
> >> system. The firm is neither liable for the proper and complete
> >>transmission
> >> of the information contained in this communication nor for any delay in
> >>its
> >> receipt.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
>

[jira] [Updated] (OOZIE-2028) Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true

2014-11-18 Thread Jaydeep Vishwakarma (JIRA) 

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

Jaydeep Vishwakarma updated OOZIE-2028:
---
Description: 
1. Coord action re-run will take an addition optional flag -failed which re-run 
only the failed nodes. This will re-run the existing workflow with 
RERUN_FAIL_NODES=true. But this will also honour coord concurrency.
2. Coord action re-run with no -failed option will use the existing feature of 
launching new workflow.

  was:
1. Coord action re-run takes an addition optional flag -failed which re-runs 
only the failed nodes. This will re-run the existing workflow with 
RERUN_FAIL_NODES=true. But this will also honour coord concurrency.
2. Coord action re-run with no -failed option will use the existing feature of 
launching new workflow.


> Coord action rerun with -failed option should rerun existing workflow with 
> RERUN_FAIL_NODES=true
> 
>
> Key: OOZIE-2028
> URL: https://issues.apache.org/jira/browse/OOZIE-2028
> Project: Oozie
>  Issue Type: Sub-task
>  Components: workflow
>Affects Versions: trunk
>Reporter: Jaydeep Vishwakarma
>Assignee: Jaydeep Vishwakarma
>
> 1. Coord action re-run will take an addition optional flag -failed which 
> re-run only the failed nodes. This will re-run the existing workflow with 
> RERUN_FAIL_NODES=true. But this will also honour coord concurrency.
> 2. Coord action re-run with no -failed option will use the existing feature 
> of launching new workflow.



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

Re: VOTE Release Oozie 4.1.0 (candidate 1)

2014-11-18 Thread Rohini Palaniswamy 
+1

On Tue, Nov 18, 2014 at 2:36 AM, Ryota Egashira <
egash...@yahoo-inc.com.invalid> wrote:

> +1
> -Built release artifact successfully
> -ran couple of example jobs on single-node setting, which succeeded.
>
> Ryota
>
> On 11/17/14, 5:10 PM, "Robert Kanter"  wrote:
>
> >+1
> >
> >- downloaded release artifacts
> >- built with Hadoop 1.1.1 (though ran against Hadoop 1.2.0) and ran a few
> >of the examples.
> >- built with Hadoop 2.3.0 (though ran against Hadoop some 2.7.0-SNAPSHOT)
> >and ran a few of the examples.  There's something wrong with my Hadoop 2
> >setup, but as far as I could tell, Oozie was working properly.
> >
> >- One thing: the release-log says that 4.1 is unrelated.  That should be
> >removed.  While you're at it, please also fix that for 4.0.1, I apparently
> >forgot to do that too :)
> >
> >- (And the key issue that was already mentioned should be fixed)
> >
> >
> >On Mon, Nov 17, 2014 at 11:18 AM, Mohammad Islam
> > >> wrote:
> >
> >> Sorry Bowen for the delay.I'm looking into this , I never tried that.
> >> Regards,Mohammad
> >>
> >>  On Monday, November 17, 2014 9:58 AM, bowen zhang
> >>  wrote:
> >>
> >>
> >>  Hi Mohammad,I think the KEY issue is the reason Mona has problem
> >>signing
> >> the page since I cannot commit my key to the repo. Can you resolve this
> >> ASAP?Thanks,Bowen
> >>
> >>   From: Mona Chitnis 
> >>  To: "dev@oozie.apache.org" ; bowen zhang <
> >> bowenzhang...@yahoo.com>
> >>  Sent: Monday, November 17, 2014 9:15 AM
> >>  Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
> >>
> >> Downloaded the tarball, built and installed Oozie (-DskipTests) and ran
> >>an
> >> example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that.
> >> Was unable to verify the md5 and gpg signatures. I dont find the key
> >>used
> >> for signing the page in the list of public keys on the KEYS page. Please
> >> let me know if I'm missing the right procedure.
> >> Regards, Mona Chitnis
> >>
> >>
> >>
> >>
> >> On Monday, November 17, 2014 8:08 AM, Shwetha GS <
> >> shwetha...@inmobi.com> wrote:
> >>
> >>
> >>  +1
> >>
> >> On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang <
> >> bowenzhang...@yahoo.com.invalid> wrote:
> >>
> >> > Hi,
> >> >
> >> > I have created a build for Oozie 4.1.0, candidate 1.
> >> >
> >> > Keys to verify the signature of the release artifact are available at
> >> >
> >> >  http://www.apache.org/dist/oozie/KEYS
> >> >
> >> > Please download, test, and try it out:
> >> >
> >> >  http://people.apache.org/~bzhang/oozie-4.1.0-rc1
> >> >
> >> > The release, md5 signature, gpg signature, and rat report can all
> >> > be found at the above address.
> >> >
> >> > Vote closes on Monday EOD, the 17th.
> >> >
> >> > Bowen
> >> >
> >>
> >> --
> >> _
> >> The information contained in this communication is intended solely for
> >>the
> >> use of the individual or entity to whom it is addressed and others
> >> authorized to receive it. It may contain confidential or legally
> >>privileged
> >> information. If you are not the intended recipient you are hereby
> >>notified
> >> that any disclosure, copying, distribution or taking any action in
> >>reliance
> >> on the contents of this information is strictly prohibited and may be
> >> unlawful. If you have received this communication in error, please
> >>notify
> >> us immediately by responding to this email and then delete it from your
> >> system. The firm is neither liable for the proper and complete
> >>transmission
> >> of the information contained in this communication nor for any delay in
> >>its
> >> receipt.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
>

[jira] [Updated] (OOZIE-2028) Coord action rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true

2014-11-18 Thread Jaydeep Vishwakarma (JIRA) 

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

Jaydeep Vishwakarma updated OOZIE-2028:
---
Summary: Coord action rerun with -failed option should rerun existing 
workflow with RERUN_FAIL_NODES=true  (was: Rerun with -failed option should 
rerun existing workflow with RERUN_FAIL_NODES=true)

> Coord action rerun with -failed option should rerun existing workflow with 
> RERUN_FAIL_NODES=true
> 
>
> Key: OOZIE-2028
> URL: https://issues.apache.org/jira/browse/OOZIE-2028
> Project: Oozie
>  Issue Type: Sub-task
>  Components: workflow
>Affects Versions: trunk
>Reporter: Jaydeep Vishwakarma
>Assignee: Jaydeep Vishwakarma
>
> 1. Coord action re-run takes an addition optional flag -failed which re-runs 
> only the failed nodes. This will re-run the existing workflow with 
> RERUN_FAIL_NODES=true. But this will also honour coord concurrency.
> 2. Coord action re-run with no -failed option will use the existing feature 
> of launching new workflow.



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

Re: VOTE Release Oozie 4.1.0 (candidate 1)

2014-11-18 Thread Ryota Egashira 
+1 
-Built release artifact successfully
-ran couple of example jobs on single-node setting, which succeeded.

Ryota

On 11/17/14, 5:10 PM, "Robert Kanter"  wrote:

>+1
>
>- downloaded release artifacts
>- built with Hadoop 1.1.1 (though ran against Hadoop 1.2.0) and ran a few
>of the examples.
>- built with Hadoop 2.3.0 (though ran against Hadoop some 2.7.0-SNAPSHOT)
>and ran a few of the examples.  There's something wrong with my Hadoop 2
>setup, but as far as I could tell, Oozie was working properly.
>
>- One thing: the release-log says that 4.1 is unrelated.  That should be
>removed.  While you're at it, please also fix that for 4.0.1, I apparently
>forgot to do that too :)
>
>- (And the key issue that was already mentioned should be fixed)
>
>
>On Mon, Nov 17, 2014 at 11:18 AM, Mohammad Islam
>> wrote:
>
>> Sorry Bowen for the delay.I'm looking into this , I never tried that.
>> Regards,Mohammad
>>
>>  On Monday, November 17, 2014 9:58 AM, bowen zhang
>>  wrote:
>>
>>
>>  Hi Mohammad,I think the KEY issue is the reason Mona has problem
>>signing
>> the page since I cannot commit my key to the repo. Can you resolve this
>> ASAP?Thanks,Bowen
>>
>>   From: Mona Chitnis 
>>  To: "dev@oozie.apache.org" ; bowen zhang <
>> bowenzhang...@yahoo.com>
>>  Sent: Monday, November 17, 2014 9:15 AM
>>  Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1)
>>
>> Downloaded the tarball, built and installed Oozie (-DskipTests) and ran
>>an
>> example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that.
>> Was unable to verify the md5 and gpg signatures. I dont find the key
>>used
>> for signing the page in the list of public keys on the KEYS page. Please
>> let me know if I'm missing the right procedure.
>> Regards, Mona Chitnis
>>
>>
>>
>>
>> On Monday, November 17, 2014 8:08 AM, Shwetha GS <
>> shwetha...@inmobi.com> wrote:
>>
>>
>>  +1
>>
>> On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang <
>> bowenzhang...@yahoo.com.invalid> wrote:
>>
>> > Hi,
>> >
>> > I have created a build for Oozie 4.1.0, candidate 1.
>> >
>> > Keys to verify the signature of the release artifact are available at
>> >
>> >  http://www.apache.org/dist/oozie/KEYS
>> >
>> > Please download, test, and try it out:
>> >
>> >  http://people.apache.org/~bzhang/oozie-4.1.0-rc1
>> >
>> > The release, md5 signature, gpg signature, and rat report can all
>> > be found at the above address.
>> >
>> > Vote closes on Monday EOD, the 17th.
>> >
>> > Bowen
>> >
>>
>> --
>> _
>> The information contained in this communication is intended solely for
>>the
>> use of the individual or entity to whom it is addressed and others
>> authorized to receive it. It may contain confidential or legally
>>privileged
>> information. If you are not the intended recipient you are hereby
>>notified
>> that any disclosure, copying, distribution or taking any action in
>>reliance
>> on the contents of this information is strictly prohibited and may be
>> unlawful. If you have received this communication in error, please
>>notify
>> us immediately by responding to this email and then delete it from your
>> system. The firm is neither liable for the proper and complete
>>transmission
>> of the information contained in this communication nor for any delay in
>>its
>> receipt.
>>
>>
>>
>>
>>
>>
>>
>>

Review Request 28136: OOZIE-2068 - sharelib support for conf

2014-11-18 Thread Purshotam Shah 

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

Review request for oozie.


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


Repository: oozie-git


Description
---

OOZIE-2068 - sharelib support for conf


Diffs
-

  core/src/main/java/org/apache/oozie/action/hadoop/Hive2ActionExecutor.java 
d70c3e1 
  core/src/main/java/org/apache/oozie/action/hadoop/HiveActionExecutor.java 
832bbe6 
  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
fd1a98b 
  core/src/main/java/org/apache/oozie/service/ShareLibService.java b408549 
  core/src/main/resources/oozie-default.xml 19cae9d 
  core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
48166a5 
  core/src/test/java/org/apache/oozie/service/TestHAShareLibService.java 
d2ad881 
  core/src/test/java/org/apache/oozie/service/TestShareLibService.java f261448 
  tools/src/test/java/org/apache/oozie/tools/TestOozieSharelibCLI.java a76014c 

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


Testing
---


Thanks,

Purshotam Shah

[jira] [Created] (OOZIE-2068) sharelib support for conf

2014-11-18 Thread Purshotam Shah (JIRA) 
Purshotam Shah created OOZIE-2068:
-

 Summary: sharelib support for conf
 Key: OOZIE-2068
 URL: https://issues.apache.org/jira/browse/OOZIE-2068
 Project: Oozie
  Issue Type: Bug
Reporter: Purshotam Shah






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