[jira] [Commented] (OOZIE-2684) Bad database schema error for WF_ACTIONS table

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2684:
--


Testing JIRA OOZIE-2684

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 100 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{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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/hive].
. {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/hive2].
. {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/streaming].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{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: 2092
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestHiveActionExecutor#testHiveAction
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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/PreCommit-OOZIE-Build/443/



> Bad database schema error for WF_ACTIONS table
> --
>
> Key: OOZIE-2684
> URL: https://issues.apache.org/jira/browse/OOZIE-2684
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-2684-00.patch
>
>
> In {{SchemaCheckerService}}, Oozie compares expected and found indexed 
> columns and generates the below error message which could be confusing to the 
> users.
> {noformat}
> 2016-09-16 12:39:26,564  INFO SchemaCheckXCommand:520 - 
> SERVER[c6402.ambari.apache.org] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] 
> ACTION[-] About to check database schema
> 2016-09-16 12:39:26,703 ERROR SchemaCheckXCommand:517 - 
> SERVER[c6402.ambari.apache.org] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] 
> ACTION[-] Found [1] extra indexes for columns in table [WF_ACTIONS]: [wf_id]
> 2016-09-16 12:39:26,723 ERROR SchemaCheckXCommand:517 - 
> SERVER[c6402.ambari.apache.org] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] 
> ACTION[-] Database schema is BAD! Check previous error log messages for 
> details
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2684 PreCommit Build #443

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2684
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/443/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [core].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2253 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-2684

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2092
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestHiveActionExecutor#testHiveAction
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/443/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  31790 0  100  3179  0   3842 --:--:-- --:--:-- --:--:--  
3839{"self":"https://issues.apache.org/jira/rest/api/2/issue/13006969/comment/16396539","id":"16396539","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 

[jira] [Commented] (OOZIE-2684) Bad database schema error for WF_ACTIONS table

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2684:
--

PreCommit-OOZIE-Build started


> Bad database schema error for WF_ACTIONS table
> --
>
> Key: OOZIE-2684
> URL: https://issues.apache.org/jira/browse/OOZIE-2684
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-2684-00.patch
>
>
> In {{SchemaCheckerService}}, Oozie compares expected and found indexed 
> columns and generates the below error message which could be confusing to the 
> users.
> {noformat}
> 2016-09-16 12:39:26,564  INFO SchemaCheckXCommand:520 - 
> SERVER[c6402.ambari.apache.org] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] 
> ACTION[-] About to check database schema
> 2016-09-16 12:39:26,703 ERROR SchemaCheckXCommand:517 - 
> SERVER[c6402.ambari.apache.org] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] 
> ACTION[-] Found [1] extra indexes for columns in table [WF_ACTIONS]: [wf_id]
> 2016-09-16 12:39:26,723 ERROR SchemaCheckXCommand:517 - 
> SERVER[c6402.ambari.apache.org] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] 
> ACTION[-] Database schema is BAD! Check previous error log messages for 
> details
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2364 PreCommit Build #442

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2364
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/442/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 789.04 KB...]
Checking patch core/src/main/resources/oozie-default.xml...
Checking patch core/src/test/java/org/apache/oozie/TestDagELFunctions.java...
Checking patch core/src/test/java/org/apache/oozie/TestSLAEventBean.java...
Checking patch core/src/test/java/org/apache/oozie/client/TestOozieCLI.java...
error: while searching for:
});
}

/**
 * Could not authenticate, Authentication failed, status: 404, message: Not 
Found
 */
