date:20170502

Build failed in Jenkins: oozie-trunk-find-patches-available #157456

2017-05-02 Thread Apache Jenkins Server

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision eb168360c550943828d9fe2c7bfdcd4f5e830003 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f eb168360c550943828d9fe2c7bfdcd4f5e830003
 > git rev-list eb168360c550943828d9fe2c7bfdcd4f5e830003 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson6369986806560561919.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0100 
901120 901120 0  96231  0 --:--:-- --:--:-- --:--:-- 96170
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : oozie-trunk-find-patches-available #157457

2017-05-02 Thread Apache Jenkins Server

See

[jira] [Created] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable in order to provide alternative implementations

2017-05-02 Thread Andras Piros (JIRA)

Andras Piros created OOZIE-2874:
---

 Summary: Make the Launcher Mapper map-only job's InputFormat class 
pluggable in order to provide alternative implementations
 Key: OOZIE-2874
 URL: https://issues.apache.org/jira/browse/OOZIE-2874
 Project: Oozie
  Issue Type: Improvement
Affects Versions: 4.3.0
Reporter: Andras Piros
Assignee: Andras Piros
 Fix For: 5.0.0


In order to prepare for YARN's [*rack-schedulable AM feature*|YARN-6050], and 
[*its MapReduce counterpart*|MAPREDUCE-6871], let's have the possibility of 
making the Launcher Mapper map-only job's {{InputFormat}} class pluggable in 
order to provide alternative implementations that can behave differently from 
[{{OozieLauncherInputFormat}}|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/OozieLauncherInputFormat.java]
 that does not request any HDFS resources.



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

[jira] [Updated] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable in order to provide alternative implementations

2017-05-02 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2874:

Description: In order to prepare for YARN's [*rack-schedulable AM 
feature*|YARN-6050], and [*its MapReduce counterpart*|MAPREDUCE-6871], let's 
have the possibility of making the Launcher Mapper map-only job's 
[{{InputFormat}}|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java]
 class pluggable in order to provide alternative implementations that can 
behave differently from 
[{{OozieLauncherInputFormat}}|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/OozieLauncherInputFormat.java]
 that does not request any HDFS resources.  (was: In order to prepare for 
YARN's [*rack-schedulable AM feature*|YARN-6050], and [*its MapReduce 
counterpart*|MAPREDUCE-6871], let's have the possibility of making the Launcher 
Mapper map-only job's {{InputFormat}} class pluggable in order to provide 
alternative implementations that can behave differently from 
[{{OozieLauncherInputFormat}}|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/OozieLauncherInputFormat.java]
 that does not request any HDFS resources.)

> Make the Launcher Mapper map-only job's InputFormat class pluggable in order 
> to provide alternative implementations
> ---
>
> Key: OOZIE-2874
> URL: https://issues.apache.org/jira/browse/OOZIE-2874
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
>
> In order to prepare for YARN's [*rack-schedulable AM feature*|YARN-6050], and 
> [*its MapReduce counterpart*|MAPREDUCE-6871], let's have the possibility of 
> making the Launcher Mapper map-only job's 
> [{{InputFormat}}|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java]
>  class pluggable in order to provide alternative implementations that can 
> behave differently from 
> [{{OozieLauncherInputFormat}}|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/OozieLauncherInputFormat.java]
>  that does not request any HDFS resources.



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

[jira] [Updated] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable

2017-05-02 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2874:

Summary: Make the Launcher Mapper map-only job's InputFormat class 
pluggable  (was: Make the Launcher Mapper map-only job's InputFormat class 
pluggable in order to provide alternative implementations)

> Make the Launcher Mapper map-only job's InputFormat class pluggable
> ---
>
> Key: OOZIE-2874
> URL: https://issues.apache.org/jira/browse/OOZIE-2874
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
>
> In order to prepare for YARN's [*rack-schedulable AM feature*|YARN-6050], and 
> [*its MapReduce counterpart*|MAPREDUCE-6871], let's have the possibility of 
> making the Launcher Mapper map-only job's 
> [{{InputFormat}}|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java]
>  class pluggable in order to provide alternative implementations that can 
> behave differently from 
> [{{OozieLauncherInputFormat}}|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/OozieLauncherInputFormat.java]
>  that does not request any HDFS resources.



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

[jira] [Updated] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable

2017-05-02 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2874:

Attachment: OOZIE-2874.001.patch

