date:20170619

[jira] [Commented] (OOZIE-2920) Document Distcp can copy files within a cluster

2017-06-19 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2920:
--

Testing JIRA OOZIE-2920

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 6 Javadoc warning(s)
{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 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: 1967
.Tests rerun: 79
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.jms.TestJMSJobEventListener,org.apache.oozie.action.hadoop.TestLauncherAM,
{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}

{color:red}. There is at least one warning, please check{color}

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

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

> Document Distcp can copy files within a cluster
> ---
>
> Key: OOZIE-2920
> URL: https://issues.apache.org/jira/browse/OOZIE-2920
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2920-0.patch, OOZIE-2920-1.patch, 
> OOZIE-2920-2.patch, OOZIE-2920-3.patch
>
>
> The FS action doesn't support a "copy" action.  We should update the 
> documentation to point to the DistCp action to help users looking for that 
> functionality.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-06-19 Thread Apache Jenkins Server

See 


--
[...truncated 358.18 KB...]
[INFO] Copying jackson-core-asl-1.9.13.jar to 

[INFO] Copying commons-jexl-2.1.1.jar to 

[INFO] Copying oozie-sharelib-hcatalog-5.0.0-SNAPSHOT.jar to 

[INFO] Copying hadoop-mapreduce-client-jobclient-2.6.0.jar to 

[INFO] Copying gson-2.7.jar to 

[INFO] Copying oozie-core-5.0.0-SNAPSHOT.jar to 

[INFO] Copying commons-pool-1.5.4.jar to 

[INFO] Copying htrace-core-3.0.4.jar to 

[INFO] Copying jaxb-impl-2.2.3-1.jar to 

[INFO] Copying jets3t-0.9.0.jar to 

[INFO] Copying datanucleus-rdbms-3.2.9.jar to 

[INFO] Copying hive-common-1.2.0.jar to 

[INFO] Copying snappy-java-1.0.4.1.jar to 

[INFO] Copying javax.annotation-api-1.2.jar to 

[INFO] Copying commons-compiler-2.7.6.jar to 

[INFO] Copying ant-1.9.1.jar to 

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

[INFO] Copying janino-2.7.6.jar to 

[INFO] Copying activemq-client-5.13.3.jar to 

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

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

[INFO] Copying hadoop-mapreduce-client-common-2.6.0.jar to 

[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

[INFO] Copying jackson-core-2.4.2.jar to 

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying netty-3.7.0.Final.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO]

[jira] [Comment Edited] (OOZIE-2920) Document Distcp can copy files within a cluster

2017-06-19 Thread Artem Ervits (JIRA)


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

Artem Ervits edited comment on OOZIE-2920 at 6/20/17 3:01 AM:
--

[~rkanter] please review, addressed the comments in #2 and #3, the twiki 
hyperlink works as expected. Thanks!


was (Author: dbist13):
[~rkanter] please review

> Document Distcp can copy files within a cluster
> ---
>
> Key: OOZIE-2920
> URL: https://issues.apache.org/jira/browse/OOZIE-2920
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2920-0.patch, OOZIE-2920-1.patch, 
> OOZIE-2920-2.patch, OOZIE-2920-3.patch
>
>
> The FS action doesn't support a "copy" action.  We should update the 
> documentation to point to the DistCp action to help users looking for that 
> functionality.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2769) Extend FS action to allow setrep on a file

2017-06-19 Thread Artem Ervits (JIRA)


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

Artem Ervits commented on OOZIE-2769:
-

tests pass locally. Rebased the patch, please review.

> Extend FS action to allow setrep on a file
> --
>
> Key: OOZIE-2769
> URL: https://issues.apache.org/jira/browse/OOZIE-2769
> Project: Oozie
>  Issue Type: Improvement
>  Components: action, core
>Affects Versions: 4.2.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
>  Labels: easyfix, features, patch
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2769-0.patch, OOZIE-2769-1.patch, 
> OOZIE-2769-2.patch, OOZIE-2769-3.patch, OOZIE-2769-4.patch, 
> OOZIE-2769-5.patch, OOZIE-2769-6.patch
>
>
> Today, Oozie FS action can only do delete/move/chgrp/chmod, this feature 
> extends FS action to allow for setrep on an HDFS file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 59906: Coordinator SLA should support to configure EL functions as variable

2017-06-19 Thread Wen Chi


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

(Updated 六月 20, 2017, 2:53 a.m.)


Review request for oozie and András Piros.


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


Repository: oozie-git


Description
---

1. coordinator.xml define SLA like this
```xml

  ${nominal_time}
  ${ 1 * HOURS}
  ${1 * MINUTES}

```
2. In job.properties define: **nominal_time=${coord:nominalTime()}**
3. Then coordinator will run failed
> "Coord Job Materialization Error: Could not parse [${coord:nominalTime()}] 
> using [-MM-dd'T'HH:mm+0800] mask";


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java 
17e7fa0a9af3c160f98ea615bc73f3a1d7489aec 
  
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
 2e39689d62fcad3eb5d58f81dbd743f3e0a6b46f 


Diff: https://reviews.apache.org/r/59906/diff/4/

Changes: https://reviews.apache.org/r/59906/diff/3-4/


Testing
---


Thanks,

Wen Chi

[jira] [Updated] (OOZIE-2920) Document Distcp can copy files within a cluster

2017-06-19 Thread Artem Ervits (JIRA)


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

Artem Ervits updated OOZIE-2920:

Attachment: OOZIE-2920-3.patch

[~rkanter] please review

> Document Distcp can copy files within a cluster
> ---
>
> Key: OOZIE-2920
> URL: https://issues.apache.org/jira/browse/OOZIE-2920
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2920-0.patch, OOZIE-2920-1.patch, 
> OOZIE-2920-2.patch, OOZIE-2920-3.patch
>
>
> The FS action doesn't support a "copy" action.  We should update the 
> documentation to point to the DistCp action to help users looking for that 
> functionality.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-06-19 Thread Apache Jenkins Server

See

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

2017-06-19 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 a5c839a3a69bfb71007b1645bb9ea79f05fcd702 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a5c839a3a69bfb71007b1645bb9ea79f05fcd702
 > git rev-list a5c839a3a69bfb71007b1645bb9ea79f05fcd702 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson3177040655177245096.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 --:--:-- --:--:-- --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0  0   
  00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0  0 0 
   0 00 0  0  0 --:--:--  0:00:04 --:--:-- 0  0 0   
 0 00 0  0  0 --:--:--  0:00:05 --:--:-- 0  0 0
0 00 0  0  0 --:--:--  0:00:06 --:--:-- 0  0 00 
00 0  0  0 --:--:--  0:00:07 --:--:-- 0  0 00   
  00 0  0  0 --:--:--  0:00:08 --:--:-- 0  0 00 
00 0  0  0 --:--:--  0:00:09 --:--:-- 0  0 00 0 
   0 0  0  0 --:--:--  0:00:10 --:--:-- 0  0 00 0   
 0 0  0  0 --:--:--  0:00:11 --:--:-- 0  0 00 0
0 0  0  0 --:--:--  0:00:12 --:--:-- 0  0 00 00 
0  0  0 --:--:--  0:00:13 --:--:-- 0  0 00 00   
  0  0  0 --:--:--  0:00:14 --:--:-- 0  0 00 00 
0  0  0 --:--:--  0:00:15 --:--:-- 0  0 00 00 0 
 0  0 --:--:--  0:00:16 --:--:-- 0  0 00 00 0   
   0  0 --:--:--  0:00:17 --:--:-- 0  0 00 00 0 
 0  0 --:--:--  0:00:18 --:--:-- 0  0 00 00 0  
0  0 --:--:--  0:00:19 --:--:-- 0  0 00 00 0  0 
 0 --:--:--  0:00:20 --:--:-- 0  0 00 00 0  0   
   0 --:--:--  0:00:21 --:--:-- 0  0 00 00 0  0 
 0 --:--:--  0:00:22 --:--:-- 0  0 00 00 0  0  
0 --:--:--  0:00:23 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:24 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:25 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:26 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:27 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:28 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:29 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:30 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:31 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:32 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:33 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:34 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:35 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:36 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:37 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:38 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:39 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:40 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:41 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:42

[jira] [Commented] (OOZIE-2769) Extend FS action to allow setrep on a file

2017-06-19 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2769:
--

Testing JIRA OOZIE-2769

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:red}-1{color} the patch contains 1 line(s) with 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}WARNING{color}: the current HEAD has 6 Javadoc warning(s)
{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 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: 1968
.Tests rerun: 79
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.jms.TestJMSJobEventListener,org.apache.oozie.action.hadoop.TestLauncherAM,
{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}

{color:red}. There is at least one warning, please check{color}

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

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

> Extend FS action to allow setrep on a file
> --
>
> Key: OOZIE-2769
> URL: https://issues.apache.org/jira/browse/OOZIE-2769
> Project: Oozie
>  Issue Type: Improvement
>  Components: action, core
>Affects Versions: 4.2.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
>  Labels: easyfix, features, patch
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2769-0.patch, OOZIE-2769-1.patch, 
> OOZIE-2769-2.patch, OOZIE-2769-3.patch, OOZIE-2769-4.patch, 
> OOZIE-2769-5.patch, OOZIE-2769-6.patch
>
>
> Today, Oozie FS action can only do delete/move/chgrp/chmod, this feature 
> extends FS action to allow for setrep on an HDFS file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-06-19 Thread Apache Jenkins Server

See 


--
[...truncated 359.84 KB...]
[INFO] Copying jackson-core-asl-1.9.13.jar to 

[INFO] Copying commons-jexl-2.1.1.jar to 

[INFO] Copying oozie-sharelib-hcatalog-5.0.0-SNAPSHOT.jar to 

[INFO] Copying hadoop-mapreduce-client-jobclient-2.6.0.jar to 

[INFO] Copying gson-2.7.jar to 

[INFO] Copying oozie-core-5.0.0-SNAPSHOT.jar to 

[INFO] Copying commons-pool-1.5.4.jar to 

[INFO] Copying htrace-core-3.0.4.jar to 

[INFO] Copying jaxb-impl-2.2.3-1.jar to 

[INFO] Copying jets3t-0.9.0.jar to 

[INFO] Copying datanucleus-rdbms-3.2.9.jar to 

[INFO] Copying hive-common-1.2.0.jar to 

[INFO] Copying snappy-java-1.0.4.1.jar to 

[INFO] Copying javax.annotation-api-1.2.jar to 

[INFO] Copying commons-compiler-2.7.6.jar to 

[INFO] Copying ant-1.9.1.jar to 

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

[INFO] Copying janino-2.7.6.jar to 

[INFO] Copying activemq-client-5.13.3.jar to 

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

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

[INFO] Copying hadoop-mapreduce-client-common-2.6.0.jar to 

[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

[INFO] Copying jackson-core-2.4.2.jar to 

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying netty-3.7.0.Final.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO]

[jira] [Updated] (OOZIE-2769) Extend FS action to allow setrep on a file

2017-06-19 Thread Artem Ervits (JIRA)


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

Artem Ervits updated OOZIE-2769:

Attachment: OOZIE-2769-6.patch

[~gezapeti] please review.

> Extend FS action to allow setrep on a file
> --
>
> Key: OOZIE-2769
> URL: https://issues.apache.org/jira/browse/OOZIE-2769
> Project: Oozie
>  Issue Type: Improvement
>  Components: action, core
>Affects Versions: 4.2.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
>  Labels: easyfix, features, patch
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2769-0.patch, OOZIE-2769-1.patch, 
> OOZIE-2769-2.patch, OOZIE-2769-3.patch, OOZIE-2769-4.patch, 
> OOZIE-2769-5.patch, OOZIE-2769-6.patch
>
>
> Today, Oozie FS action can only do delete/move/chgrp/chmod, this feature 
> extends FS action to allow for setrep on an HDFS file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2918) Delete LauncherMapper and its test