public void testSlaEvents() throws Exception {
runTest(END_POINTS, SERVLET_CLASSES, IS_SECURITY_ENABLED, new 
Callable() {
@Override
public Void call() throws Exception {
Path appPath = new Path(getFsTestCaseDir(), "app");
getFileSystem().mkdirs(appPath);
String oozieUrl = getContextURL();
String[] args = new String[] {"sla", "-oozie", oozieUrl, 
"-len", "1" };

String out = runOozieCLIAndGetStderr(args);
assertTrue(out.contains("Could not authenticate, Authentication 
failed, status: 404, message: Not Found"));

return null;
}
});
}

public void testshareLibUpdate() throws Exception {
runTest(END_POINTS, SERVLET_CLASSES, IS_SECURITY_ENABLED, new 
Callable() {
@Override

error: patch failed: 
core/src/test/java/org/apache/oozie/client/TestOozieCLI.java:1229
error: core/src/test/java/org/apache/oozie/client/TestOozieCLI.java: patch does 
not apply
Checking patch 
core/src/test/java/org/apache/oozie/client/TestWorkflowClient.java...
Hunk #1 succeeded at 60 (offset 2 lines).
Hunk #2 succeeded at 71 (offset 2 lines).
Hunk #3 succeeded at 468 (offset 6 lines).
Checking patch 
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java...
Hunk #3 succeeded at 972 (offset 154 lines).
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestSLAEventsGetForFilterJPAExecutor.java...
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestSLAEventsGetForSeqIdJPAExecutor.java...
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestSLAEventsGetJPAExecutor.java...
Checking patch core/src/test/java/org/apache/oozie/store/TestSLAStore.java...
Checking patch core/src/test/java/org/apache/oozie/test/XDataTestCase.java...
Checking patch core/src/test/java/org/apache/oozie/test/XTestCase.java...
error: while searching for:
import org.apache.oozie.BundleJobBean;
import org.apache.oozie.CoordinatorActionBean;
import org.apache.oozie.CoordinatorJobBean;
import org.apache.oozie.SLAEventBean;
import org.apache.oozie.WorkflowActionBean;
import org.apache.oozie.WorkflowJobBean;
import org.apache.oozie.dependency.FSURIHandler;

error: patch failed: core/src/test/java/org/apache/oozie/test/XTestCase.java:62
error: core/src/test/java/org/apache/oozie/test/XTestCase.java: patch does not 
apply
Checking patch 
core/src/test/java/org/apache/oozie/util/db/TestSLADbOperations.java...
Checking patch 
core/src/test/java/org/apache/oozie/util/db/TestSLADbXOperations.java...
Checking patch docs/src/site/twiki/CoordinatorFunctionalSpec.twiki...
Hunk #1 succeeded at 3935 (offset 341 lines).
Checking patch docs/src/site/twiki/DG_CommandLineTool.twiki...
error: while searching for:
   -auth select authentication type 
[SIMPLE|KERBEROS]
   -oozieOozie URL
.
  oozie sla  : sla operations (Deprecated as of Oozie 4.0)
-authselect authentication type 
[SIMPLE|KERBEROS]
-len number of results (default '100', max 
limited by oozie server setting which defaults to '1000')
-offset  start offset (default '0')
-oozie   Oozie URL
-filter  
jobid=\;appname=
.
  oozie pig  -X  : submit a pig job, everything after '-X' 
are pass-through parameters to pig, any '-D' arguments after '-X' are put in 

-authselect authentication type 
[SIMPLE|KERBEROS]
-doasdoAs user, impersonates as the specified 
user.

error: patch failed: docs/src/site/twiki/DG_CommandLineTool.twiki:141
error: docs/src/site/twiki/DG_CommandLineTool.twiki: patch does not apply
Checking patch tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java...
Hunk #1 succeeded at 1139 (offset 54 lines).
Checking patch webapp/src/main/webapp/WEB-INF/web.xml...
Patch failed to apply to head of branch

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2364:
--


Testing JIRA OOZIE-2364

Cleaning local git workspace



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




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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2644) Skip queuing Notification Commands when there's nothing to notify

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2644:
--


Testing JIRA OOZIE-2644

Cleaning local git workspace



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




> Skip queuing Notification Commands when there's nothing to notify
> -
>
> Key: OOZIE-2644
> URL: https://issues.apache.org/jira/browse/OOZIE-2644
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 3.1.3
>Reporter: Robert Kanter
>Assignee: Azrael Seoeun
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2644.1.patch, OOZIE-2644.2.patch
>
>
> When you use the 
> [Workflow|https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html#a5_Workflow_Notifications]
>  or 
> [Coordinator|https://oozie.apache.org/docs/4.2.0/CoordinatorFunctionalSpec.html#a15._Coordinator_Notifications]
>  Notification features, Oozie can end up queuing up a lot of 
> {{WorkflowNotificationXCommand}} and {{CoordActionNotificationXCommand}}.  
> This happens even if there's no notification configured on the job (which I 
> imagine is most of the time); in this case, the {{execute}} method simply 
> does nothing.  This is wasteful and clogs the queue up.  
> We should change the code so that it doesn't queue up one of these Commands 
> unless there's actually a URL to notify.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2364:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2644 PreCommit Build #441

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2644
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/441/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 767.05 KB...]

error: patch failed: 
core/src/main/java/org/apache/oozie/local/LocalOozie.java:24
error: core/src/main/java/org/apache/oozie/local/LocalOozie.java: patch does 
not apply
Checking patch core/src/main/resources/oozie-default.xml...
Hunk #1 succeeded at 2408 (offset 93 lines).
Checking patch 
core/src/test/java/org/apache/oozie/command/coord/TestCoordActionNotificationXCommand.java...
Checking patch 
core/src/test/java/org/apache/oozie/command/coord/TestCoordActionsKillXCommand.java...
Checking patch 
core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java...
error: while searching for:
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.io.IOException;

public class TestWorkflowNotificationXCommand extends XTestCase {
private EmbeddedServletContainer container;

public static class CallbackServlet extends HttpServlet {
public static volatile String JOB_ID = null;

error: patch failed: 
core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java:34
error: 
core/src/test/java/org/apache/oozie/command/wf/TestWorkflowNotificationXCommand.java:
 patch does not apply
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobQueryExecutor.java...
Checking patch core/src/test/java/org/apache/oozie/test/XDataTestCase.java...
Checking patch src/main/java/org/apache/oozie/CoordinatorActionBean.java...
error: src/main/java/org/apache/oozie/CoordinatorActionBean.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/CoordinatorJobBean.java...
error: src/main/java/org/apache/oozie/CoordinatorJobBean.java: No such file or 
directory
Checking patch 
src/main/java/org/apache/oozie/command/NotificationXCommand.java...
error: src/main/java/org/apache/oozie/command/NotificationXCommand.java: No 
such file or directory
Checking patch src/main/java/org/apache/oozie/command/XCommand.java...
error: src/main/java/org/apache/oozie/command/XCommand.java: No such file or 
directory
Checking patch 
src/main/java/org/apache/oozie/command/coord/CoordActionSkipXCommand.java...
error: 
src/main/java/org/apache/oozie/command/coord/CoordActionSkipXCommand.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/coord/CoordActionStartXCommand.java...
error: 
src/main/java/org/apache/oozie/command/coord/CoordActionStartXCommand.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/coord/CoordActionTimeOutXCommand.java...
error: 
src/main/java/org/apache/oozie/command/coord/CoordActionTimeOutXCommand.java: 
No such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/coord/CoordActionsKillXCommand.java...
error: 
src/main/java/org/apache/oozie/command/coord/CoordActionsKillXCommand.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java...
error: 
src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java:
 No such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/coord/CoordRerunXCommand.java...
error: src/main/java/org/apache/oozie/command/coord/CoordRerunXCommand.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/wf/ActionCheckXCommand.java...
error: src/main/java/org/apache/oozie/command/wf/ActionCheckXCommand.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/wf/ActionEndXCommand.java...
error: src/main/java/org/apache/oozie/command/wf/ActionEndXCommand.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/wf/ActionKillXCommand.java...
error: src/main/java/org/apache/oozie/command/wf/ActionKillXCommand.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/command/wf/ActionStartXCommand.java...
error: src/main/java/org/apache/oozie/command/wf/ActionStartXCommand.java: No 
such file or directory
Checking patch src/main/java/org/apache/oozie/command/wf/ActionXCommand.java...
error: src/main/java/org/apache/oozie/command/wf/ActionXCommand.java: No such 
file or directory
Checking patch src/main/java/org/apache/oozie/command/wf/KillXCommand.java...
error: src/main/java/org/apache/oozie/command/wf/KillXCommand.java: No such 
file or directory
Checking patch src/main/java/org/apache/oozie/command/wf/ResumeXCommand.java...
error: src/main/java/org/apache/oozie/command/wf/ResumeXCommand.java: No such 
file or directory
Checking patch 

[jira] [Commented] (OOZIE-2644) Skip queuing Notification Commands when there's nothing to notify

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2644:
--

PreCommit-OOZIE-Build started


> Skip queuing Notification Commands when there's nothing to notify
> -
>
> Key: OOZIE-2644
> URL: https://issues.apache.org/jira/browse/OOZIE-2644
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 3.1.3
>Reporter: Robert Kanter
>Assignee: Azrael Seoeun
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2644.1.patch, OOZIE-2644.2.patch
>
>
> When you use the 
> [Workflow|https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html#a5_Workflow_Notifications]
>  or 
> [Coordinator|https://oozie.apache.org/docs/4.2.0/CoordinatorFunctionalSpec.html#a15._Coordinator_Notifications]
>  Notification features, Oozie can end up queuing up a lot of 
> {{WorkflowNotificationXCommand}} and {{CoordActionNotificationXCommand}}.  
> This happens even if there's no notification configured on the job (which I 
> imagine is most of the time); in this case, the {{execute}} method simply 
> does nothing.  This is wasteful and clogs the queue up.  
> We should change the code so that it doesn't queue up one of these Commands 
> unless there's actually a URL to notify.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2779) Mask Hive2 action Beeline JDBC password

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2779:
--


Testing JIRA OOZIE-2779

Cleaning local git workspace



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




> Mask Hive2 action Beeline JDBC password
> ---
>
> Key: OOZIE-2779
> URL: https://issues.apache.org/jira/browse/OOZIE-2779
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Major
>  Labels: security
> Fix For: trunk
>
> Attachments: OOZIE-2779-00.patch, OOZIE-2779-01.patch, 
> OOZIE-2779-01.patch
>
>
> Hive2 Oozie launcher job prints the JDBC password into launcher stdout logs.
> {noformat}
> Beeline command arguments :
>  -u
>  jdbc:hive2://source-1:1/default
>  -n
>  ambari-qa
>  -p
>  DUMMY
>  -d
>  org.apache.hive.jdbc.HiveDriver
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2779 PreCommit Build #440

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2779
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/440/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 761.91 KB...]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  7.142 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  6.258 s]
[INFO] Apache Oozie Core .. SUCCESS [01:25 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.860 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.836 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  9.119 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 10.054 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.976 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.831 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 10.877 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.024 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.173 s]
[INFO] Apache Oozie WebApp  SUCCESS [  8.368 s]
[INFO] Apache Oozie Tools . SUCCESS [ 12.581 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.745 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.859 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.223 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.655 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 04:00 min
[INFO] Finished at: 2018-03-13T02:51:16Z
[INFO] Final Memory: 170M/1336M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch 
sharelib/hive2/src/main/java/org/apache/oozie/action/hadoop/Hive2Main.java...
error: while searching for:
arguments.add(oozieConfig.getKey() + "=" + oozieConfig.getValue());
}

System.out.println("Beeline command arguments :");
for (String arg : arguments) {
System.out.println(" " + arg);
}
System.out.println();

LauncherMainHadoopUtils.killChildYarnJobs(actionConf);


error: patch failed: 
sharelib/hive2/src/main/java/org/apache/oozie/action/hadoop/Hive2Main.java:227
error: 
sharelib/hive2/src/main/java/org/apache/oozie/action/hadoop/Hive2Main.java: 
patch does not apply
Checking patch 
sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/JavaMain.java...
error: while searching for:

Class klass = actionConf.getClass(JAVA_MAIN_CLASS, Object.class);
System.out.println("Main class: " + klass.getName());
LauncherMapper.printArgs("Arguments :", args);
System.out.println();
Method mainMethod = klass.getMethod("main", String[].class);
try {

error: patch failed: 
sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/JavaMain.java:48
error: 
sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/JavaMain.java: 
patch does not apply
Checking patch 
sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java...
error: 
sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java:
 No such file or directory
Checking patch 
sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java...
error: while searching for:
throw new RuntimeException("Action Configuration does not have [" + 
SqoopActionExecutor.SQOOP_ARGS + "] property");
}

LauncherMapper.printArgs("Sqoop command arguments :", sqoopArgs);
LauncherMainHadoopUtils.killChildYarnJobs(sqoopConf);


System.out.println("=");

error: patch failed: 
sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java:170
error: 
sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java: 
patch does not apply
Checking patch 
hive2/src/main/java/org/apache/oozie/action/hadoop/Hive2Main.java...
error: hive2/src/main/java/org/apache/oozie/action/hadoop/Hive2Main.java: No 
such file or directory
Checking patch 
oozie/src/main/java/org/apache/oozie/action/hadoop/JavaMain.java...
error: oozie/src/main/java/org/apache/oozie/action/hadoop/JavaMain.java: No 
such file or directory
Checking patch 

[jira] [Commented] (OOZIE-2779) Mask Hive2 action Beeline JDBC password

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2779:
--

PreCommit-OOZIE-Build started


> Mask Hive2 action Beeline JDBC password
> ---
>
> Key: OOZIE-2779
> URL: https://issues.apache.org/jira/browse/OOZIE-2779
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Major
>  Labels: security
> Fix For: trunk
>
> Attachments: OOZIE-2779-00.patch, OOZIE-2779-01.patch, 
> OOZIE-2779-01.patch
>
>
> Hive2 Oozie launcher job prints the JDBC password into launcher stdout logs.
> {noformat}
> Beeline command arguments :
>  -u
>  jdbc:hive2://source-1:1/default
>  -n
>  ambari-qa
>  -p
>  DUMMY
>  -d
>  org.apache.hive.jdbc.HiveDriver
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1376:
--


Testing JIRA OOZIE-1376

Cleaning local git workspace



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




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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1376 PreCommit Build #439

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1376
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/439/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 761.46 KB...]
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  1.883 s]
[INFO] Apache Oozie Client  SUCCESS [ 19.196 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 13.503 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  6.550 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  5.358 s]
[INFO] Apache Oozie Core .. SUCCESS [01:20 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.505 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.646 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  8.224 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  8.868 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.827 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.751 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 11.036 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.051 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.368 s]
[INFO] Apache Oozie WebApp  SUCCESS [  8.598 s]
[INFO] Apache Oozie Tools . SUCCESS [ 13.165 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.796 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.982 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.319 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.730 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:50 min
[INFO] Finished at: 2018-03-13T02:45:12Z
[INFO] Final Memory: 171M/1937M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch 
core/src/test/java/org/apache/oozie/service/TestProxyUserService.java...
Hunk #1 succeeded at 183 (offset 1 line).
Hunk #2 succeeded at 195 (offset 1 line).
Checking patch 
core/src/test/java/org/apache/oozie/service/TestAuthorizationService.java...
error: while searching for:
IOUtils.copyCharStream(adminListReader, adminListWriter);
}
else {
conf.set(AuthorizationService.CONF_ADMIN_GROUPS, getTestGroup());
}
conf.set(Services.CONF_SERVICE_CLASSES,
 conf.get(Services.CONF_SERVICE_CLASSES) + "," + 
AuthorizationService.class.getName() +

error: patch failed: 
core/src/test/java/org/apache/oozie/service/TestAuthorizationService.java:84
error: 
core/src/test/java/org/apache/oozie/service/TestAuthorizationService.java: 
patch does not apply
Checking patch 
core/src/main/java/org/apache/oozie/service/ProxyUserService.java...
Hunk #1 succeeded at 26 (offset 1 line).
Hunk #2 succeeded at 86 (offset 1 line).
Hunk #3 succeeded at 102 (offset 1 line).
Hunk #4 succeeded at 115 (offset 1 line).
Hunk #5 succeeded at 146 (offset 1 line).
Checking patch 
core/src/main/java/org/apache/oozie/service/AuthorizationService.java...
Hunk #1 succeeded at 76 (offset 10 lines).
Hunk #2 succeeded at 132 (offset 22 lines).
Hunk #3 succeeded at 156 (offset 22 lines).
Hunk #4 succeeded at 189 (offset 22 lines).
Hunk #5 succeeded at 203 (offset 22 lines).
Hunk #6 succeeded at 305 (offset 22 lines).
Checking patch core/src/main/conf/oozie-site.xml...
Hunk #1 succeeded at 48 (offset -308 lines).
Checking patch core/src/main/conf/adminusers.txt...
Checking patch 
src/test/java/org/apache/oozie/service/TestProxyUserService.java...
error: src/test/java/org/apache/oozie/service/TestProxyUserService.java: No 
such file or directory
Checking patch 
src/test/java/org/apache/oozie/service/TestAuthorizationService.java...
error: src/test/java/org/apache/oozie/service/TestAuthorizationService.java: No 
such file or directory
Checking patch src/main/java/org/apache/oozie/service/ProxyUserService.java...
error: src/main/java/org/apache/oozie/service/ProxyUserService.java: No such 
file or directory
Checking patch 

Failed: OOZIE-2338 PreCommit Build #438

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2338
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/438/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 760.30 KB...]
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target/test-classes
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Some input files use or override a deprecated API.
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  2.052 s]
[INFO] Apache Oozie Client  SUCCESS [ 20.884 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 14.657 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  7.290 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  5.759 s]
[INFO] Apache Oozie Core .. SUCCESS [01:23 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.838 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.414 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  7.638 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  8.779 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  6.331 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.813 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 10.022 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.043 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.203 s]
[INFO] Apache Oozie WebApp  SUCCESS [  8.887 s]
[INFO] Apache Oozie Tools . SUCCESS [ 13.054 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.788 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.585 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.260 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.551 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:55 min
[INFO] Finished at: 2018-03-13T02:39:25Z
[INFO] Final Memory: 169M/1928M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch 
core/src/main/java/org/apache/oozie/service/ConfigurationService.java...
error: while searching for:
private static final Set MASK_PROPS = new HashSet();
private static Map defaultConfigs = new 
HashMap();

private static Method getPasswordMethod;

static {

error: patch failed: 
core/src/main/java/org/apache/oozie/service/ConfigurationService.java:97
error: core/src/main/java/org/apache/oozie/service/ConfigurationService.java: 
patch does not apply
Checking patch 
core/src/main/java/org/apache/oozie/service/HCatAccessorService.java...
Checking patch 
core/src/main/java/org/apache/oozie/sla/listener/SLAEmailEventListener.java...
Checking patch core/src/main/resources/oozie-default.xml...
Hunk #1 succeeded at 238 (offset 27 lines).
Hunk #2 succeeded at 2975 (offset 227 lines).
Checking patch docs/src/site/twiki/DG_EmailActionExtension.twiki...
Checking patch 
src/main/java/org/apache/oozie/service/ConfigurationService.java...
error: src/main/java/org/apache/oozie/service/ConfigurationService.java: No 
such file or directory

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1376:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2338) Invalid configuration defined reported for some valid configs

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2338:
--


Testing JIRA OOZIE-2338

Cleaning local git workspace



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




> Invalid configuration defined reported for some valid configs
> -
>
> Key: OOZIE-2338
> URL: https://issues.apache.org/jira/browse/OOZIE-2338
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2338.001.patch, OOZIE-2338.002.patch
>
>
> OOZIE-1890 moved all default config values from the code and oozie-site into 
> oozie-default; it also added a WARN message on startup when a config is found 
> in oozie-site that's not defined in oozie-default.  
> However, this can produce some false positives.  In particular, we observed 
> these:
> {noformat}
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.auth]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.host]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.HCatAccessorService.hcat.configuration]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.from.address]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.ProxyUserService.proxyuser.hue.hosts]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.GroupsService.hadoop.security.group.mapping]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.port]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.ProxyUserService.proxyuser.hue.groups]
> {noformat}
> While harmful, these messages may be concerning or confusing for users.
> Some of these are simply missing from oozie-default (because they have no 
> default value?), while others such as the ProxyUserService configs, will 
> require special handling because the property name can vary.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2259) Create a callback action

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2259:
--


Testing JIRA OOZIE-2259

Cleaning local git workspace



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




> Create a callback action 
> -
>
> Key: OOZIE-2259
> URL: https://issues.apache.org/jira/browse/OOZIE-2259
> Project: Oozie
>  Issue Type: New Feature
>  Components: action
>Reporter: Jaydeep Vishwakarma
>Assignee: Jaydeep Vishwakarma
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2259-v1.patch, OOZIE-2259-v3.patch, 
> OOZIE-2259-v4.patch, OOZIE-2259-v5.patch, OOZIE-2259-v8.patch, 
> OOZIE-2259-v9.patch, OOZIE-2259_v6.patch, OOZIE-2259_v7.patch
>
>
> Need an action to send notification to external server by oozie. We should be 
> able to do multiple types of callback, Currently I know jms and http call. It 
> should suppose to have capability to call diffrent types of methods along 
> with n number of arguments. 
> The sample workflow with callback action 
> {code:xml}
> 
> ...
> 
> 
>   [HOST]
>   [METHOD]
>   
>   [KEY][VALUE]
>   
> ...
> 
> ...
> 
> ...
> 
> {code}
> HOST : by the host system can figure out if it is http or jms callback 
> action. System will send the notification to that host.
> METHOD : it can be POST/GET/QUEUE/TOPIC



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2338) Invalid configuration defined reported for some valid configs

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2338:
--

