date:20170404

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

2017-04-04 Thread Apache Jenkins Server

See

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

2017-04-04 Thread Apache Jenkins Server

See 


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

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

[jira] [Commented] (OOZIE-2825) Custom Authentication doc page is not well formatted

2017-04-04 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-2825:
--

Thanks for taking a look at this.  I left some specific comments on RB, but I 
think this page needs a much larger refactoring than simply tweaking the 
examples. 

Given the general unclarity with this information, and the fact that a lot of 
what it's talking about is actually part of Hadoop (specifically, the 
hadoop-auth module), I think we'd be better off removing a bunch of this and 
pointing to the Hadoop documentation 
(https://hadoop.apache.org/docs/r2.7.2/hadoop-auth/index.html).

More specifically, I'd remove the code samples on this page.  They're really 
unhelpful.  Just point to the relevant Hadoop code instead.  We can keep the 
mention and descriptions of the various Hadoop classes, and the stuff under the 
"Provide Custom Authentication to Oozie Client" because that's Oozie-specific.  

> Custom Authentication doc page is not well formatted
> 
>
> Key: OOZIE-2825
> URL: https://issues.apache.org/jira/browse/OOZIE-2825
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Laszlo Zeke
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: OOZIE-2825-1.patch, OOZIE-2825-2.patch
>
>
> At line 30 there's a verbatim tag staring but don't end.
> Also at line 45 a paragraph is staring but it does not make a lot of sense 
> with a code sample seems to be cut in half.
> All in ENG_Custom_Authentication.twiki



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

Re: Review Request 57799: OOZIE-2825 Fixed custom Authentication doc page

2017-04-04 Thread Robert Kanter


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




docs/src/site/twiki/ENG_Custom_Authentication.twiki
Line 35 (original), 35 (patched)


It's not clear what TheAuthenticatorConf is supposed to be used for.  The 
code for it starting on line 55 doesn't seem to do anything other than wrap a 
hashmap...  And conf is never used here.



docs/src/site/twiki/ENG_Custom_Authentication.twiki
Lines 40-41 (original), 40-41 (patched)


This is pretty vague.



docs/src/site/twiki/ENG_Custom_Authentication.twiki
Line 58 (original), 52 (patched)


The sentence structure is weird here, but I think it's trying to say: "The 
following shows an example of a singleton configuration class which can be used 
by an Authentictor class to set and get config properties which are required by 
the Authenticator."

Even so, I'm not sure what this is for.



docs/src/site/twiki/ENG_Custom_Authentication.twiki
Line 90 (original), 84 (patched)


"... an Oozie client should..."


- Robert Kanter


On April 4, 2017, 12:39 p.m., Jan Hentschel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57799/
> ---
> 
> (Updated April 4, 2017, 12:39 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2825
> https://issues.apache.org/jira/browse/OOZIE-2825
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Fixed the code sample in the custom authentication page in the documentation.
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/ENG_Custom_Authentication.twiki 64334b6 
> 
> 
> Diff: https://reviews.apache.org/r/57799/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Jan Hentschel
> 
>

[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories

2017-04-04 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-2849:
--

I think it should be fine as long as we do it in a major release (i.e. 5.0.0) 
because it could break someone's deployment flow if they had previously been 
grabbing the directories and not the archives.

> Fix build warnings when assembling directories
> --
>
> Key: OOZIE-2849
> URL: https://issues.apache.org/jira/browse/OOZIE-2849
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2849-01.patch, OOZIE-2849-02.patch
>
>
> When building oozie we can observe a lot of warning
> {code}
> [WARNING] Assembly file: 
> /Users/asasvari/workspace/apache/oozie_dup/tools/target/oozie-tools-4.4.0-SNAPSHOT-tools
>  is not a regular file (it may be a directory). It cannot be attached to the 
> project build for installation or deployment.
> {code}
> This behaviour can be explained by 
> https://issues.apache.org/jira/browse/MASSEMBLY-628



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

[jira] [Commented] (OOZIE-1283) Remove the old ssh documentation

2017-04-04 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1283:
--

+1

> Remove the old ssh documentation
> 
>
> Key: OOZIE-1283
> URL: https://issues.apache.org/jira/browse/OOZIE-1283
> Project: Oozie
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Robert Kanter
>Assignee: Jan Hentschel
>Priority: Minor
>  Labels: newbie
> Attachments: OOZIE-1283-1.patch
>
>
> The documentation currently has info on the ssh action extension: 
> http://oozie.apache.org/docs/3.3.1/DG_SshActionExtension.html
> as well as the old one: 
> http://oozie.apache.org/docs/3.3.1/WorkflowFunctionalSpec.html#a3.2.5_Ssh_Action
> We should remove the old one or at least put a WARNING and a link to the new 
> one.



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

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

2017-04-04 Thread Apache Jenkins Server

See

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

2017-04-04 Thread Apache Jenkins Server

See 


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

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

Re: Review Request 57107: OOZIE-2815 oozie not always display job log

2017-04-04 Thread Purshotam Shah via Review Board


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

(Updated April 4, 2017, 7:41 p.m.)


Review request for oozie.


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


Repository: oozie-git


Description
---

OOZIE-2815 oozie not always display job log


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/BaseEngine.java 
50df8978773ed54fb5a39bb142d7235de1ed396f 
  core/src/main/java/org/apache/oozie/BundleEngine.java 
d0099b48772069217375c032d171e8dc6b1d 
  core/src/main/java/org/apache/oozie/CoordinatorEngine.java 
2f9f8227f1b2bbb0074cfa19aac37ab9a3fe7c0f 
  core/src/main/java/org/apache/oozie/DagEngine.java 
57d276199de149b294f64570a8878b660e9a5a0c 
  core/src/main/java/org/apache/oozie/service/XLogService.java 
04f04f41403fc6446967524124b8cf86f816d71c 
  core/src/main/java/org/apache/oozie/service/XLogStreamingService.java 
c15c4c1731838655d8f899f9c0405b226f8111b0 
  core/src/main/java/org/apache/oozie/service/ZKXLogStreamingService.java 
97771ad22be84d1a8167c69a6b48b7012652cf8b 
  core/src/main/java/org/apache/oozie/servlet/V0JobServlet.java 
d3b468965f33e300d7ca0f31efc596fd969b47a5 
  core/src/main/java/org/apache/oozie/servlet/V1JobServlet.java 
9356768639e6e3ea548b25baa75d576351fa80e3 
  core/src/main/java/org/apache/oozie/util/AuthUrlClient.java 
b45a96acc397c26cdba8d5c62503013dd572f247 
  core/src/main/java/org/apache/oozie/util/TimestampedMessageParser.java 
a676f4d35a49147aadde73357397b211ab829c85 
  core/src/main/java/org/apache/oozie/util/XLogAuditFilter.java 
c377db5df5dd0bbeed77b4d5c88e1c4e2e64a51e 
  core/src/main/java/org/apache/oozie/util/XLogAuditStreamer.java 
e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  core/src/main/java/org/apache/oozie/util/XLogErrorStreamer.java 
e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
  core/src/main/java/org/apache/oozie/util/XLogFilter.java 
3b49f77e016cbeaedfa03708dbc680e68f40ca16 
  core/src/main/java/org/apache/oozie/util/XLogStreamer.java 
19f1fee55ba8d6c456e798f01e55cfe84cfb5803 
  core/src/main/resources/oozie-default.xml 
95e0c36e1b2f5aef18637f6f956a990ba36166f2 
  core/src/test/java/org/apache/oozie/TestCoordinatorEngineStreamLog.java 
3eb1016f3ffccaa9db077580b90cc1b3c53fd479 
  core/src/test/java/org/apache/oozie/service/TestConfigurationService.java 
42ffdbeb41e5829cdf814cf13ada331973fc33bd 
  core/src/test/java/org/apache/oozie/service/TestXLogStreamingService.java 
bebb678798ec4a01c9710660d4b99fddd5167560 
  core/src/test/java/org/apache/oozie/service/TestZKXLogStreamingService.java 
fca8d844f1563da5856eff36f53f21d519630d31 
  core/src/test/java/org/apache/oozie/util/TestLogStreamer.java 
f90f784503e101ae2f96fee52977ee83f3098301 
  
core/src/test/java/org/apache/oozie/util/TestSimplifiedTimestampedMessageParser.java
 ea899faf00aa2f98f43838987c9b716321a50dea 
  core/src/test/java/org/apache/oozie/util/TestTimestampedMessageParser.java 
9e28cbc77129bb2675b92ec9c18c77accfd78a55 
  core/src/test/java/org/apache/oozie/util/TestXLogUserFilterParam.java 
46f273fde7f14b446463448c90f22519761997b6 
  webapp/src/main/webapp/oozie-console.js 
76864a9a06e98357c2d17e35609e2a76afbd595c 


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

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


Testing
---


Thanks,

Purshotam Shah

Re: Review Request 57107: OOZIE-2815 oozie not always display job log

2017-04-04 Thread Purshotam Shah via Review Board



> On March 31, 2017, 5:48 p.m., Satish Saley wrote:
> > core/src/main/java/org/apache/oozie/service/ZKXLogStreamingService.java
> > Line 324 (original), 251 (patched)
> > 
> >
> > I see that we are truncating logs for XLogErrorStreamer and 
> > XLogAuditStreamer rather than throwing exception.
> > But still there could be exeptions (may not be explicitly thrown) such 
> > as IOException from TimestampedMessageParser.increment() method. It would 
> > be safer to have a catch block, setting isException=true and flushing to 
> > the writer only if isException is false. That will take care of OOZIE-2636

We don't have to call flush on finally block. Writer is HttpServletResponse 
writer. In the end, the container will flush and close the HttpServletResponse 
stream.


> On March 31, 2017, 5:48 p.m., Satish Saley wrote:
> > core/src/main/java/org/apache/oozie/service/ZKXLogStreamingService.java
> > Line 324 (original), 251 (patched)
> > 
> >
> > I see that we are truncating logs for XLogErrorStreamer and 
> > XLogAuditStreamer rather than throwing exception.
> > But still there could be exeptions (may not be explicitly thrown) such 
> > as IOException from TimestampedMessageParser.increment() method. It would 
> > be safer to have a catch block, setting isException=true and flushing to 
> > the writer only if isException is false. That will take care of OOZIE-2636

We don't have to call flush on finally block. Writer is HttpServletResponse 
writer. In the end, the container will flush and close the HttpServletResponse 
stream.


- Purshotam


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


On March 14, 2017, 2:03 a.m., Purshotam Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57107/
> ---
> 
> (Updated March 14, 2017, 2:03 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2815
> https://issues.apache.org/jira/browse/OOZIE-2815
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2815 oozie not always display job log
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/BaseEngine.java 
> 50df8978773ed54fb5a39bb142d7235de1ed396f 
>   core/src/main/java/org/apache/oozie/BundleEngine.java 
> d0099b48772069217375c032d171e8dc6b1d 
>   core/src/main/java/org/apache/oozie/CoordinatorEngine.java 
> 2f9f8227f1b2bbb0074cfa19aac37ab9a3fe7c0f 
>   core/src/main/java/org/apache/oozie/DagEngine.java 
> 57d276199de149b294f64570a8878b660e9a5a0c 
>   core/src/main/java/org/apache/oozie/service/XLogService.java 
> 04f04f41403fc6446967524124b8cf86f816d71c 
>   core/src/main/java/org/apache/oozie/service/XLogStreamingService.java 
> c15c4c1731838655d8f899f9c0405b226f8111b0 
>   core/src/main/java/org/apache/oozie/service/ZKXLogStreamingService.java 
> 97771ad22be84d1a8167c69a6b48b7012652cf8b 
>   core/src/main/java/org/apache/oozie/servlet/V0JobServlet.java 
> d3b468965f33e300d7ca0f31efc596fd969b47a5 
>   core/src/main/java/org/apache/oozie/servlet/V1JobServlet.java 
> 9356768639e6e3ea548b25baa75d576351fa80e3 
>   core/src/main/java/org/apache/oozie/util/AuthUrlClient.java 
> b45a96acc397c26cdba8d5c62503013dd572f247 
>   core/src/main/java/org/apache/oozie/util/TimestampedMessageParser.java 
> a676f4d35a49147aadde73357397b211ab829c85 
>   core/src/main/java/org/apache/oozie/util/XLogAuditFilter.java 
> c377db5df5dd0bbeed77b4d5c88e1c4e2e64a51e 
>   core/src/main/java/org/apache/oozie/util/XLogAuditStreamer.java 
> e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
>   core/src/main/java/org/apache/oozie/util/XLogErrorStreamer.java 
> e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 
>   core/src/main/java/org/apache/oozie/util/XLogFilter.java 
> 3b49f77e016cbeaedfa03708dbc680e68f40ca16 
>   core/src/main/java/org/apache/oozie/util/XLogStreamer.java 
> 19f1fee55ba8d6c456e798f01e55cfe84cfb5803 
>   core/src/main/resources/oozie-default.xml 
> 95e0c36e1b2f5aef18637f6f956a990ba36166f2 
>   core/src/test/java/org/apache/oozie/TestCoordinatorEngineStreamLog.java 
> 3eb1016f3ffccaa9db077580b90cc1b3c53fd479 
>   core/src/test/java/org/apache/oozie/service/TestConfigurationService.java 
> 42ffdbeb41e5829cdf814cf13ada331973fc33bd 
>   core/src/test/java/org/apache/oozie/service/TestXLogStreamingService.java 
> bebb678798ec4a01c9710660d4b99fddd5167560 
>   core/src/test/java/org/apache/oozie/service/TestZKXLogStreamingService.java 
> fca8d844f1563da5856eff36f53f21d519630d31 
>   core/src/test/java/org/apache/oozie/util/TestLogStreamer.java 
> f90f784503e101ae2f96fee52977ee83f3098301 
>   
>

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-2850:
--

Did we verify that when HTTPS is turned on this only opens up HTTP for the 
{{/oozie/callback}} addresses and not for other addresses like {{/oozie/jobs}}? 
 If so, then +1 from me.

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch, 
> OOZIE-2850-06.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] [Commented] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

2017-04-04 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2701:
--

Testing JIRA OOZIE-2701

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:red}-1{color} the patch contains 1 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1912
.Tests rerun: 15
.Tests failed at first run: org.apache.oozie.jms.TestJMSJobEventListener,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

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

> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch, OOZIE-2701-04.patch, 
> OOZIE-2701-05.patch, OOZIE-2701-06.patch, OOZIE-2701-07.patch, 
> OOZIE-2701-08.patch, OOZIE-2701-09.patch, OOZIE-2701-10.patch, 
> OOZIE-2701-11.patch, OOZIE-2701-12.patch
>
>




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

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

2017-04-04 Thread Apache Jenkins Server

See 


--
[...truncated 964.65 KB...]
[INFO] Copying jersey-client-1.9.jar to 

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

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

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

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

[INFO] Copying serp-1.15.1.jar to 

[INFO] Copying asm-5.0.1.jar to 

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

[INFO] Copying opencsv-2.3.jar to 

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

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

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

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

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

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

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

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

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-distro ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/distro.xml
[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] Building tar : 

[INFO]

[jira] [Updated] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Attila Sasvari (JIRA)


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

Attila Sasvari updated OOZIE-2850:
--
Attachment: OOZIE-2850-06.patch

[~gezapeti] thanks for reviewing and testing it on a secure cluster. tab 
removed in the new patch

(would be nice to improve test-patch to show here the location)

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch, 
> OOZIE-2850-06.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] [Comment Edited] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Peter Cseh (JIRA)


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

Peter Cseh edited comment on OOZIE-2850 at 4/4/17 3:50 PM:
---

I've tried out the -05 patch on a secure cluster and the callbacks are working 
nicely.
There is a tab in the patch, please fix that [~asasvari], otherwise +1.




was (Author: gezapeti):
I've tried out the -05 patch on a secure cluster and the callbacks are working 
nicely.
Thanks for the patch [~asasvari], +1.


> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2850:
---

I've tried out the -05 patch on a secure cluster and the callbacks are working 
nicely.
Thanks for the patch [~asasvari], +1.


> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] [Updated] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