2017-06-19 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2918:
--

Testing JIRA OOZIE-2918

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 16 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}WARNING{color}: the current HEAD has 6 Javadoc warning(s)
{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 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: 1964
.Tests rerun: 18
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestHdfsOperations,org.apache.oozie.jms.TestJMSJobEventListener,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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

{color:red}. There is at least one warning, please check{color}

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

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

> Delete LauncherMapper and its test
> --
>
> Key: OOZIE-2918
> URL: https://issues.apache.org/jira/browse/OOZIE-2918
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
> Attachments: OOZIE-2918-01.patch, OOZIE-2918-02.patch, 
> OOZIE-2918-03.patch
>
>
> While LauncherMapper itself is not used anymore it contains a bunch of static 
> methods that are referenced from different places in the code.
> We should refactor out code and related test cases to where they belong.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-06-19 Thread Apache Jenkins Server

See

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

2017-06-19 Thread Apache Jenkins Server

See

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

2017-06-19 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 a5c839a3a69bfb71007b1645bb9ea79f05fcd702 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a5c839a3a69bfb71007b1645bb9ea79f05fcd702
 > git rev-list a5c839a3a69bfb71007b1645bb9ea79f05fcd702 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson658085299845145808.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 --:--:--  0:00:01 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0  0   
  00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0
curl: (35) Unknown SSL protocol error in connection to issues.apache.org:443 
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Updated] (OOZIE-2918) Delete LauncherMapper and its test

2017-06-19 Thread Attila Sasvari (JIRA)


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

Attila Sasvari updated OOZIE-2918:
--
Attachment: OOZIE-2918-03.patch

> Delete LauncherMapper and its test
> --
>
> Key: OOZIE-2918
> URL: https://issues.apache.org/jira/browse/OOZIE-2918
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
> Attachments: OOZIE-2918-01.patch, OOZIE-2918-02.patch, 
> OOZIE-2918-03.patch
>
>
> While LauncherMapper itself is not used anymore it contains a bunch of static 
> methods that are referenced from different places in the code.
> We should refactor out code and related test cases to where they belong.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2957) Documentation states that starting a coordinator is possible

2017-06-19 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2957:
--