PreCommit-OOZIE-Build started


> Invalid configuration defined reported for some valid configs
> -
>
> Key: OOZIE-2338
> URL: https://issues.apache.org/jira/browse/OOZIE-2338
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2338.001.patch, OOZIE-2338.002.patch
>
>
> OOZIE-1890 moved all default config values from the code and oozie-site into 
> oozie-default; it also added a WARN message on startup when a config is found 
> in oozie-site that's not defined in oozie-default.  
> However, this can produce some false positives.  In particular, we observed 
> these:
> {noformat}
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.auth]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.host]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.HCatAccessorService.hcat.configuration]
> 2015-08-18 01:16:32,365 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.from.address]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.ProxyUserService.proxyuser.hue.hosts]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.GroupsService.hadoop.security.group.mapping]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, [oozie.email.smtp.port]
> 2015-08-18 01:16:32,366 WARN org.apache.oozie.service.ConfigurationService: 
> SERVER[] Invalid configuration defined, 
> [oozie.service.ProxyUserService.proxyuser.hue.groups]
> {noformat}
> While harmful, these messages may be concerning or confusing for users.
> Some of these are simply missing from oozie-default (because they have no 
> default value?), while others such as the ProxyUserService configs, will 
> require special handling because the property name can vary.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2259 PreCommit Build #437

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2259
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/437/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 762.22 KB...]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.960 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  8.080 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  9.661 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  9.979 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  6.091 s]
[INFO] Apache Oozie Examples .. SUCCESS [ 10.218 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 10.442 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.349 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.032 s]
[INFO] Apache Oozie WebApp  SUCCESS [  8.222 s]
[INFO] Apache Oozie Tools . SUCCESS [ 12.366 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.724 s]
[INFO] Apache Oozie Server  SUCCESS [ 11.064 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.180 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.693 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 04:17 min
[INFO] Finished at: 2018-03-13T02:33:23Z
[INFO] Final Memory: 169M/1274M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch client/src/main/java/org/apache/oozie/cli/OozieCLI.java...
error: while searching for:
"hive2-action-0.1.xsd")));
sources.add(new 
StreamSource(Thread.currentThread().getContextClassLoader()
.getResourceAsStream("spark-action-0.1.xsd")));
SchemaFactory factory = 
SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
Schema schema = factory.newSchema(sources.toArray(new 
StreamSource[sources.size()]));
Validator validator = schema.newValidator();

error: patch failed: 
client/src/main/java/org/apache/oozie/cli/OozieCLI.java:2095
error: client/src/main/java/org/apache/oozie/cli/OozieCLI.java: patch does not 
apply
Checking patch client/src/main/resources/callback-action-0.1.xsd...
Checking patch 
core/src/main/java/org/apache/oozie/action/callback/CallBack.java...
Checking patch 
core/src/main/java/org/apache/oozie/action/callback/CallbackActionExecutor.java...
Checking patch 
core/src/main/java/org/apache/oozie/action/callback/HTTPCallBack.java...
Checking patch 
core/src/main/java/org/apache/oozie/action/callback/JMSCallBack.java...
Checking patch 
core/src/main/java/org/apache/oozie/action/callback/JMSNotification.java...
Checking patch 
core/src/main/java/org/apache/oozie/service/CallbackActionService.java...
Checking patch core/src/main/resources/oozie-default.xml...
error: while searching for:
org.apache.oozie.service.ProxyUserService,
org.apache.oozie.service.XLogStreamingService,
org.apache.oozie.service.JvmPauseMonitorService,
org.apache.oozie.service.SparkConfigurationService


All services to be created and managed by Oozie Services singleton.

error: patch failed: core/src/main/resources/oozie-default.xml:130
error: core/src/main/resources/oozie-default.xml: patch does not apply
Checking patch 
core/src/test/java/org/apache/oozie/action/callback/TestCallbackActionExecutor.java...
Checking patch docs/src/site/twiki/DG_CallbackActionExtension.twiki...
Checking patch docs/src/site/twiki/DG_CommandLineTool.twiki...
Hunk #1 succeeded at 1382 (offset 95 lines).
Hunk #2 succeeded at 1439 (offset 95 lines).
Checking patch docs/src/site/twiki/index.twiki...
Checking patch src/main/java/org/apache/oozie/cli/OozieCLI.java...
error: src/main/java/org/apache/oozie/cli/OozieCLI.java: No such file or 
directory
Checking patch src/main/resources/callback-action-0.1.xsd...
Checking patch src/main/java/org/apache/oozie/action/callback/CallBack.java...
Checking patch 
src/main/java/org/apache/oozie/action/callback/CallbackActionExecutor.java...
Checking patch 
src/main/java/org/apache/oozie/action/callback/HTTPCallBack.java...
Checking patch 
src/main/java/org/apache/oozie/action/callback/JMSCallBack.java...
Checking patch 

[jira] [Commented] (OOZIE-2259) Create a callback action

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2259:
--

PreCommit-OOZIE-Build started


> Create a callback action 
> -
>
> Key: OOZIE-2259
> URL: https://issues.apache.org/jira/browse/OOZIE-2259
> Project: Oozie
>  Issue Type: New Feature
>  Components: action
>Reporter: Jaydeep Vishwakarma
>Assignee: Jaydeep Vishwakarma
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2259-v1.patch, OOZIE-2259-v3.patch, 
> OOZIE-2259-v4.patch, OOZIE-2259-v5.patch, OOZIE-2259-v8.patch, 
> OOZIE-2259-v9.patch, OOZIE-2259_v6.patch, OOZIE-2259_v7.patch
>
>
> Need an action to send notification to external server by oozie. We should be 
> able to do multiple types of callback, Currently I know jms and http call. It 
> should suppose to have capability to call diffrent types of methods along 
> with n number of arguments. 
> The sample workflow with callback action 
> {code:xml}
> 
> ...
> 
> 
>   [HOST]
>   [METHOD]
>   
>   [KEY][VALUE]
>   
> ...
> 
> ...
> 
> ...
> 
> {code}
> HOST : by the host system can figure out if it is http or jms callback 
> action. System will send the notification to that host.
> METHOD : it can be POST/GET/QUEUE/TOPIC



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2231) Upgrade curator to latest version 2.12.0

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2231:
--


Testing JIRA OOZIE-2231

Cleaning local git workspace



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




> Upgrade curator to latest version 2.12.0
> 
>
> Key: OOZIE-2231
> URL: https://issues.apache.org/jira/browse/OOZIE-2231
> Project: Oozie
>  Issue Type: Bug
>  Components: HA
>Reporter: Purshotam Shah
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch, 
> OOZIE-2231-02.patch, OOZIE-2231-02.patch, OOZIE-2231-03.patch, 
> OOZIE-2231-04.patch, OOZIE-2231-05.patch, OOZIE-2231-06.patch
>
>
> It have some fix related to InterProcessReadWriteLock, ChildReaper, 
> LeaderSelector which we use.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2231 PreCommit Build #436

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2231
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/436/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 760.55 KB...]
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target/test-classes
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Some input files use or override a deprecated API.
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  1.690 s]
[INFO] Apache Oozie Client  SUCCESS [ 17.054 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 12.078 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  6.023 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  5.060 s]
[INFO] Apache Oozie Core .. SUCCESS [01:14 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.150 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  8.359 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  7.460 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  8.336 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.556 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.069 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [  9.285 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.021 s]
[INFO] Apache Oozie Docs .. SUCCESS [  2.815 s]
[INFO] Apache Oozie WebApp  SUCCESS [  7.730 s]
[INFO] Apache Oozie Tools . SUCCESS [ 12.211 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.691 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.498 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.052 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.215 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:31 min
[INFO] Finished at: 2018-03-13T02:26:35Z
[INFO] Final Memory: 169M/1894M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch 
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java...
Hunk #10 succeeded at 1057 (offset 5 lines).
Hunk #11 succeeded at 1121 (offset 15 lines).
Hunk #12 succeeded at 1195 (offset 15 lines).
Hunk #13 succeeded at 1793 (offset 16 lines).
Hunk #14 succeeded at 1930 (offset 16 lines).
Checking patch 
core/src/main/java/org/apache/oozie/service/JvmPauseMonitorService.java...
Checking patch docs/src/site/twiki/DG_QuickStart.twiki...
Checking patch docs/src/site/twiki/ENG_Building.twiki...
Checking patch pom.xml...
error: while searching for:
 2.10
 hadoop200
 0.8.4

 9.2.19.v20160908

 0.9.94
 2.4.2
 2.11.0
 2.5.0
 1.9.13
 1.2.17
 5.13.3

error: patch failed: pom.xml:103
error: pom.xml: patch does not apply
Checking patch sharelib/pig/pom.xml...
fatal: git diff header lacks filename information when removing 1 leading 
pathname component (line 255)
Patch failed to apply to head of branch

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 

[jira] [Commented] (OOZIE-2231) Upgrade curator to latest version 2.12.0

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2231:
--

PreCommit-OOZIE-Build started


> Upgrade curator to latest version 2.12.0
> 
>
> Key: OOZIE-2231
> URL: https://issues.apache.org/jira/browse/OOZIE-2231
> Project: Oozie
>  Issue Type: Bug
>  Components: HA
>Reporter: Purshotam Shah
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch, 
> OOZIE-2231-02.patch, OOZIE-2231-02.patch, OOZIE-2231-03.patch, 
> OOZIE-2231-04.patch, OOZIE-2231-05.patch, OOZIE-2231-06.patch
>
>
> It have some fix related to InterProcessReadWriteLock, ChildReaper, 
> LeaderSelector which we use.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1599 PreCommit Build #435

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1599
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/435/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [core].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2252 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-1599

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
-1 the patch contains 1 line(s) with trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2092
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionInputCheckXCommand#testNone
TestStatusTransitService#testBundleStatusTransitWithLock
TestHiveActionExecutor#testHiveAction
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/435/

Adding comment to JIRA
  % 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{"self":"https://issues.apache.org/jira/rest/api/2/issue/12676230/comment/16396414","id":"16396414","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1599:
--


Testing JIRA OOZIE-1599

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:red}-1{color} the patch contains 1 line(s) with 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 100 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{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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/hive].
. {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/hive2].
. {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/streaming].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{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: 2092
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionInputCheckXCommand#testNone
TestStatusTransitService#testBundleStatusTransitWithLock
TestHiveActionExecutor#testHiveAction
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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/PreCommit-OOZIE-Build/435/



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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2513 PreCommit Build #434

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2513
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/434/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 773.39 KB...]
error: while searching for:
import org.apache.oozie.test.EmbeddedServletContainer;
import org.apache.oozie.test.ZKXTestCase;
import org.apache.oozie.util.DateUtils;
import org.apache.oozie.util.XLogFilter;
import org.apache.oozie.util.ZKUtils;

public class TestZKXLogStreamingService extends ZKXTestCase {

error: patch failed: 
core/src/test/java/org/apache/oozie/service/TestZKXLogStreamingService.java:32
error: 
core/src/test/java/org/apache/oozie/service/TestZKXLogStreamingService.java: 
patch does not apply
Checking patch core/src/test/java/org/apache/oozie/util/TestLogStreamer.java...
error: while searching for:
import java.io.FileOutputStream;
import java.io.FileWriter;
import java.io.IOException;
import java.io.StringWriter;
import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.Calendar;
import java.util.Date;
import java.util.zip.GZIPOutputStream;

import org.apache.oozie.command.CommandException;
import org.apache.oozie.service.ServiceException;
import org.apache.oozie.service.Services;
import org.apache.oozie.test.XTestCase;

public class TestLogStreamer extends XTestCase {

error: patch failed: 
core/src/test/java/org/apache/oozie/util/TestLogStreamer.java:22
error: core/src/test/java/org/apache/oozie/util/TestLogStreamer.java: patch 
does not apply
Checking patch 
core/src/test/java/org/apache/oozie/util/TestXLogUserFilterParam.java...
error: while searching for:
private String doStreamLog(XLogFilter xf, Date startDate, Date endDate) 
throws Exception {
StringWriter w = new StringWriter();
Services.get().get(XLogStreamingService.class)
.streamLog(xf, startDate, endDate, w, new HashMap());
return w.toString();
}


error: patch failed: 
core/src/test/java/org/apache/oozie/util/TestXLogUserFilterParam.java:397
error: core/src/test/java/org/apache/oozie/util/TestXLogUserFilterParam.java: 
patch does not apply
Checking patch src/main/java/org/apache/oozie/BaseEngine.java...
error: src/main/java/org/apache/oozie/BaseEngine.java: No such file or directory
Checking patch src/main/java/org/apache/oozie/BundleEngine.java...
error: src/main/java/org/apache/oozie/BundleEngine.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/CoordinatorEngine.java...
error: src/main/java/org/apache/oozie/CoordinatorEngine.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/DagEngine.java...
error: src/main/java/org/apache/oozie/DagEngine.java: No such file or directory
Checking patch src/main/java/org/apache/oozie/service/XLogService.java...
error: src/main/java/org/apache/oozie/service/XLogService.java: No such file or 
directory
Checking patch 
src/main/java/org/apache/oozie/service/XLogStreamingService.java...
error: src/main/java/org/apache/oozie/service/XLogStreamingService.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/service/ZKXLogStreamingService.java...
error: src/main/java/org/apache/oozie/service/ZKXLogStreamingService.java: No 
such file or directory
Checking patch src/main/java/org/apache/oozie/servlet/V0JobServlet.java...
error: src/main/java/org/apache/oozie/servlet/V0JobServlet.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/servlet/V1JobServlet.java...
error: src/main/java/org/apache/oozie/servlet/V1JobServlet.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/util/XLogAuditFilter.java...
error: src/main/java/org/apache/oozie/util/XLogAuditFilter.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/util/XLogAuditStreamer.java...
error: src/main/java/org/apache/oozie/util/XLogAuditStreamer.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/util/XLogErrorStreamer.java...
error: src/main/java/org/apache/oozie/util/XLogErrorStreamer.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/util/XLogFilter.java...
error: src/main/java/org/apache/oozie/util/XLogFilter.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/util/XLogStreamer.java...
error: src/main/java/org/apache/oozie/util/XLogStreamer.java: No such file or 
directory
Checking patch 
src/test/java/org/apache/oozie/TestCoordinatorEngineStreamLog.java...
error: src/test/java/org/apache/oozie/TestCoordinatorEngineStreamLog.java: No 
such file or directory
Checking patch 
src/test/java/org/apache/oozie/service/TestXLogStreamingService.java...
error: src/test/java/org/apache/oozie/service/TestXLogStreamingService.java: No 
such file or directory
Checking patch 

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1599:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2513) log.scan.duration should not be used for error and audit logs

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2513:
--


Testing JIRA OOZIE-2513

Cleaning local git workspace



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




> log.scan.duration should not be used for error and audit logs
> -
>
> Key: OOZIE-2513
> URL: https://issues.apache.org/jira/browse/OOZIE-2513
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2513-V1.patch, OOZIE-2513-V2.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2461) Workflow, Coordinator and Bundle job querying should have last modified filter

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2461:
--


Testing JIRA OOZIE-2461

Cleaning local git workspace



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




> Workflow, Coordinator and Bundle job querying should have last modified filter
> --
>
> Key: OOZIE-2461
> URL: https://issues.apache.org/jira/browse/OOZIE-2461
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2461-1.patch, OOZIE-2461-10.patch, 
> OOZIE-2461-11.patch, OOZIE-2461-6.patch, OOZIE-2461-7.patch, 
> OOZIE-2461-8.patch, OOZIE-2461-9.patch
>
>
> To get currently running coordinator and id, one user had to do
> http://localhost:11000/oozie/v1/jobs?jobtype=coord=user%3satish_1.0%3B=1=3000
> They could not use name in the filter as they include a version and keep 
> changing. For eg:
> urs_satish_filter-0.1-daily-coord
> urs_puru_service-0.4-hourly-coord
> It would be good to have last modified filter to get recently active 
> coordinators.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2513) log.scan.duration should not be used for error and audit logs

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2513:
--

PreCommit-OOZIE-Build started


> log.scan.duration should not be used for error and audit logs
> -
>
> Key: OOZIE-2513
> URL: https://issues.apache.org/jira/browse/OOZIE-2513
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2513-V1.patch, OOZIE-2513-V2.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2461 PreCommit Build #433

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2461
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/433/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 771.81 KB...]
package org.apache.oozie.executor.jpa;