> Make the Launcher Mapper map-only job's InputFormat class pluggable
> ---
>
> Key: OOZIE-2874
> URL: https://issues.apache.org/jira/browse/OOZIE-2874
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-2874.001.patch
>
>
> In order to prepare for YARN's [*rack-schedulable AM feature*|YARN-6050], and 
> [*its MapReduce counterpart*|MAPREDUCE-6871], let's have the possibility of 
> making the Launcher Mapper map-only job's 
> [{{InputFormat}}|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java]
>  class pluggable in order to provide alternative implementations that can 
> behave differently from 
> [{{OozieLauncherInputFormat}}|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/OozieLauncherInputFormat.java]
>  that does not request any HDFS resources.



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

[jira] [Updated] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable

2017-05-02 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2874:

Fix Version/s: (was: 5.0.0)

> Make the Launcher Mapper map-only job's InputFormat class pluggable
> ---
>
> Key: OOZIE-2874
> URL: https://issues.apache.org/jira/browse/OOZIE-2874
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Attachments: OOZIE-2874.001.patch
>
>
> In order to prepare for YARN's [*rack-schedulable AM feature*|YARN-6050], and 
> [*its MapReduce counterpart*|MAPREDUCE-6871], let's have the possibility of 
> making the Launcher Mapper map-only job's 
> [{{InputFormat}}|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java]
>  class pluggable in order to provide alternative implementations that can 
> behave differently from 
> [{{OozieLauncherInputFormat}}|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/OozieLauncherInputFormat.java]
>  that does not request any HDFS resources.



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

[jira] [Updated] (OOZIE-2870) non working examples in oozie documentation coordinator spec

2017-05-02 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2870:

Attachment: OOZIE-2870.001.patch

> non working examples in oozie documentation coordinator spec
> 
>
> Key: OOZIE-2870
> URL: https://issues.apache.org/jira/browse/OOZIE-2870
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Clemens Valiente
>Assignee: Andras Piros
>  Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-2870.001.patch
>
>
> in the chapters:
> 4.4.1.2. The coord:endOfDays(int n) EL function
> https://oozie.apache.org/docs/4.3.0/CoordinatorFunctionalSpec.html#a4.4.1.2._The_coord:endOfDaysint_n_EL_function
> 4.4.2.2. The coord:endOfMonths(int n) EL function
> https://oozie.apache.org/docs/4.3.0/CoordinatorFunctionalSpec.html#a4.4.2.2._The_coord:endOfMonthsint_n_EL_function
> there is a hello world coordinator example:
> {code:xml}
>start="2009-01-02T08:00Z" end="2009-01-04T08:00Z" 
> timezone="America/Los_Angeles"
>  xmlns="uri:oozie:coordinator:0.1">
>   
> 10
> ${concurrency_level}
> ${execution_order}
> ${materialization_throttle}
>   
> ...{code}
> The throttle element does not exist for the oozie:coordinator specification 
> 0.1 so the version should probably be updated here.



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

[jira] [Assigned] (OOZIE-2870) non working examples in oozie documentation coordinator spec

2017-05-02 Thread Andras Piros (JIRA)


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

Andras Piros reassigned OOZIE-2870:
---

Assignee: Andras Piros

> non working examples in oozie documentation coordinator spec
> 
>
> Key: OOZIE-2870
> URL: https://issues.apache.org/jira/browse/OOZIE-2870
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Clemens Valiente
>Assignee: Andras Piros
>  Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-2870.001.patch
>
>
> in the chapters:
> 4.4.1.2. The coord:endOfDays(int n) EL function
> https://oozie.apache.org/docs/4.3.0/CoordinatorFunctionalSpec.html#a4.4.1.2._The_coord:endOfDaysint_n_EL_function
> 4.4.2.2. The coord:endOfMonths(int n) EL function
> https://oozie.apache.org/docs/4.3.0/CoordinatorFunctionalSpec.html#a4.4.2.2._The_coord:endOfMonthsint_n_EL_function
> there is a hello world coordinator example:
> {code:xml}
>start="2009-01-02T08:00Z" end="2009-01-04T08:00Z" 
> timezone="America/Los_Angeles"
>  xmlns="uri:oozie:coordinator:0.1">
>   
> 10
> ${concurrency_level}
> ${execution_order}
> ${materialization_throttle}
>   
> ...{code}
> The throttle element does not exist for the oozie:coordinator specification 
> 0.1 so the version should probably be updated here.



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

[jira] [Commented] (OOZIE-2751) LocalOozieClient is missing methods from OozieClient

2017-05-02 Thread Abhishek Bafna (JIRA)


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

Abhishek Bafna commented on OOZIE-2751:
---

Ping [~pbacsko], [~gezapeti].