Testing JIRA OOZIE-2957

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 6 Javadoc warning(s)
{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 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: 1770
.Tests rerun: 3
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestHdfsOperations,
{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}

{color:red}. There is at least one warning, please check{color}

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

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

> Documentation states that starting a coordinator is possible
> 
>
> Key: OOZIE-2957
> URL: https://issues.apache.org/jira/browse/OOZIE-2957
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, docs
>Affects Versions: 5.0.0
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
> Attachments: OOZIE-2957-1.patch
>
>
> The documentation of the command line tools states that starting a 
> coordinator is possible
> {quote}---+++ Starting a Workflow, Coordinator or Bundle Job
> Example:
> 
> $ oozie job -oozie http://localhost:11000/oozie -start 
> 14-20090525161321-oozie-joe
> 
> The =start= option starts a previously submitted workflow job, coordinator 
> job or bundle job that is in =PREP= status.
> After the command is executed the workflow job will be in =RUNNING= status, 
> coordinator job will be in =RUNNING= status and
> bundle job will be in =RUNNING=status.{quote}
> As of OOZIE-923 this should not be possible. The documentation should be 
> changed to not include coordinators in this section or mention that starting 
> a coordinator from the CLI is not possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-06-19 Thread Apache Jenkins Server

See 


Changes:

[gezapeti] OOZIE-2815 amend - Oozie not always display job log (andras.piros via

--
[...truncated 360.56 KB...]
[INFO] Copying jackson-core-asl-1.9.13.jar to 

[INFO] Copying commons-jexl-2.1.1.jar to 

[INFO] Copying oozie-sharelib-hcatalog-5.0.0-SNAPSHOT.jar to 

[INFO] Copying hadoop-mapreduce-client-jobclient-2.6.0.jar to 

[INFO] Copying gson-2.7.jar to 

[INFO] Copying oozie-core-5.0.0-SNAPSHOT.jar to 

[INFO] Copying commons-pool-1.5.4.jar to 

[INFO] Copying htrace-core-3.0.4.jar to 

[INFO] Copying jaxb-impl-2.2.3-1.jar to 

[INFO] Copying jets3t-0.9.0.jar to 

[INFO] Copying datanucleus-rdbms-3.2.9.jar to 

[INFO] Copying hive-common-1.2.0.jar to 

[INFO] Copying snappy-java-1.0.4.1.jar to 

[INFO] Copying javax.annotation-api-1.2.jar to 

[INFO] Copying commons-compiler-2.7.6.jar to 

[INFO] Copying ant-1.9.1.jar to 

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

[INFO] Copying janino-2.7.6.jar to 

[INFO] Copying activemq-client-5.13.3.jar to 

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

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

[INFO] Copying hadoop-mapreduce-client-common-2.6.0.jar to 

[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

[INFO] Copying jackson-core-2.4.2.jar to 

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying netty-3.7.0.Final.jar to 

[INFO] Copying xmlenc-0.52.jar to

[jira] [Commented] (OOZIE-2941) Old map-reduce workflow example can't work with OYA

2017-06-19 Thread Peter Bacsko (JIRA)


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

Peter Bacsko commented on OOZIE-2941:
-

So what's the status of this?

Is there a consensus on whether it's a bug or not? 

> Old map-reduce workflow example can't work with OYA
> ---
>
> Key: OOZIE-2941
> URL: https://issues.apache.org/jira/browse/OOZIE-2941
> Project: Oozie
>  Issue Type: Sub-task
>  Components: workflow
>Affects Versions: trunk
>Reporter: Dongying Jiao
> Attachments: RM_UI.jpg
>
>
> map-reduce workflow in Oozie examples run failed after OYA merged. The 
> exception in yarn log is:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
>   at java.lang.ClassLoader.defineClass1(Native Method)
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
>   at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
>   at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   ... 15 more



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 59906: Coordinator SLA should support to configure EL functions as variable

2017-06-19 Thread András Piros


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




core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java
Line 870 (original), 870 (patched)


`LOG.warn("Variable is not defined in job.properties. Here is the message: 
{0}", e.getMessage());`


- András Piros


On June 19, 2017, 11:09 a.m., Wen Chi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59906/
> ---
> 
> (Updated June 19, 2017, 11:09 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Bugs: OOZIE-2929
> https://issues.apache.org/jira/browse/OOZIE-2929
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> 1. coordinator.xml define SLA like this
> ```xml
> 
>   ${nominal_time}
>   ${ 1 * HOURS}
>   ${1 * MINUTES}
> 
> ```
> 2. In job.properties define: **nominal_time=${coord:nominalTime()}**
> 3. Then coordinator will run failed
> > "Coord Job Materialization Error: Could not parse [${coord:nominalTime()}] 
> > using [-MM-dd'T'HH:mm+0800] mask";
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java 
> 17e7fa0a9af3c160f98ea615bc73f3a1d7489aec 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
>  2e39689d62fcad3eb5d58f81dbd743f3e0a6b46f 
> 
> 
> Diff: https://reviews.apache.org/r/59906/diff/3/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Wen Chi
> 
>

[jira] [Updated] (OOZIE-2957) Documentation states that starting a coordinator is possible

2017-06-19 Thread Jan Hentschel (JIRA)


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

Jan Hentschel updated OOZIE-2957:
-
Attachment: OOZIE-2957-1.patch

> Documentation states that starting a coordinator is possible
> 
>
> Key: OOZIE-2957
> URL: https://issues.apache.org/jira/browse/OOZIE-2957
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator, docs
>Affects Versions: 5.0.0
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
> Attachments: OOZIE-2957-1.patch
>
>
> The documentation of the command line tools states that starting a 
> coordinator is possible
> {quote}---+++ Starting a Workflow, Coordinator or Bundle Job
> Example:
> 
> $ oozie job -oozie http://localhost:11000/oozie -start 
> 14-20090525161321-oozie-joe
> 
> The =start= option starts a previously submitted workflow job, coordinator 
> job or bundle job that is in =PREP= status.
> After the command is executed the workflow job will be in =RUNNING= status, 
> coordinator job will be in =RUNNING= status and
> bundle job will be in =RUNNING=status.{quote}
> As of OOZIE-923 this should not be possible. The documentation should be 
> changed to not include coordinators in this section or mention that starting 
> a coordinator from the CLI is not possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2769) Extend FS action to allow setrep on a file

2017-06-19 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2769:
---

Oh, this totally slipped my mind. I'm sorry.
Can you rebase the patch? It does not apply to master anymore.

> Extend FS action to allow setrep on a file
> --
>
> Key: OOZIE-2769
> URL: https://issues.apache.org/jira/browse/OOZIE-2769
> Project: Oozie
>  Issue Type: Improvement
>  Components: action, core
>Affects Versions: 4.2.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
>  Labels: easyfix, features, patch
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2769-0.patch, OOZIE-2769-1.patch, 
> OOZIE-2769-2.patch, OOZIE-2769-3.patch, OOZIE-2769-4.patch, OOZIE-2769-5.patch
>
>
> Today, Oozie FS action can only do delete/move/chgrp/chmod, this feature 
> extends FS action to allow for setrep on an HDFS file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2815) Oozie not always display job log

2017-06-19 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2815:
---

+1 for the second amend patch.

> Oozie not always display job log
> 
>
> Key: OOZIE-2815
> URL: https://issues.apache.org/jira/browse/OOZIE-2815
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-2815.amend.002.patch, OOZIE-2815-amend-1.patch, 
> OOZIE-2815-V2.patch, OOZIE-2815-V3.patch, OOZIE-2815-V4.patch, 
> OOZIE-2815-V5.patch
>
>
> There are few issues with log streaming. We will fix following things.
> 1. UI has an issue with displaying "loading... done". It used to show loading 
> done even if logs were not loaded entirely.
> 2. Server-server communication time out. The default time is 1 min. Setting 
> to 3 min same as UI.
> 3. We use to throw an error message if log scan duration is more than 
> configured duration. We will be truncating log.
> 4. No log scan duration check for audit and error log since it doesn't 
> support log filter.
> 5. Different buffer.len setting for error and audit log, so that partial 
> loading can be faster. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2815) Oozie not always display job log

2017-06-19 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2815:
--

Testing JIRA OOZIE-2815

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:red}WARNING{color}: the current HEAD has 6 Javadoc warning(s)
{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 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: 1967
.Tests rerun: 64
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.action.hadoop.TestLauncherAM,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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

{color:red}. There is at least one warning, please check{color}

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

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

> Oozie not always display job log
> 
>
> Key: OOZIE-2815
> URL: https://issues.apache.org/jira/browse/OOZIE-2815
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-2815.amend.002.patch, OOZIE-2815-amend-1.patch, 
> OOZIE-2815-V2.patch, OOZIE-2815-V3.patch, OOZIE-2815-V4.patch, 
> OOZIE-2815-V5.patch
>
>
> There are few issues with log streaming. We will fix following things.
> 1. UI has an issue with displaying "loading... done". It used to show loading 
> done even if logs were not loaded entirely.
> 2. Server-server communication time out. The default time is 1 min. Setting 
> to 3 min same as UI.
> 3. We use to throw an error message if log scan duration is more than 
> configured duration. We will be truncating log.
> 4. No log scan duration check for audit and error log since it doesn't 
> support log filter.
> 5. Different buffer.len setting for error and audit log, so that partial 
> loading can be faster. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 59906: Coordinator SLA should support to configure EL functions as variable

2017-06-19 Thread Wen Chi


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

(Updated 六月 19, 2017, 11:09 a.m.)


Review request for oozie and András Piros.


Changes
---

add ``LOG.warn()`` for sla content is not defined as variable in job.properties;


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


Repository: oozie-git


Description
---

1. coordinator.xml define SLA like this
```xml

  ${nominal_time}
  ${ 1 * HOURS}
  ${1 * MINUTES}

```
2. In job.properties define: **nominal_time=${coord:nominalTime()}**
3. Then coordinator will run failed
> "Coord Job Materialization Error: Could not parse [${coord:nominalTime()}] 
> using [-MM-dd'T'HH:mm+0800] mask";


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java 
17e7fa0a9af3c160f98ea615bc73f3a1d7489aec 
  
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
 2e39689d62fcad3eb5d58f81dbd743f3e0a6b46f 


Diff: https://reviews.apache.org/r/59906/diff/3/

Changes: https://reviews.apache.org/r/59906/diff/2-3/


Testing
---


Thanks,

Wen Chi

[jira] [Updated] (OOZIE-2815) Oozie not always display job log

2017-06-19 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2815:

Attachment: OOZIE-2815.amend.002.patch

> Oozie not always display job log
> 
>
> Key: OOZIE-2815
> URL: https://issues.apache.org/jira/browse/OOZIE-2815
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-2815.amend.002.patch, OOZIE-2815-amend-1.patch, 
> OOZIE-2815-V2.patch, OOZIE-2815-V3.patch, OOZIE-2815-V4.patch, 
> OOZIE-2815-V5.patch
>
>
> There are few issues with log streaming. We will fix following things.
> 1. UI has an issue with displaying "loading... done". It used to show loading 
> done even if logs were not loaded entirely.
> 2. Server-server communication time out. The default time is 1 min. Setting 
> to 3 min same as UI.
> 3. We use to throw an error message if log scan duration is more than 
> configured duration. We will be truncating log.
> 4. No log scan duration check for audit and error log since it doesn't 
> support log filter.
> 5. Different buffer.len setting for error and audit log, so that partial 
> loading can be faster. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OOZIE-2957) Documentation states that starting a coordinator is possible