import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;

import org.apache.oozie.CoordinatorJobBean;
import org.apache.oozie.CoordinatorJobInfo;
import org.apache.oozie.client.CoordinatorJob;
import org.apache.oozie.client.OozieClient;
import org.apache.oozie.service.JPAService;
import org.apache.oozie.service.Services;
import org.apache.oozie.test.XDataTestCase;

error: patch failed: 
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobInfoGetJPAExecutor.java:19
error: 
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobInfoGetJPAExecutor.java:
 patch does not apply
Checking patch 
core/src/test/java/org/apache/oozie/executor/jpa/TestWorkflowsJobGetJPAExecutor.java...
Hunk #1 succeeded at 430 (offset 92 lines).
Checking patch docs/src/site/twiki/DG_CommandLineTool.twiki...
error: while searching for:
 -auth   select authentication type 
[SIMPLE|KERBEROS]
 -doas   doAs user, impersonates as the specified 
user.
 -filter 
user=\;name=\;group=\;status=\;frequency=\;unit=\;startcreatedtime=\;
  endcreatedtime=\;sortby=
 -jobtypejob type ('Supported in Oozie-2.0 or 
later versions ONLY - coordinator' or 'wf' (default))
 -lennumber of jobs (default '100')
 -localtime   use local time (same as passing your time 
zone to -timezone). Overrides -timezone option

error: patch failed: docs/src/site/twiki/DG_CommandLineTool.twiki:101
error: docs/src/site/twiki/DG_CommandLineTool.twiki: patch does not apply
Checking patch docs/src/site/twiki/WebServicesAPI.twiki...
Hunk #1 succeeded at 1805 (offset 141 lines).
error: while searching for:
Moreover, the =jobtype= parameter could be used to determine what type of job 
is looking for.
The valid values of job type are: =wf=, =coordinator= or =bundle=.

startCreatedTime and endCreatedTime should be specified either in *ISO8601 
(UTC)* format (*-MM-dd'T'HH:mm'Z'*) or a offset value in days or hours from 
the current time. For example, -2d means the current time - 2 days. -3h means 
the current time - 3 hours. -5m means the current time - 5 minutes

--- Bulk modify jobs


error: patch failed: docs/src/site/twiki/WebServicesAPI.twiki:1675
error: docs/src/site/twiki/WebServicesAPI.twiki: patch does not apply
Checking patch src/main/java/org/apache/oozie/cli/OozieCLI.java...
error: src/main/java/org/apache/oozie/cli/OozieCLI.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/client/OozieClient.java...
error: src/main/java/org/apache/oozie/client/OozieClient.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/BundleJobBean.java...
error: src/main/java/org/apache/oozie/BundleJobBean.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/CoordinatorEngine.java...
error: src/main/java/org/apache/oozie/CoordinatorEngine.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/CoordinatorJobBean.java...
error: src/main/java/org/apache/oozie/CoordinatorJobBean.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/DagEngine.java...
error: src/main/java/org/apache/oozie/DagEngine.java: No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/BundleJobInfoGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/BundleJobInfoGetJPAExecutor.java: 
No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/BundleJobQueryExecutor.java...
error: src/main/java/org/apache/oozie/executor/jpa/BundleJobQueryExecutor.java: 
No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/CoordJobInfoGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/CoordJobInfoGetJPAExecutor.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/WorkflowsJobGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/WorkflowsJobGetJPAExecutor.java: No 
such file or directory
Checking patch src/main/java/org/apache/oozie/store/StoreStatusFilter.java...
error: src/main/java/org/apache/oozie/store/StoreStatusFilter.java: No such 
file or directory
Checking patch src/main/java/org/apache/oozie/util/JobsFilterUtils.java...
error: src/main/java/org/apache/oozie/util/JobsFilterUtils.java: No such file 
or directory
Checking patch src/test/java/org/apache/oozie/client/TestOozieCLI.java...
error: 

[jira] [Commented] (OOZIE-2461) Workflow, Coordinator and Bundle job querying should have last modified filter

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2461:
--

PreCommit-OOZIE-Build started


> Workflow, Coordinator and Bundle job querying should have last modified filter
> --
>
> Key: OOZIE-2461
> URL: https://issues.apache.org/jira/browse/OOZIE-2461
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2461-1.patch, OOZIE-2461-10.patch, 
> OOZIE-2461-11.patch, OOZIE-2461-6.patch, OOZIE-2461-7.patch, 
> OOZIE-2461-8.patch, OOZIE-2461-9.patch
>
>
> To get currently running coordinator and id, one user had to do
> http://localhost:11000/oozie/v1/jobs?jobtype=coord=user%3satish_1.0%3B=1=3000
> They could not use name in the filter as they include a version and keep 
> changing. For eg:
> urs_satish_filter-0.1-daily-coord
> urs_puru_service-0.4-hourly-coord
> It would be good to have last modified filter to get recently active 
> coordinators.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1579:
--


Testing JIRA OOZIE-1579

Cleaning local git workspace



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




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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1579 PreCommit Build #432

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1579
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/432/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 761.34 KB...]
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  1.636 s]
[INFO] Apache Oozie Client  SUCCESS [ 16.238 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 11.443 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  5.721 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  5.021 s]
[INFO] Apache Oozie Core .. SUCCESS [01:15 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.153 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.191 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  7.714 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  8.355 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.587 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.398 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [  9.706 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.022 s]
[INFO] Apache Oozie Docs .. SUCCESS [  2.964 s]
[INFO] Apache Oozie WebApp  SUCCESS [  7.956 s]
[INFO] Apache Oozie Tools . SUCCESS [ 12.050 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.780 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.083 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.106 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.203 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:31 min
[INFO] Finished at: 2018-03-13T00:27:51Z
[INFO] Final Memory: 170M/1940M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch client/src/main/java/org/apache/oozie/cli/OozieCLI.java...
error: while searching for:
public static final String RERUN_NOCLEANUP_OPTION = "nocleanup";

public static final String AUTH_OPTION = "auth";

public static final String VERBOSE_OPTION = "verbose";
public static final String VERBOSE_DELIMITER = "\t";

error: patch failed: client/src/main/java/org/apache/oozie/cli/OozieCLI.java:130
error: client/src/main/java/org/apache/oozie/cli/OozieCLI.java: patch does not 
apply
Checking patch 
client/src/main/java/org/apache/oozie/client/AuthOozieClient.java...
error: while searching for:
import java.net.URL;
import java.util.HashMap;
import java.util.Map;

import org.apache.hadoop.security.authentication.client.AuthenticatedURL;
import org.apache.hadoop.security.authentication.client.AuthenticationException;

error: patch failed: 
client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:27
error: client/src/main/java/org/apache/oozie/client/AuthOozieClient.java: patch 
does not apply
Checking patch core/src/main/conf/oozie-site.xml...
error: while searching for:
simple

Defines authentication used for Oozie HTTP endpoint.
Supported values are: simple | kerberos | 
#AUTHENTICATION_HANDLER_CLASSNAME#




error: patch failed: core/src/main/conf/oozie-site.xml:266
error: core/src/main/conf/oozie-site.xml: patch does not apply
Checking patch src/main/java/org/apache/oozie/cli/OozieCLI.java...
error: src/main/java/org/apache/oozie/cli/OozieCLI.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/client/AuthOozieClient.java...
error: src/main/java/org/apache/oozie/client/AuthOozieClient.java: No such file 
or directory
Checking patch src/main/conf/oozie-site.xml...
error: src/main/conf/oozie-site.xml: No such file or directory
Patch failed to apply to head of branch

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0   

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1579:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2573 PreCommit Build #431

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2573
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/431/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 965.01 KB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2257 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-2573

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
-1 COMPILE
+1 HEAD compiles
-1 patch does not compile
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS - patch does not compile, cannot run testcases
-1 DISTRO
-1 distro tarball fails with the patch


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/431/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/12979311/comment/16396289","id":"16396289","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 

[jira] [Commented] (OOZIE-2573) dataset url which contains spaces can not be handled rightly

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2573:
--


Testing JIRA OOZIE-2573

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 100 Javadoc warning(s)
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {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 [sharelib/streaming].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails 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/PreCommit-OOZIE-Build/431/



> dataset url  which contains spaces can not be handled rightly
> -
>
> Key: OOZIE-2573
> URL: https://issues.apache.org/jira/browse/OOZIE-2573
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: WangMeng
>Assignee: WangMeng
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2573.01.patch, OOZIE-2573.02.patch
>
>
> Currently , Oozie does not escape special character-spaces , this will lead 
> to dataset url  which contains spaces can not be handled rightly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2573) dataset url which contains spaces can not be handled rightly

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2573:
--

PreCommit-OOZIE-Build started


> dataset url  which contains spaces can not be handled rightly
> -
>
> Key: OOZIE-2573
> URL: https://issues.apache.org/jira/browse/OOZIE-2573
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: WangMeng
>Assignee: WangMeng
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2573.01.patch, OOZIE-2573.02.patch
>
>
> Currently , Oozie does not escape special character-spaces , this will lead 
> to dataset url  which contains spaces can not be handled rightly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1636 PreCommit Build #430

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1636
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/430/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 759.45 KB...]
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/main/resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
oozie-zookeeper-security-tests ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target/test-classes
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Some input files use or override a deprecated API.
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  1.829 s]
[INFO] Apache Oozie Client  SUCCESS [ 16.557 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 11.793 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  5.741 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  4.701 s]
[INFO] Apache Oozie Core .. SUCCESS [01:14 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  6.582 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.079 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  7.148 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  8.316 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.320 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.014 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [  9.232 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.018 s]
[INFO] Apache Oozie Docs .. SUCCESS [  2.696 s]
[INFO] Apache Oozie WebApp  SUCCESS [  7.946 s]
[INFO] Apache Oozie Tools . SUCCESS [ 11.589 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.504 s]
[INFO] Apache Oozie Server  SUCCESS [  9.712 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.125 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.258 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:26 min
[INFO] Finished at: 2018-03-13T00:07:10Z
[INFO] Final Memory: 171M/1966M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java...
error: while searching for:
}

private final static String CREATE_OOZIE_SYS =
"create table OOZIE_SYS (name varchar(100), data varchar(100))";

private final static 

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1636:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Success: OOZIE-2949 PreCommit Build #429

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2949
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/429/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/streaming].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2252 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-2949

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [examples].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2093
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestJMSAccessorService#testConnectionRetryExceptionListener
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/429/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13080339/comment/16396268","id":"16396268","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 