> LocalOozieClient is missing methods from OozieClient
> 
>
> Key: OOZIE-2751
> URL: https://issues.apache.org/jira/browse/OOZIE-2751
> Project: Oozie
>  Issue Type: Bug
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2751-00.patch, OOZIE-2751-01.patch, 
> OOZIE-2751-02.patch, OOZIE-2751-03.patch, OOZIE-2751-04.patch, 
> OOZIE-2751-05.patch, OOZIE-2751-06.patch, OOZIE-2751-07.patch, 
> OOZIE-2751-08.patch
>
>
> {{LocalOozieClient}} works by wrapping direct calls to {{DagEngine}} in the 
> normal {{OozieClient}} methods instead of making REST calls to an Oozie 
> Server.  However, it currently doesn't override all methods, which means you 
> hit the {{OozieClient}} implementation, which tries to make a REST call and 
> will fail (because it's not setup for that).  For example, {{getStatus(String 
> jobId)}} isn't overridden, and doesn't work when used from 
> {{LocalOozieClient}}.
> We should also create a test that verifies that all methods are overridden.



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

[jira] [Commented] (OOZIE-2870) non working examples in oozie documentation coordinator spec

2017-05-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2870:
--

Testing JIRA OOZIE-2870

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{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: 1932
{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/3798/

> non working examples in oozie documentation coordinator spec
> 
>
> Key: OOZIE-2870
> URL: https://issues.apache.org/jira/browse/OOZIE-2870
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Clemens Valiente
>Assignee: Andras Piros
>  Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-2870.001.patch
>
>
> in the chapters:
> 4.4.1.2. The coord:endOfDays(int n) EL function
> https://oozie.apache.org/docs/4.3.0/CoordinatorFunctionalSpec.html#a4.4.1.2._The_coord:endOfDaysint_n_EL_function
> 4.4.2.2. The coord:endOfMonths(int n) EL function
> https://oozie.apache.org/docs/4.3.0/CoordinatorFunctionalSpec.html#a4.4.2.2._The_coord:endOfMonthsint_n_EL_function
> there is a hello world coordinator example:
> {code:xml}
>start="2009-01-02T08:00Z" end="2009-01-04T08:00Z" 
> timezone="America/Los_Angeles"
>  xmlns="uri:oozie:coordinator:0.1">
>   
> 10
> ${concurrency_level}
> ${execution_order}
> ${materialization_throttle}
>   
> ...{code}
> The throttle element does not exist for the oozie:coordinator specification 
> 0.1 so the version should probably be updated here.



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

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

2017-05-02 Thread Apache Jenkins Server

See 


--
[...truncated 921.69 KB...]
[INFO] Copying jetty-schemas-3.1.M0.jar to 

[INFO] Copying hadoop-annotations-2.4.0.jar to 

[INFO] Copying xbean-asm5-shaded-3.17.jar to 

[INFO] Copying oozie-client-4.4.0-SNAPSHOT.jar to 

[INFO] Copying serp-1.15.1.jar to 

[INFO] Copying asm-5.0.1.jar to 

[INFO] Copying openjpa-lib-2.4.1.jar to 

[INFO] Copying opencsv-2.3.jar to 

[INFO] Copying jasper-runtime-5.5.23.jar to 

[INFO] Copying curator-client-2.5.0.jar to 

[INFO] Copying jetty-annotations-9.2.19.v20160908.jar to 

[INFO] Copying jersey-server-1.9.jar to 

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

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

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

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-distro ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/distro.xml
[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] Building tar : 

[INFO] 
[INFO] 
[INFO] Building Apache Oozie ZooKeeper Security Tests 4.4.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default

[jira] [Commented] (OOZIE-2870) non working examples in oozie documentation coordinator spec

2017-05-02 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-2870:
-

[~pbacsko] [~gezapeti] can you pls. have a look?

> non working examples in oozie documentation coordinator spec
> 
>
> Key: OOZIE-2870
> URL: https://issues.apache.org/jira/browse/OOZIE-2870
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Clemens Valiente
>Assignee: Andras Piros
>  Labels: newbie
> Fix For: 5.0.0
>
> Attachments: OOZIE-2870.001.patch
>
>
> in the chapters:
> 4.4.1.2. The coord:endOfDays(int n) EL function
> https://oozie.apache.org/docs/4.3.0/CoordinatorFunctionalSpec.html#a4.4.1.2._The_coord:endOfDaysint_n_EL_function
> 4.4.2.2. The coord:endOfMonths(int n) EL function
> https://oozie.apache.org/docs/4.3.0/CoordinatorFunctionalSpec.html#a4.4.2.2._The_coord:endOfMonthsint_n_EL_function
> there is a hello world coordinator example:
> {code:xml}
>start="2009-01-02T08:00Z" end="2009-01-04T08:00Z" 
> timezone="America/Los_Angeles"
>  xmlns="uri:oozie:coordinator:0.1">
>   
> 10
> ${concurrency_level}
> ${execution_order}
> ${materialization_throttle}
>   
> ...{code}
> The throttle element does not exist for the oozie:coordinator specification 
> 0.1 so the version should probably be updated here.



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

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

2017-05-02 Thread Apache Jenkins Server

See 


--
[...truncated 968.68 KB...]
[INFO] Copying opencsv-2.3.jar to 

[INFO] Copying jasper-runtime-5.5.23.jar to 

[INFO] Copying curator-client-2.5.0.jar to 

[INFO] Copying jetty-annotations-9.2.19.v20160908.jar to 

[INFO] Copying jersey-server-1.9.jar to 

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

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

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

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-distro ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/distro.xml
[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] Building tar : 

[INFO] 
[INFO] 
[INFO] Building Apache Oozie ZooKeeper Security Tests 4.4.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

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

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Nothi

[jira] [Commented] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable

2017-05-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2874:
--

Testing JIRA OOZIE-2874

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 [core].
. {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 [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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/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 [sharelib/streaming].
. {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/hcatalog].
. {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/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 [tools].
. {color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
{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: 1935
.Tests failed: 1
.Tests errors: 2

.The patch failed the following testcases:

.  testNofindLogs(org.apache.oozie.util.TestTimestampedMessageParser)

.Tests failing with errors:
.  
testProcessRemainingLog(org.apache.oozie.util.TestTimestampedMessageParser)
.  
testProcessRemainingCoordinatorLogForActions(org.apache.oozie.util.TestTimestampedMessageParser)

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

> Make the Launcher Mapper map-only job's InputFormat class pluggable
> ---
>
> Key: OOZIE-2874
> URL: https://issues.apache.org/jira/browse/OOZIE-2874
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Attachments: OOZIE-2874.001.patch
>
>
> In order to prepare for YARN's [*rack-schedulable AM feature*|YARN-6050], and 
> [*its MapReduce counterpart*|MAPREDUCE-6871], let's have the possibility of 
> making the Launcher Mapper map-only job's 
> [{{InputFormat}}|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java]
>  class pluggable in order to provide alternative implementations that can 
> behave differently from 
> [{{OozieLauncherInputFormat}}|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/OozieLauncherInputFormat.java]
>  that does not request any HDFS resources.



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

[jira] [Commented] (OOZIE-2826) Falcon feed fails to aws s3; Oozie joda time version does not meet required jar version 2.2 or later

2017-05-02 Thread Steve Loughran (JIRA)


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

Steve Loughran commented on OOZIE-2826:
---

Joda time needs to be >= 2.8.1 to work on recent Java 8 & Java 7 JVMs; 2.5 
isn't going to work there. Sorry

> Falcon feed fails to aws s3; Oozie joda time version does not meet required 
> jar version 2.2 or later
> 
>
> Key: OOZIE-2826
> URL: https://issues.apache.org/jira/browse/OOZIE-2826
> Project: Oozie
>  Issue Type: Bug
>  Components: workflow
>Affects Versions: 4.3.0
>Reporter: Péter Gergő Barna
>Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-2826.patch, oozie-joda.example-feed.xml, 
> oozie-joda.log.txt
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Symptom:
> 2016-11-04 17:34:50,283 WARN [main] 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler: Unable to parse 
> last modified date: Wed, 02 Nov 2016 23:05:38 GMT
> java.lang.IllegalStateException: Joda-time 2.2 or later version is 
> required, but found version: 2.1
>   at com.amazonaws.util.DateUtils.handleException(DateUtils.java:149)
>   at com.amazonaws.util.DateUtils.parseRFC822Date(DateUtils.java:195)
>   at 
> com.amazonaws.services.s3.internal.ServiceUtils.parseRfc822Date(ServiceUtils.java:78)
>   at 
> com.amazonaws.services.s3.internal.AbstractS3ResponseHandler.populateObjectMetadata(AbstractS3ResponseHandler.java:115)
>   at 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler.handle(S3MetadataResponseHandler.java:32)
>   at 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler.handle(S3MetadataResponseHandler.java:25)
>   at 
> com.amazonaws.http.AmazonHttpClient.handleResponse(AmazonHttpClient.java:1072)
>   at 
> com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:746)
>   at 
> com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
>   at 
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1050)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1027)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.getObjectMetadata(S3AFileSystem.java:850)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.getFileStatus(S3AFileSystem.java:1403)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.innerMkdirs(S3AFileSystem.java:1343)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.mkdirs(S3AFileSystem.java:1308)
>   at org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:1898)
>   at 
> org.apache.falcon.util.DistCPOptionsUtil.getDistCpOptions(DistCPOptionsUtil.java:90)
>   at 
> org.apache.falcon.replication.FeedReplicator.getDistCpOptions(FeedReplicator.java:229)
>   at 
> org.apache.falcon.replication.FeedReplicator.run(FeedReplicator.java:70)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>   at 
> org.apache.falcon.replication.FeedReplicator.main(FeedReplicator.java:64)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at org.apache.oozie.action.hadoop.JavaMain.run(JavaMain.java:56)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.JavaMain.main(JavaMain.java:35)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724)
>   at org.apache.hadoop.m

Build failed in Jenkins: oozie-trunk-find-patches-available #157514

2017-05-02 Thread Apache Jenkins Server

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision eb168360c550943828d9fe2c7bfdcd4f5e830003 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f eb168360c550943828d9fe2c7bfdcd4f5e830003
 > git rev-list eb168360c550943828d9fe2c7bfdcd4f5e830003 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson5053763812849935937.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0100 
 447k0  447k0 0   317k  0 --:--:--  0:00:01 --:--:--  317k100 
1231k0 1231k0 0   523k  0 --:--:--  0:00:02 --:--:--  523k100 
1695k0 1695k0 0   504k  0 --:--:--  0:00:03 --:--:--  504k100 
1735k0 1735k0 0   481k  0 --:--:--  0:00:03 --:--:--  481k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : oozie-trunk-find-patches-available #157515

2017-05-02 Thread Apache Jenkins Server

See

[jira] Subscription: Oozie Patch Available

2017-05-02 Thread jira

Issue Subscription
Filter: Oozie Patch Available (96 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2874  Make the Launcher Mapper map-only job's InputFormat class pluggable
https://issues.apache.org/jira/browse/OOZIE-2874
OOZIE-2873  Check El Functions before submitting the coordinator
https://issues.apache.org/jira/browse/OOZIE-2873
OOZIE-2870  non working examples in oozie documentation coordinator spec
https://issues.apache.org/jira/browse/OOZIE-2870
OOZIE-2849  Fix build warnings when assembling directories
https://issues.apache.org/jira/browse/OOZIE-2849
OOZIE-2848  Override sharelib.tgz in distro when rebuilding Oozie
https://issues.apache.org/jira/browse/OOZIE-2848
OOZIE-2846  TestSSLServerConnectorFactory fails with Jetty 9.3 and 9.4
https://issues.apache.org/jira/browse/OOZIE-2846
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues.apache.org/jira/browse/OOZIE-2829
OOZIE-2825  Custom Authentication doc page is not well formatted
https://issues.apache.org/jira/browse/OOZIE-2825
OOZIE-2824  Fix typos in documentation
https://issues.apache.org/jira/browse/OOZIE-2824
OOZIE-2815  Oozie not always display job log
https://issues.apache.org/jira/browse/OOZIE-2815
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2796  oozie.action.keep.action.dir not getting noticed
https://issues.apache.org/jira/browse/OOZIE-2796
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2785  Master is not compiling with hadoop-1 profile
https://issues.apache.org/jira/browse/OOZIE-2785
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2780  Upgrade hadoop-common version to 2.6.0
https://issues.apache.org/jira/browse/OOZIE-2780
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2769  Extend FS action to allow setrep on a file
https://issues.apache.org/jira/browse/OOZIE-2769
OOZIE-2751  LocalOozieClient is missing methods from OozieClient
https://issues.apache.org/jira/browse/OOZIE-2751
OOZIE-2746  Several tests failure in TestV2ValidateServlet.java
https://issues.apache.org/jira/browse/OOZIE-2746
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2733  change org.apache.hadoop.fs.permission.AccessControlException to 
org.apache.hadoop.security.AccessControlException
https://issues.apache.org/jira/browse/OOZIE-2733
OOZIE-2726  Flaky test due to daylight saving changes
https://issues.apache.org/jira/browse/OOZIE-2726
OOZIE-2718  Improve -dryrun for bundles
https://issues.apache.org/jira/browse/OOZIE-2718
OOZIE-2713  Provide an option to log out contents of the localized jar files
https://issues.apache.org/jira/browse/OOZIE-2713
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693  SimpleHCatDependencyCache.removeMissingDependency can throw NPE
https://issues.apache.org/jira/browse/OOZIE-2693
OOZIE-2692  Oozie job submit doesn't report error message to user if there is 
any issue with job conf
https://issues.apache.org/jira/browse/OOZIE-2692
OOZIE-2684  Bad database schema error for WF_ACTIONS table
https://issues.apache.org/jira/browse/OOZIE-2684
OOZIE-2681  fix javadoc to compile on JDK8 again
https://issues.apache.org/jira/browse/OOZIE-2681
OOZIE-2670  Upgrade Hbase to 1.2
https://issues.apache.org/jira/browse/OOZIE-2670
OOZIE-2668  Status update and recovery problems when coord action and its 
children not in sync
https://issues.apache.org/jira/browse/OOZIE-2668
OOZIE-2662  DB migration fails if DB is too big
https://issues.apache.org/jira/browse/OOZIE-2662
OOZIE-2652  Skip trash while deleting hive table partition
https://issues.apache.org/jira/browse/OOZIE-2652
OOZIE-2651  Set javax.xml.parsers.DocumentBuilderFactory sys prop to make XML 
handling faster
https

[jira] [Created] (OOZIE-2875) Typo in ssh action twiki docs

2017-05-02 Thread Dongying Jiao (JIRA)

Dongying Jiao created OOZIE-2875:


 Summary: Typo in ssh action twiki docs
 Key: OOZIE-2875
 URL: https://issues.apache.org/jira/browse/OOZIE-2875
 Project: Oozie
  Issue Type: Sub-task
  Components: docs
Affects Versions: trunk
Reporter: Dongying Jiao
Priority: Minor


By default this property is set tot true.
It should be:
By default this property is set to true.




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

[jira] [Updated] (OOZIE-2875) Typo in ssh action twiki docs

2017-05-02 Thread Dongying Jiao (JIRA)


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

Dongying Jiao updated OOZIE-2875:
-
Attachment: OOZIE-2875-1.patch

> Typo in ssh action twiki docs
> -
>
> Key: OOZIE-2875
> URL: https://issues.apache.org/jira/browse/OOZIE-2875
> Project: Oozie
>  Issue Type: Sub-task
>  Components: docs
>Affects Versions: trunk
>Reporter: Dongying Jiao
>Priority: Minor
> Attachments: OOZIE-2875-1.patch
>
>
> By default this property is set tot true.
> It should be:
> By default this property is set to true.



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

[jira] [Created] (OOZIE-2876) Provide deployment primitives

2017-05-02 Thread Clay B. (JIRA)

Clay B. created OOZIE-2876:
--

 Summary: Provide deployment primitives
 Key: OOZIE-2876
 URL: https://issues.apache.org/jira/browse/OOZIE-2876
 Project: Oozie
  Issue Type: Wish
  Components: action
Reporter: Clay B.
Priority: Minor


Today one can schedule workflows which run on a cluster using many pre-existing 
artifacts. However, today there are no helpful primitives for deploying those 
artifacts to the cluster.

For example, one may use a Spark JAR (hosted in a Maven repository) stored on a 
cluster's HDFS to talk with data stored in a Hive table (the schema of which is 
likely tracked in a source code management system somewhere) and use JDBC to 
talk to an arbitrary database off the cluster. (As to which database being 
configured based on the cluster being Dev, Beta or PROD all mapped in a simple 
configuration file.) Further, the data may be verified by a simple Pig script 
(also stored in a source code management repository).

As a user, I'd like some way to get my binaries and ASCII configuration on a 
cluster without significant ad hoc shell actions.



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

[jira] [Created] (OOZIE-2877) Oozie Git Action

2017-05-02 Thread Clay B. (JIRA)

Clay B. created OOZIE-2877:
--

 Summary: Oozie Git Action
 Key: OOZIE-2877
 URL: https://issues.apache.org/jira/browse/OOZIE-2877
 Project: Oozie
  Issue Type: Sub-task
  Components: action
Reporter: Clay B.


To aide in deploying ASCII artifacts to clusters, let's provide a tie-in for a 
source-code management system. Git would be my preferred choice.

Ideally, this could handle a user's key material e.g. for an ssh key to pull 
down from a secured repository. This would free users from handling their own 
key staging and clean-up on YARN nodes and only require them to store the key 
secured in HDFS.



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

[jira] [Commented] (OOZIE-2876) Provide deployment primitives

2017-05-02 Thread Clay B. (JIRA)


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

Clay B. commented on OOZIE-2876:


I just so happen to have an implementation of something like this and will work 
to get a patch up for review in the next week.

> Provide deployment primitives
> -
>
> Key: OOZIE-2876
> URL: https://issues.apache.org/jira/browse/OOZIE-2876
> Project: Oozie
>  Issue Type: Wish
>  Components: action
>Reporter: Clay B.
>Priority: Minor
>
> Today one can schedule workflows which run on a cluster using many 
> pre-existing artifacts. However, today there are no helpful primitives for 
> deploying those artifacts to the cluster.
> For example, one may use a Spark JAR (hosted in a Maven repository) stored on 
> a cluster's HDFS to talk with data stored in a Hive table (the schema of 
> which is likely tracked in a source code management system somewhere) and use 
> JDBC to talk to an arbitrary database off the cluster. (As to which database 
> being configured based on the cluster being Dev, Beta or PROD all mapped in a 
> simple configuration file.) Further, the data may be verified by a simple Pig 
> script (also stored in a source code management repository).
> As a user, I'd like some way to get my binaries and ASCII configuration on a 
> cluster without significant ad hoc shell actions.



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

[jira] [Commented] (OOZIE-2877) Oozie Git Action

2017-05-02 Thread Clay B. (JIRA)


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

Clay B. commented on OOZIE-2877:


I just so happen to have an implementation of something like this and will work 
to get a patch up for review in the next week.

> Oozie Git Action
> 
>
> Key: OOZIE-2877
> URL: https://issues.apache.org/jira/browse/OOZIE-2877
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action
>Reporter: Clay B.
>
> To aide in deploying ASCII artifacts to clusters, let's provide a tie-in for 
> a source-code management system. Git would be my preferred choice.
> Ideally, this could handle a user's key material e.g. for an ssh key to pull 
> down from a secured repository. This would free users from handling their own 
> key staging and clean-up on YARN nodes and only require them to store the key 
> secured in HDFS.



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

[jira] [Issue Comment Deleted] (OOZIE-2876) Provide deployment primitives

2017-05-02 Thread Clay B. (JIRA)


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

Clay B. updated OOZIE-2876:
---
Comment: was deleted

(was: I just so happen to have an implementation of something like this and 
will work to get a patch up for review in the next week.)

> Provide deployment primitives
> -
>
> Key: OOZIE-2876
> URL: https://issues.apache.org/jira/browse/OOZIE-2876
> Project: Oozie
>  Issue Type: Wish
>  Components: action
>Reporter: Clay B.
>Priority: Minor
>
> Today one can schedule workflows which run on a cluster using many 
> pre-existing artifacts. However, today there are no helpful primitives for 
> deploying those artifacts to the cluster.
> For example, one may use a Spark JAR (hosted in a Maven repository) stored on 
> a cluster's HDFS to talk with data stored in a Hive table (the schema of 
> which is likely tracked in a source code management system somewhere) and use 
> JDBC to talk to an arbitrary database off the cluster. (As to which database 
> being configured based on the cluster being Dev, Beta or PROD all mapped in a 
> simple configuration file.) Further, the data may be verified by a simple Pig 
> script (also stored in a source code management repository).
> As a user, I'd like some way to get my binaries and ASCII configuration on a 
> cluster without significant ad hoc shell actions.



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