2017-06-19 Thread Jan Hentschel (JIRA)

Jan Hentschel created OOZIE-2957:


 Summary: Documentation states that starting a coordinator is 
possible
 Key: OOZIE-2957
 URL: https://issues.apache.org/jira/browse/OOZIE-2957
 Project: Oozie
  Issue Type: Bug
  Components: coordinator, docs
Affects Versions: 5.0.0
Reporter: Jan Hentschel
Assignee: Jan Hentschel


The documentation of the command line tools states that starting a coordinator 
is possible

{quote}---+++ Starting a Workflow, Coordinator or Bundle Job

Example:


$ oozie job -oozie http://localhost:11000/oozie -start 
14-20090525161321-oozie-joe


The =start= option starts a previously submitted workflow job, coordinator job 
or bundle job that is in =PREP= status.

After the command is executed the workflow job will be in =RUNNING= status, 
coordinator job will be in =RUNNING= status and
bundle job will be in =RUNNING=status.{quote}

As of OOZIE-923 this should not be possible. The documentation should be 
changed to not include coordinators in this section or mention that starting a 
coordinator from the CLI is not possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (OOZIE-2815) Oozie not always display job log

2017-06-19 Thread Andras Piros (JIRA)


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

Andras Piros reassigned OOZIE-2815:
---