2017-04-04 Thread Abhishek Bafna (JIRA)


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

Abhishek Bafna updated OOZIE-2701:
--
Attachment: OOZIE-2701-12.patch

> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch, OOZIE-2701-04.patch, 
> OOZIE-2701-05.patch, OOZIE-2701-06.patch, OOZIE-2701-07.patch, 
> OOZIE-2701-08.patch, OOZIE-2701-09.patch, OOZIE-2701-10.patch, 
> OOZIE-2701-11.patch, OOZIE-2701-12.patch
>
>




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

[jira] [Commented] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

2017-04-04 Thread Abhishek Bafna (JIRA)


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

Abhishek Bafna commented on OOZIE-2701:
---

[~gezapeti] The difference is between two terms {{multiple HCatalog servers in 
the URI}} v/s {{multiple HCatalog URI}}. 

The first is regarding, when user is having single HCat URI which gets parsed 
using the HCatURIParser#parseURI.
The second is regarding, when user is having multiple HCat URIs in place. 

I have improved the testcase 
{{TestHCatURIParser#testParsingMultipleHCatServerURI}} and added some more doc. 
Please let me know, If this needs more improvement. :)

PS: The patch will have a doc line which is more than 132 character.

Thanks.



> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch, OOZIE-2701-04.patch, 
> OOZIE-2701-05.patch, OOZIE-2701-06.patch, OOZIE-2701-07.patch, 
> OOZIE-2701-08.patch, OOZIE-2701-09.patch, OOZIE-2701-10.patch, 
> OOZIE-2701-11.patch, OOZIE-2701-12.patch
>
>




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

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

2017-04-04 Thread Apache Jenkins Server

See 


--
[...truncated 964.91 KB...]
[INFO] Copying hadoop-annotations-2.4.0.jar to 

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

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

[INFO] Copying serp-1.15.1.jar to 

[INFO] Copying asm-5.0.1.jar to 

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

[INFO] Copying opencsv-2.3.jar to 

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

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

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

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

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

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

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

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

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-distro ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/distro.xml
[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] Building tar : 

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

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2850:
--

Testing JIRA OOZIE-2850

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 1 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:orange}0{color} There are [1] new bugs found in total that would be nice 
to have fixed.
. {color:orange}0{color} There are [1] new bugs found in [server] that would be 
nice to have fixed.
. You can find the FindBugs diff here: server/findbugs-new.html
. {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/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/hcatalog].
. {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/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/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
. {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 [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: 1907
.Tests rerun: 2
.Tests failed at first run: 
org.apache.oozie.command.coord.TestCoordActionsKillXCommand,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

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

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch, OOZIE-2850-05.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] [Commented] (OOZIE-2825) Custom Authentication doc page is not well formatted

2017-04-04 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2825:
--

Testing JIRA OOZIE-2825

Cleaning local git workspace

> Custom Authentication doc page is not well formatted
> 
>
> Key: OOZIE-2825
> URL: https://issues.apache.org/jira/browse/OOZIE-2825
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Laszlo Zeke
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: OOZIE-2825-1.patch, OOZIE-2825-2.patch
>
>
> At line 30 there's a verbatim tag staring but don't end.
> Also at line 45 a paragraph is staring but it does not make a lot of sense 
> with a code sample seems to be cut in half.
> All in ENG_Custom_Authentication.twiki



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

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

2017-04-04 Thread Apache Jenkins Server

See 


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

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 6bac84745b9c62907e8cc6a16bad6c76ac3eb9c6 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 6bac84745b9c62907e8cc6a16bad6c76ac3eb9c6
 > git rev-list 6bac84745b9c62907e8cc6a16bad6c76ac3eb9c6 # timeout=10
[oozie-trunk-precommit-build] $ /bin/bash /tmp/hudson7850229562081914882.sh
rm: cannot remove 'distro/downloads/*': No such file or directory
rm: invalid option -- '.'
Try 'rm --help' for more information.

Testing JIRA OOZIE-2825

  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0  0   
  00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0  0 0 
   0 00 0  0  0 --:--:--  0:00:05 --:--:-- 0  0 0   
 0 00 0  0  0 --:--:--  0:00:06 --:--:-- 0  0 0
0 00 0  0  0 --:--:--  0:00:07 --:--:-- 0  0 00 
00 0  0  0 --:--:--  0:00:08 --:--:-- 0  0 00   
  00 0  0  0 --:--:--  0:00:09 --:--:-- 0  0 00 
00 0  0  0 --:--:--  0:00:10 --:--:-- 0  0 00 0 
   0 0  0  0 --:--:--  0:00:11 --:--:-- 0  0 00 0   
 0 0  0  0 --:--:--  0:00:12 --:--:-- 0  0 00 0
0 0  0  0 --:--:--  0:00:13 --:--:-- 0  0 00 00 
0  0  0 --:--:--  0:00:14 --:--:-- 0  0 00 00   
  0  0  0 --:--:--  0:00:15 --:--:-- 0  0 00 00 
0  0  0 --:--:--  0:00:16 --:--:-- 0  0 00 00 0 
 0  0 --:--:--  0:00:17 --:--:-- 0  0 00 00 0   
   0  0 --:--:--  0:00:18 --:--:-- 0  0 00 00 0 
 0  0 --:--:--  0:00:19 --:--:-- 0  0 00 00 0  
0  0 --:--:--  0:00:20 --:--:-- 0  0 00 00 0  0 
 0 --:--:--  0:00:21 --:--:-- 0  0 00 00 0  0   
   0 --:--:--  0:00:22 --:--:-- 0  0 00 00 0  0 
 0 --:--:--  0:00:23 --:--:-- 0  0 00 00 0  0  
0 --:--:--  0:00:24 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:25 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:26 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:27 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:28 --:--:-- 0  0   2990 00 0  0  0 
--:--:--  0:00:29 --:--:-- 0100   299  100   2990 0 10  0  
0:00:29  0:00:29 --:--:--81
OOZIE-2825 is not "Patch Available".  Exiting.

Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: Test reports were found 
but none of them are new. Did tests run? 
For example, 

 is 6 hr 5 min old

[jira] [Commented] (OOZIE-1283) Remove the old ssh documentation

2017-04-04 Thread Jan Hentschel (JIRA)


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

Jan Hentschel commented on OOZIE-1283:
--

The failing test seems to be unrelated to the actual change. Only content of 
the documentation was changed in this patch.

> Remove the old ssh documentation
> 
>
> Key: OOZIE-1283
> URL: https://issues.apache.org/jira/browse/OOZIE-1283
> Project: Oozie
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Robert Kanter
>Assignee: Jan Hentschel
>Priority: Minor
>  Labels: newbie
> Attachments: OOZIE-1283-1.patch
>
>
> The documentation currently has info on the ssh action extension: 
> http://oozie.apache.org/docs/3.3.1/DG_SshActionExtension.html
> as well as the old one: 
> http://oozie.apache.org/docs/3.3.1/WorkflowFunctionalSpec.html#a3.2.5_Ssh_Action
> We should remove the old one or at least put a WARNING and a link to the new 
> one.



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

[jira] [Updated] (OOZIE-2825) Custom Authentication doc page is not well formatted

2017-04-04 Thread Jan Hentschel (JIRA)


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

Jan Hentschel updated OOZIE-2825:
-
Attachment: OOZIE-2825-2.patch

Fixed problems with tabs from QA build.

> Custom Authentication doc page is not well formatted
> 
>
> Key: OOZIE-2825
> URL: https://issues.apache.org/jira/browse/OOZIE-2825
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Laszlo Zeke
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: OOZIE-2825-1.patch, OOZIE-2825-2.patch
>
>
> At line 30 there's a verbatim tag staring but don't end.
> Also at line 45 a paragraph is staring but it does not make a lot of sense 
> with a code sample seems to be cut in half.
> All in ENG_Custom_Authentication.twiki



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

Re: Review Request 57799: OOZIE-2825 Fixed custom Authentication doc page

2017-04-04 Thread Jan Hentschel


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

(Updated April 4, 2017, 2:39 p.m.)


Review request for oozie.


Changes
---

Fixed problems with tabs from QA build.


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


Repository: oozie-git


Description
---

Fixed the code sample in the custom authentication page in the documentation.


Diffs (updated)
-

  docs/src/site/twiki/ENG_Custom_Authentication.twiki 64334b6 


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

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


Testing
---


Thanks,

Jan Hentschel

[jira] [Created] (OOZIE-2858) HiveMain, ShellMain and SparkMain should not overwrite properties and config files locally

2017-04-04 Thread Peter Cseh (JIRA)

Peter Cseh created OOZIE-2858:
-

 Summary: HiveMain, ShellMain and SparkMain should not overwrite 
properties and config files locally
 Key: OOZIE-2858
 URL: https://issues.apache.org/jira/browse/OOZIE-2858
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Cseh


We're generating files on the fly in many of our *Main classes.
These are usually log4j.properties and hive-site.xml files (there may be 
others, but these are the ones I managed to find).

We should check if these files are there in advance and don't overwrite them if 
they are present. We could log a warning in this case or merge the contents of 
the files with the things we want to write into it. There is an example for 
this in PigMain and log4j.properties.




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

Re: Review Request 58171: OOZIE-2844 Increase stability of Oozie actions when log4j.properties is missing or not readable

2017-04-04 Thread Peter Bacsko


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




sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java
Line 31 (original), 31 (patched)


Please avoid "*" imports



sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java
Lines 59 (patched)


Could you please add a comment here about what this properties actually is 
and why is it used? 

Also, for me it's not evident what "auxiliary" means in this context. What 
about a name like "log4j-default.properties" ?



sharelib/oozie/src/main/resources/auxiliary-log4j.properties
Lines 1 (patched)


Where does the contents of this file come from?


- Peter Bacsko


On ápr. 4, 2017, 10:37 de, András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/58171/
> ---
> 
> (Updated ápr. 4, 2017, 10:37 de)
> 
> 
> Review request for oozie and Peter Bacsko.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> In several Oozie actions we face the problem that if `log4j.properties` is 
> not readable by current thread, or not present on the classpath, while taking 
> an `URL.openStream()` call afterwards, an `IOException` is thrown and the 
> action won't run.
> 
> Such actions are:
> 
> * 
> [`DistcpMain`](https://github.com/apache/oozie/blob/master/sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java#L135)
> * 
> [`HiveMain`](https://github.com/apache/oozie/blob/master/sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java#L146)
> * 
> [`PigMain`](https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java#L173)
> * 
> [`PigMainWithOldApi`](https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java#L160)
> * 
> [`SparkMain`](https://github.com/apache/oozie/blob/master/sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java#L430)
> * 
> [`SqoopMain`](https://github.com/apache/oozie/blob/master/sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java#L124)
> 
> Extend 
> [`LauncherMain.run()`](https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java#L62-L65)
>  by a convenience method that loads Hadoop's `log4j.properties` in 
> beforehand. In case `URL.openStream()` would throw `IOException` we resort to 
> a call to a new file `hadoop-default-log4j.properties` on the classpath 
> (packaged along w/ `LauncherMain.class`) that has the same contents as the 
> `log4j.properties` that is not accessible / readable / present.
> 
> 
> Diffs
> -
> 
>   
> sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java 
> fcaadefd215368565fb126ca92515792e1f1a09b 
>   sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java 
> bc8ab29c25405806f40232d32254ba2a7f5271e4 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
> 7ae48e168a310b4d55feda7cbce8b2d29c2ec505 
>   sharelib/oozie/src/main/resources/auxiliary-log4j.properties PRE-CREATION 
>   
> sharelib/oozie/src/test/java/org/apache/oozie/action/hadoop/TestLauncherMain.java
>  PRE-CREATION 
>   sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java 
> ba393eee53e92d144159f83893d4baab00737a44 
>   
> sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java
>  14ab65e7d00c426036ced3e80400c80deea0e282 
>   sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java 
> c24d95c88be0dbf6fe80241d887a70100a5e1b4a 
>   sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java 
> cb8f56e9b66de0eb2799e68bc56d0ee36d4ba317 
> 
> 
> Diff: https://reviews.apache.org/r/58171/diff/1/
> 
> 
> Testing
> ---
> 
> Relevant unit tests run.
> 
> 
> Thanks,
> 
> András Piros
> 
>

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

2017-04-04 Thread Apache Jenkins Server

See 


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

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

[jira] [Commented] (OOZIE-2844) Increase stability of Oozie actions when log4j.properties is missing or not readable

2017-04-04 Thread Peter Bacsko (JIRA)


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

Peter Bacsko commented on OOZIE-2844:
-

[~andras.piros] please create a ReviewBoard review

> Increase stability of Oozie actions when log4j.properties is missing or not 
> readable
> 
>
> Key: OOZIE-2844
> URL: https://issues.apache.org/jira/browse/OOZIE-2844
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 4.3.0
>
> Attachments: OOZIE-2844.001.patch, OOZIE-2844.002.patch
>
>
> In several Oozie actions we face the problem that if {{log4j.properties}} is 
> not readable by current thread, or not present on the classpath, while taking 
> an {{URL.openStream()}} call afterwards, an {{IOException}} is thrown and the 
> action won't run.
> Such actions are:
> * 
> [*{{DistcpMain}}*|https://github.com/apache/oozie/blob/master/sharelib/distcp/src/main/java/org/apache/oozie/action/hadoop/DistcpMain.java#L135]
> * 
> [*{{HiveMain}}*|https://github.com/apache/oozie/blob/master/sharelib/hive/src/main/java/org/apache/oozie/action/hadoop/HiveMain.java#L146]
> * 
> [*{{PigMain}}*|https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java#L173]
> * 
> [*{{PigMainWithOldApi}}*|https://github.com/apache/oozie/blob/master/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMainWithOldAPI.java#L160]
> * 
> [*{{SparkMain}}*|https://github.com/apache/oozie/blob/master/sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkMain.java#L430]
> * 
> [*{{SqoopMain}}*|https://github.com/apache/oozie/blob/master/sharelib/sqoop/src/main/java/org/apache/oozie/action/hadoop/SqoopMain.java#L124]
> Extend 
> [*{{LauncherMain.run()}}*|https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java#L62-L65]
>  by a convenience method that loads Hadoop's {{log4j.properties}} in 
> beforehand. In case {{URL.openStream()}} would throw {{IOException}} we 
> resort to a call to a new file {{hadoop-default-log4j.properties}} on the 
> classpath (packaged along w/ {{LauncherMain.class}}) that has the same 
> contents as the {{log4j.properties}} that is not accessible / readable / 
> present.



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

[jira] [Commented] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Peter Bacsko (JIRA)


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

Peter Bacsko commented on OOZIE-2850:
-

Few comments:

* {{CONTEXT_PATH}} is package private. Is this the visibility we want? Should 
it be static? If it's meant to be changed, then it should be named like 
"contextPath"
* The default value should be null, not an empty string
* Rename {{constraintHandlersCanBeSet}} to {{testConstraintHandlersCanBeSet}} 
to be consistent with existing tests

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories

2017-04-04 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2849:
--

Testing JIRA OOZIE-2849

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1906
.Tests failed: 5
.Tests errors: 3

.The patch failed the following testcases:

.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)

.Tests failing with errors:
.  testAddXIncludeFromStream(org.apache.oozie.util.TestXConfiguration)
.  testAddXIncludeFromReader(org.apache.oozie.util.TestXConfiguration)
.  testLoadDump(org.apache.oozie.tools.TestDBLoadDump)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

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

> Fix build warnings when assembling directories
> --
>
> Key: OOZIE-2849
> URL: https://issues.apache.org/jira/browse/OOZIE-2849
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2849-01.patch, OOZIE-2849-02.patch
>
>
> When building oozie we can observe a lot of warning
> {code}
> [WARNING] Assembly file: 
> /Users/asasvari/workspace/apache/oozie_dup/tools/target/oozie-tools-4.4.0-SNAPSHOT-tools
>  is not a regular file (it may be a directory). It cannot be attached to the 
> project build for installation or deployment.
> {code}
> This behaviour can be explained by 
> https://issues.apache.org/jira/browse/MASSEMBLY-628



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

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

2017-04-04 Thread Apache Jenkins Server

See 


--
[...truncated 966.99 KB...]
[INFO] Copying jackson-core-2.2.2.jar to 

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

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

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

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-distro ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/distro.xml
[INFO] Copying files to 

[INFO] Building tar : 

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

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

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ 
oozie-zookeeper-security-tests ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
oozie-zookeeper-security-tests ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main

[jira] [Created] (OOZIE-2857) oozie-trunk-precommit-build tries to delete non-existing downloads directory

2017-04-04 Thread Attila Sasvari (JIRA)

Attila Sasvari created OOZIE-2857:
-

 Summary: oozie-trunk-precommit-build tries to delete non-existing 
downloads directory 
 Key: OOZIE-2857
 URL: https://issues.apache.org/jira/browse/OOZIE-2857
 Project: Oozie
  Issue Type: Improvement
Reporter: Attila Sasvari


Pre-commit build logs contain errors like the following

{code}
[oozie-trunk-precommit-build] $ /bin/bash /tmp/hudson4474802453375480488.sh
rm: cannot remove 'distro/downloads/*': No such file or directory
rm: invalid option -- '.'
Try 'rm --help' for more information.
{code}

As Tomcat is not downloaded anymore, oozie-trunk-precommit-build jenkins job 
should be updated.



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

[jira] [Created] (OOZIE-2856) Show in JIRA comment exactly which patch was tested by jenkins job

2017-04-04 Thread Attila Sasvari (JIRA)

Attila Sasvari created OOZIE-2856:
-

 Summary: Show in JIRA comment exactly which patch was tested by 
jenkins job
 Key: OOZIE-2856
 URL: https://issues.apache.org/jira/browse/OOZIE-2856
 Project: Oozie
  Issue Type: Improvement
Reporter: Attila Sasvari
Priority: Minor


Currently you cannot see in the JIRA comments which patch was applied
{code}
Testing JIRA OOZIE-2850
Cleaning local git workspace

+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
. +1 the patch does not introduce any @author tags
{code}

test-patch could updated so that it also writes out the exact patchfile's name. 



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

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

2017-04-04 Thread Apache Jenkins Server

See 


--
[...truncated 889.94 KB...]
[INFO] Apache Oozie Distro  SKIPPED
[INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 02:55 min
[INFO] Finished at: 2017-04-04T08:43:11+00:00
[INFO] Final Memory: 108M/1179M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile 
(default-testCompile) on project oozie-server: Compilation failure
[ERROR] 
:[63,91]
 error: CONTEXT_PATH is not public in EmbeddedOozieServer; cannot be accessed 
from outside package
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :oozie-server

Reports
  Running test-patch task CLEAN
  Running test-patch task RAW_PATCH_ANALYSIS
  Running test-patch task RAT
  Running test-patch task JAVADOC
  Running test-patch task COMPILE
  Running test-patch task FINDBUGS_DIFF
[TRACE] Downloading FindBugs diff JAR from 
https://repo1.maven.org/maven2/me/andrz/findbugs/findbugs-diff/0.1.0/findbugs-diff-0.1.0-all.jar
[TRACE] FindBugs diff JAR downloaded
grep: 
:
 No such file or directory
[TRACE] FindBugs diff JAR checked, is safe to use
[TRACE] Performing FindBugs diffs
bin/test-patch-11-findbugs-diff: line 253: : No such file or directory
bin/test-patch-11-findbugs-diff: line 255: [: -le: unary operator expected
Exception in thread "main" groovy.lang.GroovyRuntimeException: Ambiguous method 
overloading for method java.io.File#.
Cannot resolve which method to invoke for [null] due to overlapping prototypes 
between:
[class java.lang.String]
[class java.net.URI]
at 
groovy.lang.MetaClassImpl.chooseMostSpecificParams(MetaClassImpl.java:3202)
at 
groovy.lang.MetaClassImpl.chooseMethodInternal(MetaClassImpl.java:3154)
at groovy.lang.MetaClassImpl.chooseMethod(MetaClassImpl.java:3097)
at 
groovy.lang.MetaClassImpl.createConstructorSite(MetaClassImpl.java:3384)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallConstructorSite(CallSiteArray.java:88)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:57)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:182)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:190)
at 
me.andrz.findbugs.diff.FindBugsDiff.diffFromFilePaths(FindBugsDiff.groovy:33)
at me.andrz.findbugs.diff.FindBugsDiff$diffFromFilePaths.call(Unknown 
Source)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
at me.andrz.findbugs.diff.FindBugsDiffIo.run(FindBugsDiffIo.groovy:21)
at me.andrz.findbugs.diff.FindBugsDiffIo$run.call(Unknown Source)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at 
me.andrz.findbugs.diff.FindBugsDiffCli.handleFileOpts(FindBugsDiffCli.groovy:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at 
org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite$StaticMetaMethodSiteNoUnwrapNoCoerce.invoke(StaticMetaMethodSite.java:148)
at

[jira] [Updated] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Attila Sasvari (JIRA)


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

Attila Sasvari updated OOZIE-2850:
--
Attachment: OOZIE-2850-04.patch

rebased patch

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch, OOZIE-2850-04.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories

2017-04-04 Thread Attila Sasvari (JIRA)


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

Attila Sasvari commented on OOZIE-2849:
---

[~gezapeti] can you take a look? thanks!

> Fix build warnings when assembling directories
> --
>
> Key: OOZIE-2849
> URL: https://issues.apache.org/jira/browse/OOZIE-2849
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2849-01.patch, OOZIE-2849-02.patch
>
>
> When building oozie we can observe a lot of warning
> {code}
> [WARNING] Assembly file: 
> /Users/asasvari/workspace/apache/oozie_dup/tools/target/oozie-tools-4.4.0-SNAPSHOT-tools
>  is not a regular file (it may be a directory). It cannot be attached to the 
> project build for installation or deployment.
> {code}
> This behaviour can be explained by 
> https://issues.apache.org/jira/browse/MASSEMBLY-628



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

[jira] [Commented] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

2017-04-04 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2701:
---

Thanks for the update [~abhishekbafna]!
I'm a bit confused with the docs:
When you have multiple HCat servers, you were defining the scheme for each of 
them in the tests like
{quote}
"hcat://hostname1:1000,hcat://hostname2:2000/mydb/clicks/datastamp=12;region=us,scheme://hostname3:3000,"
{quote}
In the documentation description and in the example, you're defining the scheme 
only once:
{quote}
hcat://[metastore_server]:[port],[metastore_server]:[port]/[database_name]/[table_name]/[partkey1]=[value];[partkey2]=[value];
hcat://myhcatmetastore:9080,myhcatmetastore:9080/database1/table1/datestamp=${YEAR}${MONTH}${DAY}${HOUR};region=USA
{quote}
I don't think the pattern in oozie-default.xml would match the URIs in the 
documentation.

> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch, OOZIE-2701-04.patch, 
> OOZIE-2701-05.patch, OOZIE-2701-06.patch, OOZIE-2701-07.patch, 
> OOZIE-2701-08.patch, OOZIE-2701-09.patch, OOZIE-2701-10.patch, 
> OOZIE-2701-11.patch
>
>




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

[jira] [Comment Edited] (OOZIE-2701) Oozie to support Multiple HCatalog URIs

2017-04-04 Thread Peter Cseh (JIRA)


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

Peter Cseh edited comment on OOZIE-2701 at 4/4/17 7:49 AM:
---

Thanks for the update [~abhishekbafna]!
I'm a bit confused with the docs:
When you have multiple HCat servers, you were defining the scheme for each of 
them in the tests like
{noformat}
"hcat://hostname1:1000,hcat://hostname2:2000/mydb/clicks/datastamp=12;region=us,scheme://hostname3:3000,"
{noformat}
In the documentation description and in the example, you're defining the scheme 
only once:
{noformat}
hcat://[metastore_server]:[port],[metastore_server]:[port]/[database_name]/[table_name]/[partkey1]=[value];[partkey2]=[value];
hcat://myhcatmetastore:9080,myhcatmetastore:9080/database1/table1/datestamp=${YEAR}${MONTH}${DAY}${HOUR};region=USA
{noformat}
I don't think the pattern in oozie-default.xml would match the URIs in the 
documentation.


was (Author: gezapeti):
Thanks for the update [~abhishekbafna]!
I'm a bit confused with the docs:
When you have multiple HCat servers, you were defining the scheme for each of 
them in the tests like
{quote}
"hcat://hostname1:1000,hcat://hostname2:2000/mydb/clicks/datastamp=12;region=us,scheme://hostname3:3000,"
{quote}
In the documentation description and in the example, you're defining the scheme 
only once:
{quote}
hcat://[metastore_server]:[port],[metastore_server]:[port]/[database_name]/[table_name]/[partkey1]=[value];[partkey2]=[value];
hcat://myhcatmetastore:9080,myhcatmetastore:9080/database1/table1/datestamp=${YEAR}${MONTH}${DAY}${HOUR};region=USA
{quote}
I don't think the pattern in oozie-default.xml would match the URIs in the 
documentation.

> Oozie to support Multiple HCatalog URIs
> ---
>
> Key: OOZIE-2701
> URL: https://issues.apache.org/jira/browse/OOZIE-2701
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2701-00.patch, OOZIE-2701-01.patch, 
> OOZIE-2701-02.patch, OOZIE-2701-03.patch, OOZIE-2701-04.patch, 
> OOZIE-2701-05.patch, OOZIE-2701-06.patch, OOZIE-2701-07.patch, 
> OOZIE-2701-08.patch, OOZIE-2701-09.patch, OOZIE-2701-10.patch, 
> OOZIE-2701-11.patch
>
>




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

[jira] [Updated] (OOZIE-2849) Fix build warnings when assembling directories

2017-04-04 Thread Attila Sasvari (JIRA)


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

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

[~rkanter] you are right, I should have not removed the {{dir}} format in 
client.xml (oozie script only got into the tar.gz). Added it back. What about 
the others do we need sharelib and examples in dir format? (I always used the 
sharelib and examples as tar.gz files)  

> Fix build warnings when assembling directories
> --
>
> Key: OOZIE-2849
> URL: https://issues.apache.org/jira/browse/OOZIE-2849
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2849-01.patch, OOZIE-2849-02.patch
>
>
> When building oozie we can observe a lot of warning
> {code}
> [WARNING] Assembly file: 
> /Users/asasvari/workspace/apache/oozie_dup/tools/target/oozie-tools-4.4.0-SNAPSHOT-tools
>  is not a regular file (it may be a directory). It cannot be attached to the 
> project build for installation or deployment.
> {code}
> This behaviour can be explained by 
> https://issues.apache.org/jira/browse/MASSEMBLY-628



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

[jira] [Updated] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Attila Sasvari (JIRA)


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

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

fix rat warning - add license to new test class

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch, 
> OOZIE-2850-03.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] [Updated] (OOZIE-2850) Fix default callback notifications

2017-04-04 Thread Attila Sasvari (JIRA)


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

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

fix findbugs warnings

> Fix default callback notifications
> --
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2850-01.patch, OOZIE-2850-02.patch
>
>
> Currently oozie.service.CallbackService.base.url  in oozie-default.xml is set 
> to use 
> [oozie.base.url/callback| 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to 
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on 
> HTTP port 11000, see [port in oozie-default.xml | 
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in 
> {{oozie.base.url}}



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

[jira] Subscription: Oozie Patch Available

2017-04-04 Thread jira

Issue Subscription
Filter: Oozie Patch Available (100 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2851  spelling mistakes in examples
https://issues.apache.org/jira/browse/OOZIE-2851
OOZIE-2850  Fix default callback notifications
https://issues.apache.org/jira/browse/OOZIE-2850
OOZIE-2849  Fix build warnings when assembling directories
https://issues.apache.org/jira/browse/OOZIE-2849
OOZIE-2848  Override sharelib.tgz in distro when rebuilding Oozie
https://issues.apache.org/jira/browse/OOZIE-2848
OOZIE-2846  TestSSLServerConnectorFactory fails with Jetty 9.3 and 9.4
https://issues.apache.org/jira/browse/OOZIE-2846
OOZIE-2844  Increase stability of Oozie actions when log4j.properties is 
missing or not readable
https://issues.apache.org/jira/browse/OOZIE-2844
OOZIE-2843  Enhance logging inside ZKLocksService and MemoryLocksService
https://issues.apache.org/jira/browse/OOZIE-2843
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2827  More directly view of the coordinator’s history from perspective of 
workflow action.
https://issues.apache.org/jira/browse/OOZIE-2827
OOZIE-2825  Custom Authentication doc page is not well formatted
https://issues.apache.org/jira/browse/OOZIE-2825
OOZIE-2824  Fix typos in documentation
https://issues.apache.org/jira/browse/OOZIE-2824
OOZIE-2818  Can't overwrite oozie.action.max.output.data on a per-workflow basis
https://issues.apache.org/jira/browse/OOZIE-2818
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2796  oozie.action.keep.action.dir not getting noticed
https://issues.apache.org/jira/browse/OOZIE-2796
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2785  Master is not compiling with hadoop-1 profile
https://issues.apache.org/jira/browse/OOZIE-2785
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2780  Upgrade hadoop-common version to 2.6.0
https://issues.apache.org/jira/browse/OOZIE-2780
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2769  Extend FS action to allow setrep on a file
https://issues.apache.org/jira/browse/OOZIE-2769
OOZIE-2751  LocalOozieClient is missing methods from OozieClient
https://issues.apache.org/jira/browse/OOZIE-2751
OOZIE-2746  Several tests failure in TestV2ValidateServlet.java
https://issues.apache.org/jira/browse/OOZIE-2746
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2733  change org.apache.hadoop.fs.permission.AccessControlException to 
org.apache.hadoop.security.AccessControlException
https://issues.apache.org/jira/browse/OOZIE-2733
OOZIE-2726  Flaky test due to daylight saving changes
https://issues.apache.org/jira/browse/OOZIE-2726
OOZIE-2718  Improve -dryrun for bundles
https://issues.apache.org/jira/browse/OOZIE-2718
OOZIE-2713  Provide an option to log out contents of the localized jar files
https://issues.apache.org/jira/browse/OOZIE-2713
OOZIE-2701  Oozie to support Multiple HCatalog URIs
https://issues.apache.org/jira/browse/OOZIE-2701
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693  SimpleHCatDependencyCache.removeMissingDependency can throw NPE
https://issues.apache.org/jira/browse/OOZIE-2693
OOZIE-2692  Oozie job submit doesn't report error message to user if there is 
any issue with job conf
https://issues.apache.org/jira/browse/OOZIE-2692
OOZIE-2684  Bad database schema error for WF_ACTIONS table
https://issues.apache.org/jira/browse/OOZIE-2684
OOZIE-2681  fix javadoc to compile on JDK8 again
https://issues.apache.org/jira/browse/OOZIE-2681
OOZIE-2670  Upgrade Hbase to 1.2
https://issues.apache.org/jira/browse/OOZIE-2670
OOZIE-2668  Status update and recovery problems when coord action and its 
children not in sync
https://issues.apache.org/jira/browse/OOZIE-2668
OOZIE-2662  DB migration fails if DB is too big

43 matches

Mail list logo