[jira] [Created] (OOZIE-2878) Oozie Maven Action

2017-05-02 Thread Clay B. (JIRA)

Clay B. created OOZIE-2878:
--

 Summary: Oozie Maven Action
 Key: OOZIE-2878
 URL: https://issues.apache.org/jira/browse/OOZIE-2878
 Project: Oozie
  Issue Type: Sub-task
  Components: action
Reporter: Clay B.
Priority: Minor


To provide a way for users to get JAR's, shared libraries and other binary 
artifacts on their cluster, perhaps a Maven action could be crafted. One could 
use a Maven POM file using the 
[maven-dependency-plugin|https://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-project-dependencies.html]
 which would be the desired artifacts from a Maven repository for later Oozie 
jobs to use.



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

[jira] [Commented] (OOZIE-2878) Oozie Maven Action

2017-05-02 Thread Clay B. (JIRA)


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

Clay B. commented on OOZIE-2878:


Particular issues an action could help users with is not needlessly populating 
a local repo in a home directory and being able to verify if an HDFS location 
has all necessary artifacts or if newer ones are available which need to 
replace those previously acquired.

> Oozie Maven Action
> --
>
> Key: OOZIE-2878
> URL: https://issues.apache.org/jira/browse/OOZIE-2878
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action
>Reporter: Clay B.
>Priority: Minor
>
> To provide a way for users to get JAR's, shared libraries and other binary 
> artifacts on their cluster, perhaps a Maven action could be crafted. One 
> could use a Maven POM file using the 
> [maven-dependency-plugin|https://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-project-dependencies.html]
>  which would be the desired artifacts from a Maven repository for later Oozie 
> jobs to use.



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

[jira] [Comment Edited] (OOZIE-2876) Provide deployment primitives

2017-05-02 Thread Clay B. (JIRA)


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

Clay B. edited comment on OOZIE-2876 at 5/3/17 6:56 AM:


It seems downloading from a generic HTTP server is a pretty easy activity for a 
Java or Shell action; have folks seen this onerous enough for new-users that an 
action could provide value?


was (Author: clayb):
It seems downloading from a generic HTTP server is a pretty easy action for a 
Java or Shell action; have folks seen this onerous enough for new-users that an 
action could provide value?

> Provide deployment primitives
> -
>
> Key: OOZIE-2876
> URL: https://issues.apache.org/jira/browse/OOZIE-2876
> Project: Oozie
>  Issue Type: Wish
>  Components: action
>Reporter: Clay B.
>Priority: Minor
>
> Today one can schedule workflows which run on a cluster using many 
> pre-existing artifacts. However, today there are no helpful primitives for 
> deploying those artifacts to the cluster.
> For example, one may use a Spark JAR (hosted in a Maven repository) stored on 
> a cluster's HDFS to talk with data stored in a Hive table (the schema of 
> which is likely tracked in a source code management system somewhere) and use 
> JDBC to talk to an arbitrary database off the cluster. (As to which database 
> being configured based on the cluster being Dev, Beta or PROD all mapped in a 
> simple configuration file.) Further, the data may be verified by a simple Pig 
> script (also stored in a source code management repository).
> As a user, I'd like some way to get my binaries and ASCII configuration on a 
> cluster without significant ad hoc shell actions.



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

[jira] [Commented] (OOZIE-2876) Provide deployment primitives

2017-05-02 Thread Clay B. (JIRA)


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

Clay B. commented on OOZIE-2876:


It seems downloading from a generic HTTP server is a pretty easy action for a 
Java or Shell action; have folks seen this onerous enough for new-users that an 
action could provide value?

> Provide deployment primitives
> -
>
> Key: OOZIE-2876
> URL: https://issues.apache.org/jira/browse/OOZIE-2876
> Project: Oozie
>  Issue Type: Wish
>  Components: action
>Reporter: Clay B.
>Priority: Minor
>
> Today one can schedule workflows which run on a cluster using many 
> pre-existing artifacts. However, today there are no helpful primitives for 
> deploying those artifacts to the cluster.
> For example, one may use a Spark JAR (hosted in a Maven repository) stored on 
> a cluster's HDFS to talk with data stored in a Hive table (the schema of 
> which is likely tracked in a source code management system somewhere) and use 
> JDBC to talk to an arbitrary database off the cluster. (As to which database 
> being configured based on the cluster being Dev, Beta or PROD all mapped in a 
> simple configuration file.) Further, the data may be verified by a simple Pig 
> script (also stored in a source code management repository).
> As a user, I'd like some way to get my binaries and ASCII configuration on a 
> cluster without significant ad hoc shell actions.



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