Assignee: Andras Piros  (was: Satish Subhashrao Saley)

> Oozie not always display job log
> 
>
> Key: OOZIE-2815
> URL: https://issues.apache.org/jira/browse/OOZIE-2815
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-2815-amend-1.patch, OOZIE-2815-V2.patch, 
> OOZIE-2815-V3.patch, OOZIE-2815-V4.patch, OOZIE-2815-V5.patch
>
>
> There are few issues with log streaming. We will fix following things.
> 1. UI has an issue with displaying "loading... done". It used to show loading 
> done even if logs were not loaded entirely.
> 2. Server-server communication time out. The default time is 1 min. Setting 
> to 3 min same as UI.
> 3. We use to throw an error message if log scan duration is more than 
> configured duration. We will be truncating log.
> 4. No log scan duration check for audit and error log since it doesn't 
> support log filter.
> 5. Different buffer.len setting for error and audit log, so that partial 
> loading can be faster. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (OOZIE-2928) Unit Tests using LocalOozie fail randomly

2017-06-19 Thread Peter Bacsko (JIRA)


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

Peter Bacsko reassigned OOZIE-2928:
---

Assignee: Denes Bodo

> Unit Tests using LocalOozie fail randomly
> -
>
> Key: OOZIE-2928
> URL: https://issues.apache.org/jira/browse/OOZIE-2928
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>  Labels: Servlet
> Fix For: 5.0.0
>
> Attachments: 0001-Fix-random-LocalOozie-based-test-failure.patch, 
> 0001-Fix-random-LocalOozie-based-test-failure.patch
>
>
> Sometimes There is an erro message running unit tests: "LocalOozie is already 
> initialized" then fails all the tests using LocalOozie.
> There is already a BindException that 
> {noformat}
>  type="java.net.BindException">java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at 
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
> at java.net.ServerSocket.bind(ServerSocket.java:376)
> at java.net.ServerSocket.init(ServerSocket.java:237)
> at 
> org.mortbay.jetty.bio.SocketConnector.newServerSocket(SocketConnector.java:80)
> at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
> at 
> org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)
> at 
> org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)
> at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.Server.doStart(Server.java:233)
> at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at 
> org.apache.oozie.test.EmbeddedServletContainer.start(EmbeddedServletContainer.java:105)
> at org.apache.oozie.local.LocalOozie.start(LocalOozie.java:81)
> at 
> org.apache.oozie.command.coord.TestCoordRerunXCommand.setUp(TestCoordRerunXCommand.java:79)
> at junit.framework.TestCase.runBare(TestCase.java:132)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> 
> {noformat}
> The source of problem seems to be in EmbeddedServletContainer.java. First we 
> create a socket, get its port number, release the socket and use this port to 
> create server:
> {noformat}
> ServerSocket ss = new ServerSocket(0);
> port = ss.getLocalPort();
> ss.close();
> server.getConnectors()[0].setHost(host);
> server.getConnectors()[0].setPort(port);
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (OOZIE-2928) Unit Tests using LocalOozie fail randomly

2017-06-19 Thread Peter Bacsko (JIRA)


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

Peter Bacsko reassigned OOZIE-2928:
---

Assignee: (was: Peter Bacsko)

> Unit Tests using LocalOozie fail randomly
> -
>
> Key: OOZIE-2928
> URL: https://issues.apache.org/jira/browse/OOZIE-2928
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>  Labels: Servlet
> Fix For: 5.0.0
>
> Attachments: 0001-Fix-random-LocalOozie-based-test-failure.patch, 
> 0001-Fix-random-LocalOozie-based-test-failure.patch
>
>
> Sometimes There is an erro message running unit tests: "LocalOozie is already 
> initialized" then fails all the tests using LocalOozie.
> There is already a BindException that 
> {noformat}
>  type="java.net.BindException">java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at 
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
> at java.net.ServerSocket.bind(ServerSocket.java:376)
> at java.net.ServerSocket.init(ServerSocket.java:237)
> at 
> org.mortbay.jetty.bio.SocketConnector.newServerSocket(SocketConnector.java:80)
> at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
> at 
> org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)
> at 
> org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)
> at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.Server.doStart(Server.java:233)
> at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at 
> org.apache.oozie.test.EmbeddedServletContainer.start(EmbeddedServletContainer.java:105)
> at org.apache.oozie.local.LocalOozie.start(LocalOozie.java:81)
> at 
> org.apache.oozie.command.coord.TestCoordRerunXCommand.setUp(TestCoordRerunXCommand.java:79)
> at junit.framework.TestCase.runBare(TestCase.java:132)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> 
> {noformat}
> The source of problem seems to be in EmbeddedServletContainer.java. First we 
> create a socket, get its port number, release the socket and use this port to 
> create server:
> {noformat}
> ServerSocket ss = new ServerSocket(0);
> port = ss.getLocalPort();
> ss.close();
> server.getConnectors()[0].setHost(host);
> server.getConnectors()[0].setPort(port);
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (OOZIE-2928) Unit Tests using LocalOozie fail randomly

2017-06-19 Thread Peter Bacsko (JIRA)


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

Peter Bacsko reassigned OOZIE-2928:
---

Assignee: Peter Bacsko