[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2949:
--


Testing JIRA OOZIE-2949

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 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 100 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{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 [tools].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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 [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/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {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/spark].
. {color:green}+1{color} There are no new bugs found in [examples].
{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: 2093
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
TestJMSAccessorService#testConnectionRetryExceptionListener
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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/PreCommit-OOZIE-Build/429/



> Escape quotes whitespaces in Sqoop  field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2949-0.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or 
> multiple arg elements.
> When using the command element, Oozie will split the command on every space 
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an 
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell 
> into the workflow.xml.
> We should split the  field by taking quotes into account, similar to 
> what OOZIE-2391
> did for the Spark action's  field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2473) Connection pool for SMTP connection

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2473:
--


Testing JIRA OOZIE-2473

Cleaning local git workspace



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




> Connection pool for SMTP connection
> ---
>
> Key: OOZIE-2473
> URL: https://issues.apache.org/jira/browse/OOZIE-2473
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2473-1.patch, OOZIE-2473-1.patch, 
> OOZIE-2473-2.patch
>
>
> Currently, to send an email we setup new connection every time which seems 
> costly. It would be good to have a connection pool.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2949:
--

PreCommit-OOZIE-Build started


> Escape quotes whitespaces in Sqoop  field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2949-0.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or 
> multiple arg elements.
> When using the command element, Oozie will split the command on every space 
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an 
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell 
> into the workflow.xml.
> We should split the  field by taking quotes into account, similar to 
> what OOZIE-2391
> did for the Spark action's  field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2473 PreCommit Build #428

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2473
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/428/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 762.22 KB...]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.746 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  7.850 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  9.081 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.637 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.256 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 10.632 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.051 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.105 s]
[INFO] Apache Oozie WebApp  SUCCESS [  8.212 s]
[INFO] Apache Oozie Tools . SUCCESS [ 12.957 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.596 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.411 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.049 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.105 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:39 min
[INFO] Finished at: 2018-03-12T22:30:47Z
[INFO] Final Memory: 170M/1958M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch a/core/pom.xml => b/core/pom.xml...
error: a/core/pom.xml: No such file or directory
Checking patch a/core/src/main/java/org/apache/oozie/ErrorCode.java => 
b/core/src/main/java/org/apache/oozie/ErrorCode.java...
error: a/core/src/main/java/org/apache/oozie/ErrorCode.java: No such file or 
directory
Checking patch 
a/core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java => 
b/core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java...
error: 
a/core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java: No 
such file or directory
Checking patch 
b/core/src/main/java/org/apache/oozie/pool/smtp/ConnectionBuilder.java...
Checking patch 
b/core/src/main/java/org/apache/oozie/pool/smtp/ConnectionBuilderFactory.java...
Checking patch 
b/core/src/main/java/org/apache/oozie/pool/smtp/SMTPConnection.java...
Checking patch 
b/core/src/main/java/org/apache/oozie/pool/smtp/SMTPConnectionFactory.java...
Checking patch 
b/core/src/main/java/org/apache/oozie/pool/smtp/TransportBuilder.java...
Checking patch 
b/core/src/main/java/org/apache/oozie/pool/smtp/TransportBuilderFactory.java...
Checking patch b/core/src/main/java/org/apache/oozie/service/PoolService.java...
Checking patch 
a/core/src/main/java/org/apache/oozie/sla/listener/SLAEmailEventListener.java 
=> 
b/core/src/main/java/org/apache/oozie/sla/listener/SLAEmailEventListener.java...
error: 
a/core/src/main/java/org/apache/oozie/sla/listener/SLAEmailEventListener.java: 
No such file or directory
Checking patch a/core/src/main/resources/oozie-default.xml => 
b/core/src/main/resources/oozie-default.xml...
error: a/core/src/main/resources/oozie-default.xml: No such file or directory
Checking patch 
a/core/src/test/java/org/apache/oozie/sla/TestSLAEmailEventListener.java => 
b/core/src/test/java/org/apache/oozie/sla/TestSLAEmailEventListener.java...
error: 
a/core/src/test/java/org/apache/oozie/sla/TestSLAEmailEventListener.java: No 
such file or directory
Checking patch 
b/core/src/test/java/org/apache/oozie/sla/TestSMTPConnectionPool.java...
Checking patch a/pom.xml => b/pom.xml...
error: a/pom.xml: No such file or directory
Checking patch core/pom.xml...
Hunk #1 succeeded at 345 (offset 89 lines).
Checking patch core/src/main/java/org/apache/oozie/ErrorCode.java...
Checking patch 
core/src/main/java/org/apache/oozie/action/email/EmailActionExecutor.java...
Checking patch 
core/src/main/java/org/apache/oozie/pool/smtp/ConnectionBuilder.java...
Checking patch 
core/src/main/java/org/apache/oozie/pool/smtp/ConnectionBuilderFactory.java...
Checking patch 
core/src/main/java/org/apache/oozie/pool/smtp/SMTPConnection.java...
Checking patch 
core/src/main/java/org/apache/oozie/pool/smtp/SMTPConnectionFactory.java...
Checking patch 
core/src/main/java/org/apache/oozie/pool/smtp/TransportBuilder.java...
Checking patch 
core/src/main/java/org/apache/oozie/pool/smtp/TransportBuilderFactory.java...
Checking patch 

[jira] [Commented] (OOZIE-2473) Connection pool for SMTP connection

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2473:
--

PreCommit-OOZIE-Build started


> Connection pool for SMTP connection
> ---
>
> Key: OOZIE-2473
> URL: https://issues.apache.org/jira/browse/OOZIE-2473
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-2473-1.patch, OOZIE-2473-1.patch, 
> OOZIE-2473-2.patch
>
>
> Currently, to send an email we setup new connection every time which seems 
> costly. It would be good to have a connection pool.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1369 PreCommit Build #427

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1369
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/427/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 760.50 KB...]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target/test-classes
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Some input files use or override a deprecated API.
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  1.950 s]
[INFO] Apache Oozie Client  SUCCESS [ 17.325 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 12.245 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  6.057 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  4.956 s]
[INFO] Apache Oozie Core .. SUCCESS [01:15 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.045 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.483 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  8.136 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  8.533 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.651 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.194 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 10.058 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.025 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.054 s]
[INFO] Apache Oozie WebApp  SUCCESS [  8.342 s]
[INFO] Apache Oozie Tools . SUCCESS [ 11.959 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.910 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.066 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.410 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.994 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:36 min
[INFO] Finished at: 2018-03-12T22:25:08Z
[INFO] Final Memory: 169M/1692M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java...
error: while searching for:
args.add("-sqlFile");
args.add(sqlFile);
}
args.add("org.apache.oozie.client.rest.JsonWorkflowJob");
args.add("org.apache.oozie.WorkflowJobBean");
args.add("org.apache.oozie.client.rest.JsonWorkflowAction");
args.add("org.apache.oozie.WorkflowActionBean");
args.add("org.apache.oozie.client.rest.JsonCoordinatorJob");
args.add("org.apache.oozie.CoordinatorJobBean");
args.add("org.apache.oozie.client.rest.JsonCoordinatorAction");
args.add("org.apache.oozie.CoordinatorActionBean");
args.add("org.apache.oozie.client.rest.JsonSLAEvent");
args.add("org.apache.oozie.SLAEventBean");
args.add("org.apache.oozie.client.rest.sla.JsonSLARegistrationEvent");
args.add("org.apache.oozie.sla.SLARegistrationBean");
args.add("org.apache.oozie.client.rest.JsonBundleJob");
args.add("org.apache.oozie.BundleJobBean");
args.add("org.apache.oozie.BundleActionBean");
args.add("org.apache.oozie.sla.SLACalculatorBean");
args.add("org.apache.oozie.sla.SLASummaryBean");

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1369:
--


Testing JIRA OOZIE-1369

Cleaning local git workspace



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




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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1232:
--


Testing JIRA OOZIE-1232

Cleaning local git workspace



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




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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1369:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1232 PreCommit Build #426

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1232
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/426/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 760.58 KB...]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target/test-classes
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Some input files use or override a deprecated API.
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  2.874 s]
[INFO] Apache Oozie Client  SUCCESS [ 18.786 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 12.192 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  6.663 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  5.189 s]
[INFO] Apache Oozie Core .. SUCCESS [01:18 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.386 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.901 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  7.842 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  8.521 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.750 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.772 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 10.482 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.023 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.179 s]
[INFO] Apache Oozie WebApp  SUCCESS [  9.291 s]
[INFO] Apache Oozie Tools . SUCCESS [ 13.832 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.862 s]
[INFO] Apache Oozie Server  SUCCESS [ 11.132 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.186 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.375 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 03:47 min
[INFO] Finished at: 2018-03-12T22:19:42Z
[INFO] Final Memory: 170M/1881M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch 
core/src/test/java/org/apache/oozie/service/TestGroupsService.java...
Hunk #1 succeeded at 20 (offset 1 line).
Hunk #2 succeeded at 108 (offset 1 line).
Checking patch 
core/src/test/java/org/apache/oozie/util/TestHadoopConfLoader.java...
Checking patch core/src/test/resources/test-hadoop-config.xml...
Checking patch core/src/main/java/org/apache/oozie/service/GroupsService.java...
Hunk #1 succeeded at 19 (offset 1 line).
Hunk #2 succeeded at 35 (offset 1 line).
Hunk #3 succeeded at 56 (offset 1 line).
Checking patch 
core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java...
error: while searching for:
import org.apache.hadoop.security.token.Token;
import org.apache.oozie.ErrorCode;
import org.apache.oozie.action.hadoop.JavaActionExecutor;
import org.apache.oozie.util.ParamChecker;
import org.apache.oozie.util.XConfiguration;
import org.apache.oozie.util.XLog;

error: patch failed: 
core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java:31
error: core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java: 
patch does not apply
Checking patch core/src/main/java/org/apache/oozie/util/HadoopConfLoader.java...
Checking patch src/test/java/org/apache/oozie/service/TestGroupsService.java...
error: 

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1676:
--


Testing JIRA OOZIE-1676

Cleaning local git workspace



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




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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1232:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1676 PreCommit Build #425

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1676
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/425/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 770.62 KB...]
assertEquals(url, data.get("OOZIE_URL"));
assertEquals("java.util.HashMap", data.get("@class"));