Build failed in Jenkins: oozie-trunk-find-patches-available #157456

Jenkins build is back to normal : oozie-trunk-find-patches-available #157457

[jira] [Created] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable in order to provide alternative implementations

[jira] [Updated] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable in order to provide alternative implementations

[jira] [Updated] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable

[jira] [Updated] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable

[jira] [Updated] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable

[jira] [Updated] (OOZIE-2870) non working examples in oozie documentation coordinator spec

[jira] [Assigned] (OOZIE-2870) non working examples in oozie documentation coordinator spec

[jira] [Commented] (OOZIE-2751) LocalOozieClient is missing methods from OozieClient

[jira] [Commented] (OOZIE-2870) non working examples in oozie documentation coordinator spec

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

[jira] [Commented] (OOZIE-2870) non working examples in oozie documentation coordinator spec

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

[jira] [Commented] (OOZIE-2874) Make the Launcher Mapper map-only job's InputFormat class pluggable

[jira] [Commented] (OOZIE-2826) Falcon feed fails to aws s3; Oozie joda time version does not meet required jar version 2.2 or later

Build failed in Jenkins: oozie-trunk-find-patches-available #157514

Jenkins build is back to normal : oozie-trunk-find-patches-available #157515

[jira] Subscription: Oozie Patch Available

[jira] [Created] (OOZIE-2875) Typo in ssh action twiki docs

[jira] [Updated] (OOZIE-2875) Typo in ssh action twiki docs

[jira] [Created] (OOZIE-2876) Provide deployment primitives

[jira] [Created] (OOZIE-2877) Oozie Git Action

[jira] [Commented] (OOZIE-2876) Provide deployment primitives

[jira] [Commented] (OOZIE-2877) Oozie Git Action

[jira] [Issue Comment Deleted] (OOZIE-2876) Provide deployment primitives

[jira] [Created] (OOZIE-2878) Oozie Maven Action

[jira] [Commented] (OOZIE-2878) Oozie Maven Action

[jira] [Comment Edited] (OOZIE-2876) Provide deployment primitives

[jira] [Commented] (OOZIE-2876) Provide deployment primitives

30 matches

Site Navigation

Mail list logo

Footer information