> Unit Tests using LocalOozie fail randomly
> -
>
> Key: OOZIE-2928
> URL: https://issues.apache.org/jira/browse/OOZIE-2928
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Peter Bacsko
>  Labels: Servlet
> Fix For: 5.0.0
>
> Attachments: 0001-Fix-random-LocalOozie-based-test-failure.patch, 
> 0001-Fix-random-LocalOozie-based-test-failure.patch
>
>
> Sometimes There is an erro message running unit tests: "LocalOozie is already 
> initialized" then fails all the tests using LocalOozie.
> There is already a BindException that 
> {noformat}
>  type="java.net.BindException">java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at 
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
> at java.net.ServerSocket.bind(ServerSocket.java:376)
> at java.net.ServerSocket.init(ServerSocket.java:237)
> at 
> org.mortbay.jetty.bio.SocketConnector.newServerSocket(SocketConnector.java:80)
> at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
> at 
> org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)
> at 
> org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)
> at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.Server.doStart(Server.java:233)
> at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at 
> org.apache.oozie.test.EmbeddedServletContainer.start(EmbeddedServletContainer.java:105)
> at org.apache.oozie.local.LocalOozie.start(LocalOozie.java:81)
> at 
> org.apache.oozie.command.coord.TestCoordRerunXCommand.setUp(TestCoordRerunXCommand.java:79)
> at junit.framework.TestCase.runBare(TestCase.java:132)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> 
> {noformat}
> The source of problem seems to be in EmbeddedServletContainer.java. First we 
> create a socket, get its port number, release the socket and use this port to 
> create server:
> {noformat}
> ServerSocket ss = new ServerSocket(0);
> port = ss.getLocalPort();
> ss.close();
> server.getConnectors()[0].setHost(host);
> server.getConnectors()[0].setPort(port);
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2918) Delete LauncherMapper and its test

2017-06-19 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2918:
--