error: patch failed: 
core/src/test/java/org/apache/oozie/util/TestZKUtils.java:76
error: core/src/test/java/org/apache/oozie/util/TestZKUtils.java: patch does 
not apply
Checking patch 
core/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java...
error: core/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java: 
No such file or directory
Checking patch distro/src/main/tomcat/ssl-web.xml...
error: distro/src/main/tomcat/ssl-web.xml: No such file or directory
Checking patch docs/src/site/twiki/WebServicesAPI.twiki...
Checking patch webapp/src/main/webapp/WEB-INF/web.xml...
Hunk #2 succeeded at 165 (offset 14 lines).
Hunk #3 succeeded at 190 (offset 14 lines).
Hunk #4 succeeded at 210 (offset 14 lines).
error: while searching for:
/v2/sla/*




index.jsp

error: patch failed: webapp/src/main/webapp/WEB-INF/web.xml:188
error: webapp/src/main/webapp/WEB-INF/web.xml: patch does not apply
Checking patch webapp/src/main/webapp/oozie-console.js...
Hunk #2 succeeded at 2386 (offset 553 lines).
error: while searching for:
var responseObj = eval('(' + responseTxt + ')');
var j = 0;
for (var i in responseObj) {
fo.elements[j] = {};
fo.elements[j].name = i;
fo.elements[j].value = responseObj[i];
j ++;
}
return fo;
}

error: patch failed: webapp/src/main/webapp/oozie-console.js:1843
error: webapp/src/main/webapp/oozie-console.js: patch does not apply
Checking patch src/main/java/org/apache/oozie/client/OozieClient.java...
error: src/main/java/org/apache/oozie/client/OozieClient.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/servlet/BaseAdminServlet.java...
error: src/main/java/org/apache/oozie/servlet/BaseAdminServlet.java: No such 
file or directory
Checking patch src/main/java/org/apache/oozie/servlet/V0AdminServlet.java...
error: src/main/java/org/apache/oozie/servlet/V0AdminServlet.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/servlet/V1AdminServlet.java...
error: src/main/java/org/apache/oozie/servlet/V1AdminServlet.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/servlet/V2AdminServlet.java...
error: src/main/java/org/apache/oozie/servlet/V2AdminServlet.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/servlet/V3AdminServlet.java...
Checking patch src/main/java/org/apache/oozie/servlet/VersionServlet.java...
error: src/main/java/org/apache/oozie/servlet/VersionServlet.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/util/Instrumentation.java...
error: src/main/java/org/apache/oozie/util/Instrumentation.java: No such file 
or directory
Checking patch 
src/main/java/org/apache/oozie/util/MetricsInstrumentation.java...
error: src/main/java/org/apache/oozie/util/MetricsInstrumentation.java: No such 
file or directory
Checking patch src/test/java/org/apache/oozie/client/TestWorkflowClient.java...
error: src/test/java/org/apache/oozie/client/TestWorkflowClient.java: No such 
file or directory
Checking patch 
src/test/java/org/apache/oozie/service/TestZKJobsConcurrencyService.java...
error: 
src/test/java/org/apache/oozie/service/TestZKJobsConcurrencyService.java: No 
such file or directory
Checking patch 
src/test/java/org/apache/oozie/servlet/DummyV3AdminServlet.java...
Checking patch 
src/test/java/org/apache/oozie/servlet/TestHAV3AdminServlet.java...
Checking patch src/test/java/org/apache/oozie/servlet/TestV3AdminServlet.java...
Checking patch src/test/java/org/apache/oozie/servlet/TestVersionServlet.java...
error: src/test/java/org/apache/oozie/servlet/TestVersionServlet.java: No such 
file or directory
Checking patch src/test/java/org/apache/oozie/test/XTestCase.java...
error: src/test/java/org/apache/oozie/test/XTestCase.java: No such file or 
directory
Checking patch src/test/java/org/apache/oozie/test/ZKXTestCase.java...
error: src/test/java/org/apache/oozie/test/ZKXTestCase.java: No such file or 
directory
Checking patch src/test/java/org/apache/oozie/util/TestZKUtils.java...
error: src/test/java/org/apache/oozie/util/TestZKUtils.java: No such file or 
directory
Checking patch 
src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java...
error: src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java: No 
such file or directory
Checking patch src/main/tomcat/ssl-web.xml...
error: src/main/tomcat/ssl-web.xml: No such file or directory
Checking patch src/site/twiki/WebServicesAPI.twiki...
error: 

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1676:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2427:
--


Testing JIRA OOZIE-2427

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 100 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{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [core].
. {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/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/spark].
. {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/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/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
{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: 2092
.Tests failed: 17
.Tests errors: 12

.The patch failed the following testcases:

testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)
testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)

.Tests failing with errors:
testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectors(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLADurationMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectionContext)

Failed: OOZIE-2427 PreCommit Build #424

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2427
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/424/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.73 MB...]
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2092
Tests failed: 17
Tests errors: 12

The patch failed the following testcases:

testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)
testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)

Tests failing with errors:
testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectors(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLADurationMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectionContext)
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestHAPartitionDependencyManagerService#testCheckAfterActionDelete
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/424/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  55520 0  100  5552  0   7186 --:--:-- --:--:-- --:--:--  

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2427:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2518) Oozie is creating many files and directories in /tmp per day

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2518:
--


Testing JIRA OOZIE-2518

Cleaning local git workspace



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




> Oozie is creating many files and directories in /tmp per day
> 
>
> Key: OOZIE-2518
> URL: https://issues.apache.org/jira/browse/OOZIE-2518
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.2.0
>Reporter: Sergey Svynarchuk
>Assignee: Sergey Svynarchuk
>Priority: Major
>  Labels: patch
> Fix For: trunk
>
> Attachments: OOZIE-2518.patch
>
>
> Oozie generate many tmp files, I have over 2000 files in /tmp from oozie, 
> that have been created over the last 7 days: 
> {code}
> drwxr-xr-x 3 root root   22 Apr 22 14:19 /tmp/oozie-war-packing-24575
> drwxr-xr-x 3 root root   22 Apr 22 14:15 /tmp/oozie-war-packing-12211
> drwxr-xr-x 3 root root   22 Apr 22 14:10 /tmp/oozie-war-packing-32238
> drwxr-xr-x 2 test test6 Apr 22 13:54 
> /tmp/oozie-test8457897583638353023.dir
> -rw-r--r-- 1 test test0 Apr 22 13:54 /tmp/ooziedb-2680155694357966339.sql
> drwxr-xr-x 2 test test6 Apr 22 13:53 /tmp/oozie-test142692242798969000.dir
> -rw-r--r-- 1 test test0 Apr 22 13:53 /tmp/ooziedb-9104680045020610294.sql
> drwxr-xr-x 2 test test6 Apr 22 13:53 
> /tmp/oozie-test5885601734493698256.dir
> -rw-r--r-- 1 test test0 Apr 22 13:53 /tmp/ooziedb-4675739133078261538.sql
> drwxr-xr-x 2 test test6 Apr 22 13:53 
> /tmp/oozie-test5565479595579419225.dir
> [root@test-node ext-conf]# ls -ldt /tmp/ooz* | tail
> drwxr-xr-x 3 root root   22 Apr 13 08:17 /tmp/oozie-war-packing-22705
> drwxr-xr-x 3 root root   22 Apr 13 08:16 /tmp/oozie-war-packing-18292
> drwxr-xr-x 3 root root   22 Apr 13 08:09 /tmp/oozie-war-packing-20289
> drwxr-xr-x 3 root root   22 Apr 13 08:09 /tmp/oozie-war-packing-18417
> drwxr-xr-x 3 root root   22 Apr 13 08:08 /tmp/oozie-war-packing-14712
> drwxr-xr-x 3 root root   22 Apr 13 08:05 /tmp/oozie-war-packing-25206
> drwxr-xr-x 3 root root   22 Apr 13 07:53 /tmp/oozie-war-packing-968
> drwxr-xr-x 3 root root   22 Apr 13 07:52 /tmp/oozie-war-packing-27771
> drwxr-xr-x 3 root root   22 Apr 13 07:45 /tmp/oozie-war-packing-30342
> drwxr-xr-x 3 root root   22 Apr 13 07:45 /tmp/oozie-war-packing-29086
> {code}
> This files can be moved into oozie tmp dir (something like this 
> /tmp/oozieTmp) and also we could cleanup old files



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-2518 PreCommit Build #423

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2518
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/423/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 996.28 KB...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [ 15.384 s]
[INFO] Apache Oozie Client  SUCCESS [ 28.706 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 20.859 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [ 10.259 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  7.775 s]
[INFO] Apache Oozie Core .. SUCCESS [01:51 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [ 10.336 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [ 12.454 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [ 11.377 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 11.523 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  7.829 s]
[INFO] Apache Oozie Examples .. SUCCESS [ 11.762 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 14.709 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.024 s]
[INFO] Apache Oozie Docs .. SUCCESS [  4.814 s]
[INFO] Apache Oozie WebApp  SUCCESS [ 12.353 s]
[INFO] Apache Oozie Tools . SUCCESS [ 19.890 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  2.347 s]
[INFO] Apache Oozie Server  SUCCESS [ 14.975 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.733 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.696 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 05:37 min
[INFO] Finished at: 2018-03-12T20:17:35Z
[INFO] Final Memory: 173M/1201M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch core/src/main/java/org/apache/oozie/service/Services.java...
Checking patch distro/src/main/bin/addtowar.sh...
Checking patch distro/src/main/bin/oozie-setup.sh...
Hunk #1 succeeded at 50 (offset 3 lines).
Checking patch distro/src/main/bin/oozied.sh...
error: while searching for:
  exit -1
fi
  fi
  echo
}


error: patch failed: distro/src/main/bin/oozied.sh:86
error: distro/src/main/bin/oozied.sh: patch does not apply
Checking patch tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java...
error: while searching for:
throw new Exception("'-sqlfile ' or '-run' options 
must be specified");
}
CommandLine commandLine = command.getCommandLine();
String sqlFile = (commandLine.hasOption(SQL_FILE_OPT))
 ? commandLine.getOptionValue(SQL_FILE_OPT)
 : File.createTempFile("ooziedb-", 
".sql").getAbsolutePath();
boolean run = commandLine.hasOption(RUN_OPT);
if (command.getName().equals(CREATE_CMD)) {
createDB(sqlFile, run);

error: patch failed: 
tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java:119
error: tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java: patch does 
not apply
Checking patch 
tools/src/main/java/org/apache/oozie/tools/OozieSharelibCLI.java...
Checking patch src/main/java/org/apache/oozie/service/Services.java...
error: src/main/java/org/apache/oozie/service/Services.java: No such file or 
directory
Checking patch src/main/bin/addtowar.sh...
error: src/main/bin/addtowar.sh: No such file or directory
Checking patch src/main/bin/oozie-setup.sh...
error: src/main/bin/oozie-setup.sh: No such file or directory
Checking patch src/main/bin/oozied.sh...
error: src/main/bin/oozied.sh: No such file or directory
Checking patch src/main/java/org/apache/oozie/tools/OozieDBCLI.java...
error: src/main/java/org/apache/oozie/tools/OozieDBCLI.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/tools/OozieSharelibCLI.java...
error: src/main/java/org/apache/oozie/tools/OozieSharelibCLI.java: No such file 
or directory
Patch failed to apply to head of branch

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1860:
--


Testing JIRA OOZIE-1860

Cleaning local git workspace



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




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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1860 PreCommit Build #422

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1860
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/422/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 760.01 KB...]
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
oozie-zookeeper-security-tests ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target/test-classes
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Some input files use or override a deprecated API.
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  2.106 s]
[INFO] Apache Oozie Client  SUCCESS [ 19.063 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 13.097 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  7.485 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  5.022 s]
[INFO] Apache Oozie Core .. SUCCESS [01:24 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  8.333 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.722 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  8.186 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  9.125 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  6.341 s]
[INFO] Apache Oozie Examples .. SUCCESS [  9.110 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 11.520 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.021 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.125 s]
[INFO] Apache Oozie WebApp  SUCCESS [  8.801 s]
[INFO] Apache Oozie Tools . SUCCESS [ 16.699 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.811 s]
[INFO] Apache Oozie Server  SUCCESS [ 11.971 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.485 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.893 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 04:02 min
[INFO] Finished at: 2018-03-12T20:08:41Z
[INFO] Final Memory: 171M/1967M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch sharelib/oozie/pom.xml...
error: while searching for:
test


org.apache.oozie
oozie-hadoop-utils
compile

error: patch failed: sharelib/oozie/pom.xml:59
error: sharelib/oozie/pom.xml: patch does not apply
Checking patch 
sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java...
error: 
sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java:
 No such file or directory
Checking patch 
sharelib/oozie/src/test/java/org/apache/oozie/action/hadoop/LauncherMapperTest.java...
Checking 

[jira] [Resolved] (OOZIE-3055) Release Oozie 5.0.0

[Andras Piros (JIRA)]

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

Andras Piros resolved OOZIE-3055.
-
Resolution: Won't Fix

> Release Oozie 5.0.0
> ---
>
> Key: OOZIE-3055
> URL: https://issues.apache.org/jira/browse/OOZIE-3055
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
>
> It's been a while where we had a decent {{4.3.0}} release. Let's roll for 
> {{5.0.0}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1860:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2814:
---

[~gezapeti], [~andras.piros] can you review the latest patch? Thanks.

> OYA: Update example workflows to newest schemas
> ---
>
> Key: OOZIE-2814
> URL: https://issues.apache.org/jira/browse/OOZIE-2814
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
>Priority: Blocker
> Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, 
> OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, 
> OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch
>
>
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric.  Most, if not all, examples currently use pretty old versions 
> of the schemas.  We should take this opportunity to update the examples to 
> the newest schemas added by OOZIE-2687, which should help demonstrate them.
> It may make sense to keep the older schemas too, to show that older workflows 
> still work.  We have some examples where we have two workflow XML files that 
> do the same thing in different ways.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1779:
--


Testing JIRA OOZIE-1779

Cleaning local git workspace



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




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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-1779 PreCommit Build #421

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-1779
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/421/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 778.39 KB...]
// query
if (!isEnabled && !isUnit) {
sb.append(seletStr).append(" where 
w.timeUnitStr IN (:timeUnitStr" + index);
isUnit = true;
isEnabled = true;
} else {
// Unit filter is neither the first nor the 
last condition to be added to the where
// clause of query
if (isEnabled && !isUnit) {
sb.append(" and w.timeUnitStr IN 
(:timeUnitStr" + index);
isUnit = true;
} else {
if (isUnit) {
sb.append(", :timeUnitStr" + index);
}
}
}
// This unit filter value is the last condition 
to be added to the where clause of query
if (i == values.size() - 1) {
sb.append(")");
}
++index;
valArray.add(values.get(i));
orArray.add(colName);
colArray.add(colVar);
}
}
}
}
}
}
}
}

error: patch failed: 
core/src/main/java/org/apache/oozie/store/StoreStatusFilter.java:17
error: core/src/main/java/org/apache/oozie/store/StoreStatusFilter.java: patch 
does not apply
Checking patch core/src/main/java/org/apache/oozie/store/WorkflowStore.java...
Hunk #1 succeeded at 475 (offset -1 lines).
Checking patch 
core/src/test/java/org/apache/oozie/TestCoordinatorEngineSimple.java...
error: while searching for:
import java.util.List;
import java.util.Map;

import org.apache.oozie.service.Services;
import org.apache.oozie.test.XTestCase;
import org.junit.Test;

error: patch failed: 
core/src/test/java/org/apache/oozie/TestCoordinatorEngineSimple.java:20
error: core/src/test/java/org/apache/oozie/TestCoordinatorEngineSimple.java: 
patch does not apply
Checking patch core/src/test/java/org/apache/oozie/TestDagEngine.java...
Hunk #1 succeeded at 42 (offset 1 line).
Hunk #2 succeeded at 236 (offset 1 line).
Checking patch 
core/src/test/java/org/apache/oozie/store/TestDBWorkflowStore.java...
Hunk #1 succeeded at 397 (offset 1 line).
Checking patch 
core/src/test/java/org/apache/oozie/store/TestStoreStatusFilter.java...
Checking patch src/main/java/org/apache/oozie/client/OozieClient.java...
error: src/main/java/org/apache/oozie/client/OozieClient.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/BundleEngine.java...
error: src/main/java/org/apache/oozie/BundleEngine.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/CoordinatorEngine.java...
error: src/main/java/org/apache/oozie/CoordinatorEngine.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/DagEngine.java...
error: src/main/java/org/apache/oozie/DagEngine.java: No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/BundleJobInfoGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/BundleJobInfoGetJPAExecutor.java: 
No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/CoordJobInfoGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/CoordJobInfoGetJPAExecutor.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/WorkflowsJobGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/WorkflowsJobGetJPAExecutor.java: No 
such file or directory
Checking patch src/main/java/org/apache/oozie/store/CoordinatorStore.java...
error: src/main/java/org/apache/oozie/store/CoordinatorStore.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/store/StoreStatusFilter.java...
error: src/main/java/org/apache/oozie/store/StoreStatusFilter.java: No such 
file or directory
Checking patch src/main/java/org/apache/oozie/store/WorkflowStore.java...
error: src/main/java/org/apache/oozie/store/WorkflowStore.java: No such file or 
directory
Checking patch 
src/test/java/org/apache/oozie/TestCoordinatorEngineSimple.java...
error: 

[jira] [Updated] (OOZIE-2975) code clean up in pig sharelib, replace Exception with more explicit, add try with resources, StringBuilder instead of StringBuffer

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2975:

Fix Version/s: (was: 5.0.0)
   5.1.0

> code clean up in pig sharelib, replace Exception with more explicit, add try 
> with resources, StringBuilder instead of StringBuffer
> --
>
> Key: OOZIE-2975
> URL: https://issues.apache.org/jira/browse/OOZIE-2975
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: 5.1.0
>
> Attachments: OOZIE-2975-0.patch
>
>
> 1. Replaced StringBuffer with StringBuilder
> 2. Replaced Exception with IOException and ExecException
> 3. Replaced old Hashmap notation with diamond notation
> 4. Added try-with-resources notation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3061) Kill only those child jobs which are not already killed

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3061:

Fix Version/s: (was: 5.0.0)
   5.1.0

> Kill only those child jobs which are not already killed
> ---
>
> Key: OOZIE-3061
> URL: https://issues.apache.org/jira/browse/OOZIE-3061
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Satish Subhashrao Saley
>Assignee: Mate Juhasz
>Priority: Trivial
>  Labels: newbie, newbiee
> Fix For: 5.1.0
>
> Attachments: OOZIE-3061-001.patch, OOZIE-3061-002.patch, 
> OOZIE-3061-003.patch, OOZIE-3061-004.patch
>
>
> Here we kill all child jobs. 
> https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java#L265
> We should check before killing for already killed application.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1779:
--

PreCommit-OOZIE-Build started


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-1779:

Fix Version/s: (was: 5.0.0)
   5.1.0

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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3189) Update the release script and wiki page to use sha512 instead of md5

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-3189:
---

Thanks for the patch!
./bin/create-release-artifact failder for the first time though.
The problem is that if mvn downloads something then the line
{{releaseVersion=$(mvn help:evaluate -Dexpression=project.version | grep -v 
INFO | grep -v WARNING)}} returns "Downloaded from centra: https://..; 
instead of the oozie version.
Can you change that line to {{mvn help:evaluate -Dexpression=project.version | 
grep -v INFO | grep -v WARNING | grep -v Downloading |grep -v Downloaded}} ? It 
seems to fix the issue for now.

> Update the release script and wiki page to use sha512 instead of md5
> 
>
> Key: OOZIE-3189
> URL: https://issues.apache.org/jira/browse/OOZIE-3189
> Project: Oozie
>  Issue Type: Improvement
>  Components: scripts
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-3189.001.patch
>
>
> Apache has updated it's policy on the release signatures, as per it's website 
> [here|https://www.apache.org/dev/release-distribution#sigs-and-sums] and a 
> recent email. Basically, all future releases should be providing a sha512 
> checksum instead of an md5 one.
> There are two tasks:
>  # Update the release script to use sha512 instead of md5
>  [https://github.com/apache/oozie/blob/master/bin/create-release-artifact#L71]
>  [https://www.apache.org/dev/release-signing#sha-checksum]
>  # Update the wiki (requires committer/pmc permissions?)
>  [https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release]
> While we're updating the wiki, we should add details on:
>  # Making sure the gpg key used for signing releases is 4096 bit RSA
>  # Publishing your gpg public key to a key server 
> ([https://www.apache.org/dev/release-signing#keyserver])



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...

[Denes Bodo (JIRA)]

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

Denes Bodo updated OOZIE-3186:
--
Priority: Critical  (was: Major)

> Oozie is unable to use configuration linked using jceks://file/...
> --
>
> Key: OOZIE-3186
> URL: https://issues.apache.org/jira/browse/OOZIE-3186
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1, 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
>  Labels: usability
> Fix For: 5.0.0
>
> Attachments: OOZIE-3186-001.patch, OOZIE-3186-002.patch
>
>
> When Oozie is used with Ambari, the next configuration makes Oozie fail to 
> start:
> {noformat}
> 
>     hadoop.security.credential.provider.path
>     jceks://file/.../oozie-site.jceks
> 
> {noformat}
> Value should have *localjceks://* instead of *jceks://*. But Ambari does not 
> let change this value. I propose change the url when Oozie loads it.
>  
> Stacktrace, when the issue occurs:
> {noformat}
> org.apache.oozie.service.ServiceException: E0103: Could not load service 
> classes, Could not load password for [oozie.service.JPAService.jdbc.password] 
> at org.apache.oozie.service.Services.loadServices(Services.java:309) at 
> org.apache.oozie.service.Services.init(Services.java:213) at 
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
>  at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
>  at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779) 
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
>  at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:780) 
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at 
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:944) at 
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:779) at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:505) at 
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at 
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
>  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1069) at 
> org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at 
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at 
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at 
> org.apache.catalina.core.StandardService.start(StandardService.java:525) at 
> org.apache.catalina.core.StandardServer.start(StandardServer.java:761) at 
> org.apache.catalina.startup.Catalina.start(Catalina.java:595) 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:498) at 
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at 
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by: 
> java.lang.IllegalArgumentException: Could not load password for 
> [oozie.service.JPAService.jdbc.password] at 
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:615)
>  at 
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:602)
>  at org.apache.oozie.service.JPAService.init(JPAService.java:147) at 
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386) at 
> org.apache.oozie.service.Services.setService(Services.java:372) at 
> org.apache.oozie.service.Services.loadServices(Services.java:305) ... 26 more 
> Caused by: java.lang.reflect.InvocationTargetException 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:498) at 
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:608)
>  ... 31 more Caused by: java.lang.UnsupportedOperationException: Accessing 
> local file system is not allowed at 
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
>  at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47) 
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at 
> org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at 
> 

[jira] [Updated] (OOZIE-3186) Oozie is unable to use configuration linked using jceks://file/...

[Denes Bodo (JIRA)]

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

Denes Bodo updated OOZIE-3186:
--
Fix Version/s: 5.0.0

> Oozie is unable to use configuration linked using jceks://file/...
> --
>
> Key: OOZIE-3186
> URL: https://issues.apache.org/jira/browse/OOZIE-3186
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1, 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
>  Labels: usability
> Fix For: 5.0.0
>
> Attachments: OOZIE-3186-001.patch, OOZIE-3186-002.patch
>
>
> When Oozie is used with Ambari, the next configuration makes Oozie fail to 
> start:
> {noformat}
> 
>     hadoop.security.credential.provider.path
>     jceks://file/.../oozie-site.jceks
> 
> {noformat}
> Value should have *localjceks://* instead of *jceks://*. But Ambari does not 
> let change this value. I propose change the url when Oozie loads it.
>  
> Stacktrace, when the issue occurs:
> {noformat}
> org.apache.oozie.service.ServiceException: E0103: Could not load service 
> classes, Could not load password for [oozie.service.JPAService.jdbc.password] 
> at org.apache.oozie.service.Services.loadServices(Services.java:309) at 
> org.apache.oozie.service.Services.init(Services.java:213) at 
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
>  at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
>  at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779) 
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
>  at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:780) 
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at 
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:944) at 
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:779) at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:505) at 
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at 
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
>  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1069) at 
> org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at 
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at 
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at 
> org.apache.catalina.core.StandardService.start(StandardService.java:525) at 
> org.apache.catalina.core.StandardServer.start(StandardServer.java:761) at 
> org.apache.catalina.startup.Catalina.start(Catalina.java:595) 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:498) at 
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at 
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by: 
> java.lang.IllegalArgumentException: Could not load password for 
> [oozie.service.JPAService.jdbc.password] at 
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:615)
>  at 
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:602)
>  at org.apache.oozie.service.JPAService.init(JPAService.java:147) at 
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386) at 
> org.apache.oozie.service.Services.setService(Services.java:372) at 
> org.apache.oozie.service.Services.loadServices(Services.java:305) ... 26 more 
> Caused by: java.lang.reflect.InvocationTargetException 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:498) at 
> org.apache.oozie.service.ConfigurationService.getPassword(ConfigurationService.java:608)
>  ... 31 more Caused by: java.lang.UnsupportedOperationException: Accessing 
> local file system is not allowed at 
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
>  at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47) 
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at 
> org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at 
> 

[jira] [Commented] (OOZIE-3184) Test case in oozie-core fails with a NullPointerException

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3184:
-

Thanks [~alishap] for your work on the issue!

> Test case in oozie-core fails with a NullPointerException
> -
>
> Key: OOZIE-3184
> URL: https://issues.apache.org/jira/browse/OOZIE-3184
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Major
>  Labels: ppc64le
> Attachments: error.txt
>
>
> Maven command used is mvn -Dtest=TestGraphGenerator#testGraphWithManyNodes 
> test
>  Observed that the test case fails at GraphGenerator.java:87 of oozie-core 
> i.e. at the .parse function.
>  Have attached the error.txt file below , that has the errors occurred while 
> running the test case.
> {code:java}
> [INFO] Running org.apache.oozie.util.graph.TestGraphGenerator [ERROR] Tests 
> run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 24.157 s <<< 
> FAILURE! - in org.apache.oozie.util.graph.TestGraphGenerator [ERROR] 
> testGraphWithManyNodes(org.apache.oozie.util.graph.TestGraphGenerator) Time 
> elapsed: 24.157 s <<< ERROR! java.lang.RuntimeException: 
> java.util.concurrent.ExecutionException: java.lang.NullPointerException at 
> org.apache.oozie.util.graph.TestGraphGenerator.testGraphWithManyNodes(TestGraphGenerator.java:158)
>  Caused by: java.util.concurrent.ExecutionException: 
> java.lang.NullPointerException at 
> org.apache.oozie.util.graph.TestGraphGenerator.testGraphWithManyNodes(TestGraphGenerator.java:158)
>  Caused by: java.lang.NullPointerException{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3190) Test cases in TestGraphGenerator.java of oozie-core fail with a NullPointerException

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3190:
-

Thanks for your work [~alishap] on the issue!

> Test cases in TestGraphGenerator.java of oozie-core fail with a 
> NullPointerException
> 
>
> Key: OOZIE-3190
> URL: https://issues.apache.org/jira/browse/OOZIE-3190
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Major
>  Labels: ppc64le
>
> The test cases testSimpleGraphPng and testSimpleGraphSvg under 
> TestGraphGenerator.java fail with java.lang.NullPointerException.
>  Maven command used for testSimpleGraphPng is mvn 
> -Dtest=TestGraphGenerator#testSimpleGraphPng test.
> {code:java}
> [INFO] Running org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 24.229 s <<< FAILURE! - in org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] testSimpleGraphPng(org.apache.oozie.util.graph.TestGraphGenerator) 
> Time elapsed: 24.229 s <<< FAILURE!
> java.lang.AssertionError: Render and write PNG failed for 
> graph-workflow-simple.xml: java.util.concurrent.ExecutionException: 
> java.lang.NullPointerException
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.generateAndAssertPng(TestGraphGenerator.java:96)
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.testSimpleGraphPng(TestGraphGenerator.java:64)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] TestGraphGenerator.testSimpleGraphPng:64->generateAndAssertPng:96 
> Render and write PNG failed for graph-workflow-simple.xml: 
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> {code}
> Maven command used for testSimpleGraphSvg is mvn 
> -Dtest=TestGraphGenerator#testSimpleGraphSvg test.
> {code:java}
> [INFO] Running org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 24.113 s <<< FAILURE! - in org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] testSimpleGraphSvg(org.apache.oozie.util.graph.TestGraphGenerator) 
> Time elapsed: 24.113 s <<< FAILURE!
> java.lang.AssertionError: Render and write SVG failed: 
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.testSimpleGraphSvg(TestGraphGenerator.java:144)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] TestGraphGenerator.testSimpleGraphSvg:144 Render and write SVG 
> failed: java.util.concurrent.ExecutionException: 
> java.lang.NullPointerException
> {code}
> Have observed that the test cases use the values from the enum OutputFormat 
> which contains 3 constants : PNG, DOT & SVG
> The test cases using OutputFormat.DOT have passed whereas the once which have 
> used the other two constants i.e PNG and SVG , fail on ppc64le arch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OOZIE-3184) Test case in oozie-core fails with a NullPointerException

[Alisha Prabhu (JIRA)]

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

Alisha Prabhu resolved OOZIE-3184.
--
Resolution: Resolved

> Test case in oozie-core fails with a NullPointerException
> -
>
> Key: OOZIE-3184
> URL: https://issues.apache.org/jira/browse/OOZIE-3184
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Major
>  Labels: ppc64le
> Attachments: error.txt
>
>
> Maven command used is mvn -Dtest=TestGraphGenerator#testGraphWithManyNodes 
> test
>  Observed that the test case fails at GraphGenerator.java:87 of oozie-core 
> i.e. at the .parse function.
>  Have attached the error.txt file below , that has the errors occurred while 
> running the test case.
> {code:java}
> [INFO] Running org.apache.oozie.util.graph.TestGraphGenerator [ERROR] Tests 
> run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 24.157 s <<< 
> FAILURE! - in org.apache.oozie.util.graph.TestGraphGenerator [ERROR] 
> testGraphWithManyNodes(org.apache.oozie.util.graph.TestGraphGenerator) Time 
> elapsed: 24.157 s <<< ERROR! java.lang.RuntimeException: 
> java.util.concurrent.ExecutionException: java.lang.NullPointerException at 
> org.apache.oozie.util.graph.TestGraphGenerator.testGraphWithManyNodes(TestGraphGenerator.java:158)
>  Caused by: java.util.concurrent.ExecutionException: 
> java.lang.NullPointerException at 
> org.apache.oozie.util.graph.TestGraphGenerator.testGraphWithManyNodes(TestGraphGenerator.java:158)
>  Caused by: java.lang.NullPointerException{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (OOZIE-3190) Test cases in TestGraphGenerator.java of oozie-core fail with a NullPointerException

[Alisha Prabhu (JIRA)]

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

Alisha Prabhu resolved OOZIE-3190.
--
Resolution: Resolved

> Test cases in TestGraphGenerator.java of oozie-core fail with a 
> NullPointerException
> 
>
> Key: OOZIE-3190
> URL: https://issues.apache.org/jira/browse/OOZIE-3190
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Major
>  Labels: ppc64le
>
> The test cases testSimpleGraphPng and testSimpleGraphSvg under 
> TestGraphGenerator.java fail with java.lang.NullPointerException.
>  Maven command used for testSimpleGraphPng is mvn 
> -Dtest=TestGraphGenerator#testSimpleGraphPng test.
> {code:java}
> [INFO] Running org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 24.229 s <<< FAILURE! - in org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] testSimpleGraphPng(org.apache.oozie.util.graph.TestGraphGenerator) 
> Time elapsed: 24.229 s <<< FAILURE!
> java.lang.AssertionError: Render and write PNG failed for 
> graph-workflow-simple.xml: java.util.concurrent.ExecutionException: 
> java.lang.NullPointerException
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.generateAndAssertPng(TestGraphGenerator.java:96)
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.testSimpleGraphPng(TestGraphGenerator.java:64)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] TestGraphGenerator.testSimpleGraphPng:64->generateAndAssertPng:96 
> Render and write PNG failed for graph-workflow-simple.xml: 
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> {code}
> Maven command used for testSimpleGraphSvg is mvn 
> -Dtest=TestGraphGenerator#testSimpleGraphSvg test.
> {code:java}
> [INFO] Running org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 24.113 s <<< FAILURE! - in org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] testSimpleGraphSvg(org.apache.oozie.util.graph.TestGraphGenerator) 
> Time elapsed: 24.113 s <<< FAILURE!
> java.lang.AssertionError: Render and write SVG failed: 
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.testSimpleGraphSvg(TestGraphGenerator.java:144)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] TestGraphGenerator.testSimpleGraphSvg:144 Render and write SVG 
> failed: java.util.concurrent.ExecutionException: 
> java.lang.NullPointerException
> {code}
> Have observed that the test cases use the values from the enum OutputFormat 
> which contains 3 constants : PNG, DOT & SVG
> The test cases using OutputFormat.DOT have passed whereas the once which have 
> used the other two constants i.e PNG and SVG , fail on ppc64le arch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3190) Test cases in TestGraphGenerator.java of oozie-core fail with a NullPointerException

[Alisha Prabhu (JIRA)]

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

Alisha Prabhu commented on OOZIE-3190:
--

Oozie tests under TestGraphGenerator.java have passed on ppc64le after 
performing the following steps :

- cloned J2V8 
       git clone https://github.com/eclipsesource/J2V8
       git checkout tags/v4.5.0
 - libj2v8_linux_ppc64le.so was created after building the project.
 - exported it by using, export LD_LIBRARY_PATH command.
 - ran the the test cases under TestGraphGenerator.java in oozie.

> Test cases in TestGraphGenerator.java of oozie-core fail with a 
> NullPointerException
> 
>
> Key: OOZIE-3190
> URL: https://issues.apache.org/jira/browse/OOZIE-3190
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Major
>  Labels: ppc64le
>
> The test cases testSimpleGraphPng and testSimpleGraphSvg under 
> TestGraphGenerator.java fail with java.lang.NullPointerException.
>  Maven command used for testSimpleGraphPng is mvn 
> -Dtest=TestGraphGenerator#testSimpleGraphPng test.
> {code:java}
> [INFO] Running org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 24.229 s <<< FAILURE! - in org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] testSimpleGraphPng(org.apache.oozie.util.graph.TestGraphGenerator) 
> Time elapsed: 24.229 s <<< FAILURE!
> java.lang.AssertionError: Render and write PNG failed for 
> graph-workflow-simple.xml: java.util.concurrent.ExecutionException: 
> java.lang.NullPointerException
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.generateAndAssertPng(TestGraphGenerator.java:96)
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.testSimpleGraphPng(TestGraphGenerator.java:64)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] TestGraphGenerator.testSimpleGraphPng:64->generateAndAssertPng:96 
> Render and write PNG failed for graph-workflow-simple.xml: 
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> {code}
> Maven command used for testSimpleGraphSvg is mvn 
> -Dtest=TestGraphGenerator#testSimpleGraphSvg test.
> {code:java}
> [INFO] Running org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 24.113 s <<< FAILURE! - in org.apache.oozie.util.graph.TestGraphGenerator
> [ERROR] testSimpleGraphSvg(org.apache.oozie.util.graph.TestGraphGenerator) 
> Time elapsed: 24.113 s <<< FAILURE!
> java.lang.AssertionError: Render and write SVG failed: 
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at 
> org.apache.oozie.util.graph.TestGraphGenerator.testSimpleGraphSvg(TestGraphGenerator.java:144)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] TestGraphGenerator.testSimpleGraphSvg:144 Render and write SVG 
> failed: java.util.concurrent.ExecutionException: 
> java.lang.NullPointerException
> {code}
> Have observed that the test cases use the values from the enum OutputFormat 
> which contains 3 constants : PNG, DOT & SVG
> The test cases using OutputFormat.DOT have passed whereas the once which have 
> used the other two constants i.e PNG and SVG , fail on ppc64le arch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (109 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3189  Update the release script and wiki page to use sha512 instead of md5
https://issues.apache.org/jira/browse/OOZIE-3189
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
OOZIE-3185  Conflicting JARs org.apache.derby exist in Oozie
https://issues.apache.org/jira/browse/OOZIE-3185
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3176  Oozie-core fails with checkstyle errors.
https://issues.apache.org/jira/browse/OOZIE-3176
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3134  Potential inconsistency between the in-memory SLA map and the Oozie 
database
https://issues.apache.org/jira/browse/OOZIE-3134
OOZIE-3109  Escape log-streaming's HTML-specific characters
https://issues.apache.org/jira/browse/OOZIE-3109
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues.apache.org/jira/browse/OOZIE-3105
OOZIE-3094  fix for grammar mistake
https://issues.apache.org/jira/browse/OOZIE-3094
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-3061  Kill only those child jobs which are not already killed
https://issues.apache.org/jira/browse/OOZIE-3061
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues.apache.org/jira/browse/OOZIE-2957
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-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
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-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-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
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-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.