Testing JIRA OOZIE-2918

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 16 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}WARNING{color}: the current HEAD has 6 Javadoc warning(s)
{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 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: 1964
.Tests rerun: 88
.Tests failed at first run: 
org.apache.oozie.servlet.TestV0JobServlet,org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.jms.TestJMSJobEventListener,org.apache.oozie.action.hadoop.TestLauncherAM,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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

{color:red}. There is at least one warning, please check{color}

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

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

> Delete LauncherMapper and its test
> --
>
> Key: OOZIE-2918
> URL: https://issues.apache.org/jira/browse/OOZIE-2918
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
> Attachments: OOZIE-2918-01.patch, OOZIE-2918-02.patch
>
>
> While LauncherMapper itself is not used anymore it contains a bunch of static 
> methods that are referenced from different places in the code.
> We should refactor out code and related test cases to where they belong.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

2017-06-19 Thread Apache Jenkins Server

See

Re: Review Request 59906: Coordinator SLA should support to configure EL functions as variable

2017-06-19 Thread Wen Chi



> On 六月 19, 2017, 7:42 a.m., András Piros wrote:
> > core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java
> > Lines 870-871 (patched)
> > 
> >
> > You should at least `LOG.warn()`, but are you sure we shouldn't handle 
> > like that:
> > ```
> > throw new CommandException(ErrorCode.E1004, "Validation ERROR :" + 
> > e.getMessage(), e);
> > ```
> > 
> > Apart from that, instead of catching an `Exception`, please list all 
> > specific `Exception` types that can possibly occcur here. Code will be 
> > safer and much more readable.

As you can see: 
In **org.apache.oozie.coord.CoordELFunctions**
``java public static String ***evalAndWrap***(ELEvaluator eval, String expr) 
throws Exception``

So I use ``catch (Exception e)``, there is no ohter types;


I don't think add ``LOG.warn()`` is avaliable, user may be confused if there 
are lots of warn logs which will not affect user's coordinator;
As I said before:

coordinator.xml define SLA like this


  ${nominal_time}
  ${ 1 * HOURS}
  Notifying User for ${coord:nominalTime()} 
${coord:actualTime()} 



**should-end** and **notification-msg** are not variables defined in 
configuration, user may be confused if we log it in warn;
But we can log it in debug or trace I think;


- Wen


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


On 六月 19, 2017, 7:11 a.m., Wen Chi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59906/
> ---
> 
> (Updated 六月 19, 2017, 7:11 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Bugs: OOZIE-2929
> https://issues.apache.org/jira/browse/OOZIE-2929
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> 1. coordinator.xml define SLA like this
> ```xml
> 
>   ${nominal_time}
>   ${ 1 * HOURS}
>   ${1 * MINUTES}
> 
> ```
> 2. In job.properties define: **nominal_time=${coord:nominalTime()}**
> 3. Then coordinator will run failed
> > "Coord Job Materialization Error: Could not parse [${coord:nominalTime()}] 
> > using [-MM-dd'T'HH:mm+0800] mask";
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java 
> 17e7fa0a9af3c160f98ea615bc73f3a1d7489aec 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
>  2e39689d62fcad3eb5d58f81dbd743f3e0a6b46f 
> 
> 
> Diff: https://reviews.apache.org/r/59906/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Wen Chi
> 
>

Re: Review Request 59906: Coordinator SLA should support to configure EL functions as variable

2017-06-19 Thread András Piros


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




core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java
Lines 870-871 (patched)


You should at least `LOG.warn()`, but are you sure we shouldn't handle like 
that:
```
throw new CommandException(ErrorCode.E1004, "Validation ERROR :" + 
e.getMessage(), e);
```

Apart from that, instead of catching an `Exception`, please list all 
specific `Exception` types that can possibly occcur here. Code will be safer 
and much more readable.


- András Piros


On June 19, 2017, 7:11 a.m., Wen Chi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59906/
> ---
> 
> (Updated June 19, 2017, 7:11 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Bugs: OOZIE-2929
> https://issues.apache.org/jira/browse/OOZIE-2929
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> 1. coordinator.xml define SLA like this
> ```xml
> 
>   ${nominal_time}
>   ${ 1 * HOURS}
>   ${1 * MINUTES}
> 
> ```
> 2. In job.properties define: **nominal_time=${coord:nominalTime()}**
> 3. Then coordinator will run failed
> > "Coord Job Materialization Error: Could not parse [${coord:nominalTime()}] 
> > using [-MM-dd'T'HH:mm+0800] mask";
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java 
> 17e7fa0a9af3c160f98ea615bc73f3a1d7489aec 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
>  2e39689d62fcad3eb5d58f81dbd743f3e0a6b46f 
> 
> 
> Diff: https://reviews.apache.org/r/59906/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Wen Chi
> 
>

[jira] [Commented] (OOZIE-2916) Set a job name for the MR Action's child job

2017-06-19 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2916:
---

Thanks for contribution!
Please remove the cast for ((ActionXCommand.ActionExecutorContext) 
context).getAction().getName() in getJobName() that should fix the tests.

> Set a job name for the MR Action's child job
> 
>
> Key: OOZIE-2916
> URL: https://issues.apache.org/jira/browse/OOZIE-2916
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
> Fix For: 5.0.0
>
> Attachments: OOZIE-2889-001.patch
>
>
> The MR Action's child job (i.e. the MR Job) doesn't have a name.  It always 
> shows up as "N/A".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 59906: Coordinator SLA should support to configure EL functions as variable

2017-06-19 Thread Wen Chi


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

(Updated 六月 19, 2017, 7:11 a.m.)


Review request for oozie and András Piros.


Changes
---

Update new diff;
Add new testcase for resolveSLAContent;


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


Repository: oozie-git


Description
---

1. coordinator.xml define SLA like this
```xml

  ${nominal_time}
  ${ 1 * HOURS}
  ${1 * MINUTES}

```
2. In job.properties define: **nominal_time=${coord:nominalTime()}**
3. Then coordinator will run failed
> "Coord Job Materialization Error: Could not parse [${coord:nominalTime()}] 
> using [-MM-dd'T'HH:mm+0800] mask";


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java 
17e7fa0a9af3c160f98ea615bc73f3a1d7489aec 
  
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
 2e39689d62fcad3eb5d58f81dbd743f3e0a6b46f 


Diff: https://reviews.apache.org/r/59906/diff/2/

Changes: https://reviews.apache.org/r/59906/diff/1-2/


Testing
---


Thanks,

Wen Chi

[jira] [Updated] (OOZIE-2918) Delete LauncherMapper and its test

2017-06-19 Thread Attila Sasvari (JIRA)


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

Attila Sasvari updated OOZIE-2918:
--
Attachment: OOZIE-2918-02.patch

[~gezapeti] thanks for the review. 

Added back TestLauncher and removed tests that referenced LauncherMapper. 
Removed OozieLauncherOutputCommitter
Removed OozieLauncherOutputFormat
Renamed TestLauncherMapper
Removed OozieLauncherInputFormat and related classes (not used anymore)

[~pbacsko] someone will create a reviewboard request soon.

> Delete LauncherMapper and its test
> --
>
> Key: OOZIE-2918
> URL: https://issues.apache.org/jira/browse/OOZIE-2918
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
> Attachments: OOZIE-2918-01.patch, OOZIE-2918-02.patch
>
>
> While LauncherMapper itself is not used anymore it contains a bunch of static 
> methods that are referenced from different places in the code.
> We should refactor out code and related test cases to where they belong.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] Subscription: Oozie Patch Available

2017-06-19 Thread jira

Issue Subscription
Filter: Oozie Patch Available (110 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2943  Fix Findbugs warnings in oozie-sharelib-pig
https://issues.apache.org/jira/browse/OOZIE-2943
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2936  Fix Javadoc warnings from build
https://issues.apache.org/jira/browse/OOZIE-2936
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2931  multiple warnings during build for "no @param for"
https://issues.apache.org/jira/browse/OOZIE-2931
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2920  Document Distcp can copy files within a cluster
https://issues.apache.org/jira/browse/OOZIE-2920
OOZIE-2918  Delete LauncherMapper and its test
https://issues.apache.org/jira/browse/OOZIE-2918
OOZIE-2916  Set a job name for the MR Action's child job
https://issues.apache.org/jira/browse/OOZIE-2916
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2911  Re-add test testWfActionKillChildJob and adapt it to OYA
https://issues.apache.org/jira/browse/OOZIE-2911
OOZIE-2902  org.apache.oozie.action.hadoop.TestJavaActionExecutor fails after 
hadoop 2.6 upgrade
https://issues.apache.org/jira/browse/OOZIE-2902
OOZIE-2884  consolidate hadoop versions in pomfiles
https://issues.apache.org/jira/browse/OOZIE-2884
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2854  Oozie should handle transient DB problems
https://issues.apache.org/jira/browse/OOZIE-2854
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-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues.apache.org/jira/browse/OOZIE-2826
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-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2769  Extend

39 matches

Mail list logo