[jira] [Assigned] (OOZIE-3390) shell action's stderr contains a bogus error message (since 5.0.0)

2018-11-27 Thread Julia Kinga Marton (JIRA)


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

Julia Kinga Marton reassigned OOZIE-3390:
-

Assignee: Julia Kinga Marton  (was: Andras Piros)

>  shell action's stderr contains a bogus error message (since 5.0.0)
> ---
>
> Key: OOZIE-3390
> URL: https://issues.apache.org/jira/browse/OOZIE-3390
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Blocker
> Fix For: 5.1.0
>
>
> Shell action's stderr contains an error message about path.
> I executed shell action example to test Oozie 5.1 rc1, the job finished with 
> success, but stderr of the job contained "Path echo doesn't appear to exist".
> https://github.com/apache/oozie/blob/27e4bf1688a6a7750b9c8454de5021337696fd61/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/ShellContentWriter.java#L91
> {code}
> writeLine(errorStream, "Path " + filename + " doesn't appear 
> to exist");
> {code}
> The problem is that we ignore the PATH of the process.



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


[jira] [Updated] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1

2018-11-27 Thread Denes Bodo (JIRA)


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

Denes Bodo updated OOZIE-3120:
--
Attachment: OOZIE-3120-002.patch

> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-3120-001.patch, OOZIE-3120-002.patch
>
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade 
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [  0.972 
> s]
> [INFO] Apache Oozie Client  SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog  SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.872 s
> [INFO] Finished at: 2017-11-10T13:38:17-05:00
> [INFO] Final Memory: 31M/437M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (default-cli) on 
> project oozie-main: No formats specified in the execution parameters or the 
> assembly descriptor. -> [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, Oozie distro creation failed
> {noformat}



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


[jira] [Commented] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1

2018-11-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3120:
--

PreCommit-OOZIE-Build started


> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-3120-001.patch, OOZIE-3120-002.patch
>
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade 
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [  0.972 
> s]
> [INFO] Apache Oozie Client  SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog  SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.872 s
> [INFO] Finished at: 2017-11-10T13:38:17-05:00
> [INFO] Final Memory: 31M/437M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (default-cli) on 
> project oozie-main: No formats specified in the execution parameters or the 
> assembly descriptor. -> [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, Oozie distro creation failed
> {noformat}



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


[jira] [Updated] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Julia Kinga Marton (JIRA)


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

Julia Kinga Marton updated OOZIE-3386:
--
Attachment: OOZIE-3386-002.patch

> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {code}
> The server.log contained the following:
> {code}
> 2018-11-19 15:07:13,244  WARN V1JobsServlet:523 - 
> SERVER[Budapests-MacBook-Pro-10.local] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] URL[POST 
> http://localhost:11000/oozie/v2/jobs?action=start&user=asasvari] 
> error[E0307], E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> org.apache.oozie.servlet.XServletException: E0307: Runtime error 
> [Configuration entry oozie.jobs.api.generated.xml not present]
>at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:172)
>at 
> org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:111)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>at 
> org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:305)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
>at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
>at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
>at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>at org.eclipse.jetty.server.Server.handle(Server.java:534)
>at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
>at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
>at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
>at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)
>at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>a

[jira] [Commented] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3386:
--

PreCommit-OOZIE-Build started


> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {code}
> The server.log contained the following:
> {code}
> 2018-11-19 15:07:13,244  WARN V1JobsServlet:523 - 
> SERVER[Budapests-MacBook-Pro-10.local] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] URL[POST 
> http://localhost:11000/oozie/v2/jobs?action=start&user=asasvari] 
> error[E0307], E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> org.apache.oozie.servlet.XServletException: E0307: Runtime error 
> [Configuration entry oozie.jobs.api.generated.xml not present]
>at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:172)
>at 
> org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:111)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>at 
> org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:305)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
>at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
>at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
>at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>at org.eclipse.jetty.server.Server.handle(Server.java:534)
>at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
>at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
>at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
>at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)
>at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectC

[jira] [Commented] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Julia Kinga Marton (JIRA)


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

Julia Kinga Marton commented on OOZIE-3386:
---

[~andras.piros], I have changed the message as you suggested. Now the error 
message is the following one:

{code:bash}
Error: E0307 : E0307: Runtime error [App directory 
[hdfs://localhost:9000/user/martonjuliakinga/examples10/apps/java-main] does 
not exist and app definition cannot be created because of missing config value 
[oozie.jobs.api.generated.xml]]
{code}

The error code is also changed since in the earlier version was Error: E0504, 
what if specifically for missing app path, but now in our case is something 
more. Besides the missing app path, the app definition content is also missing, 
so the workflow.xml creation is not possible.


> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {code}
> The server.log contained the following:
> {code}
> 2018-11-19 15:07:13,244  WARN V1JobsServlet:523 - 
> SERVER[Budapests-MacBook-Pro-10.local] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] URL[POST 
> http://localhost:11000/oozie/v2/jobs?action=start&user=asasvari] 
> error[E0307], E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> org.apache.oozie.servlet.XServletException: E0307: Runtime error 
> [Configuration entry oozie.jobs.api.generated.xml not present]
>at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:172)
>at 
> org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:111)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>at 
> org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:305)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
>at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
>at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>at 
> org.eclipse.jetty.server.handler.

[jira] [Commented] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-3386:
-

Thanks for the new patch [~kmarton]! +1 (pending Jenkins)

> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {code}
> The server.log contained the following:
> {code}
> 2018-11-19 15:07:13,244  WARN V1JobsServlet:523 - 
> SERVER[Budapests-MacBook-Pro-10.local] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] URL[POST 
> http://localhost:11000/oozie/v2/jobs?action=start&user=asasvari] 
> error[E0307], E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> org.apache.oozie.servlet.XServletException: E0307: Runtime error 
> [Configuration entry oozie.jobs.api.generated.xml not present]
>at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:172)
>at 
> org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:111)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>at 
> org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:305)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
>at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
>at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
>at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>at org.eclipse.jetty.server.Server.handle(Server.java:534)
>at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
>at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
>at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
>at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)
>at 
> org.eclipse.jetty.io.Se

Failed: OOZIE-3120 PreCommit Build #927

2018-11-27 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-3120
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/927/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 2.28 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [fluent-job/fluent-job-api].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[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 [core].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2561 bytes
[TRACE] Full summary file size is 1471 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-3120

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 star imports
+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 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
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 [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +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/distcp].
 +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/git].
 +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 [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
+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: 3075
Tests failed at first run:
TestWorkflowActionRetryInfoXCommand#testRetryConsoleUrlForked
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/927/

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/13117642/comment/16700437","id":"16700437","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 Q

[jira] [Commented] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1

2018-11-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3120:
--


Testing JIRA OOZIE-3120

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 star imports
.{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}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 [sharelib/hive2].
. {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/oozie].
. {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/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/distcp].
. {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/git].
. {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 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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 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: 3075
.{color:orange}Tests failed at first run:{color}
TestWorkflowActionRetryInfoXCommand#testRetryConsoleUrlForked
.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/927/



> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-3120-001.patch, OOZIE-3120-002.patch
>
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade 
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [  0.972 
> s]
> [INFO] Apache Oozie Client  SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog  SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming .

Failed: OOZIE-3386 PreCommit Build #928

2018-11-27 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-3386
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/928/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.85 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[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 [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2561 bytes
[TRACE] Full summary file size is 1471 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-3386

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 star imports
+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 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
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 [sharelib/hive].
 +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 [sharelib/streaming].
 +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/git].
 +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 [fluent-job/fluent-job-api].
 +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 [core].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [tools].
+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: 1607
+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/928/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  32810 0  100  3281  0   4454 --:--:-- --:--:-- --:--:--  
4451{"self":"https://issues.apache.org/jira/rest/api/2/issue/13199547/comment/16700500","id":"16700500","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting

[jira] [Commented] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3386:
--


Testing JIRA OOZIE-3386

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 star imports
.{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}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 [sharelib/hive].
. {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 [sharelib/streaming].
. {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/git].
. {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 
[fluent-job/fluent-job-api].
. {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 [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 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: 1607
{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/928/



> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {code}
> The server.log contained the following:
> {code}
> 2018-11-19 15:07:13,244  WARN V1JobsServlet:523 - 
> SERVER[Budapests-MacBook-Pro-10.local] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] AC

[jira] [Commented] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-3386:
-

The [pre-commit Jenkins 
job|https://builds.apache.org/job/PreCommit-OOZIE-Build/928/consoleFull] failed:
{noformat}
14:52:40 [INFO] 
14:52:40 [INFO] Results:
14:52:40 [INFO] 
14:52:40 [INFO] Tests run: 589, Failures: 0, Errors: 0, Skipped: 0
14:52:40 [INFO] 
14:52:40 [ERROR] There are test failures.
14:52:40 
14:52:40 Please refer to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/core/target/surefire-reports
 for the individual test results.
14:52:40 Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
14:52:40 The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
14:52:40 Command was /bin/sh -c cd 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/core && 
/usr/local/asfpackages/java/jdk1.8.0_191/jre/bin/java -Xmx2048m -da 
-XX:MetaspaceSize=512M -XX:MaxMetaspaceSize=1024M -XX:+CMSClassUnloadingEnabled 
-XX:+UseConcMarkSweepGC -jar 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/core/target/surefire/surefirebooter4402261180471750437.jar
 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/core/target/surefire
 2018-11-27T13-37-04_331-jvmRun1 surefire8557612660307744506tmp 
surefire_41344644475305313520tmp
14:52:40 Error occurred in starting fork, check output in log
14:52:40 Process Exit Code: 255
{noformat}
[~kmarton] can you please have a look?

> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {code}
> The server.log contained the following:
> {code}
> 2018-11-19 15:07:13,244  WARN V1JobsServlet:523 - 
> SERVER[Budapests-MacBook-Pro-10.local] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] URL[POST 
> http://localhost:11000/oozie/v2/jobs?action=start&user=asasvari] 
> error[E0307], E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> org.apache.oozie.servlet.XServletException: E0307: Runtime error 
> [Configuration entry oozie.jobs.api.generated.xml not present]
>at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:172)
>at 
> org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:111)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>at 
> org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:305)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
>at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
>at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
>at 
> org.eclipse.jetty.server.handler.Scop

[jira] [Commented] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Julia Kinga Marton (JIRA)


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

Julia Kinga Marton commented on OOZIE-3386:
---

[~andras.piros] I will kick off another build. I think that the cause is the 
following: 
{code:bash}
14:52:40 Error occurred in starting fork, check output in log. 
{code}
Unfortunately our precommit script is not handling this case right now.

> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {code}
> The server.log contained the following:
> {code}
> 2018-11-19 15:07:13,244  WARN V1JobsServlet:523 - 
> SERVER[Budapests-MacBook-Pro-10.local] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] URL[POST 
> http://localhost:11000/oozie/v2/jobs?action=start&user=asasvari] 
> error[E0307], E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> org.apache.oozie.servlet.XServletException: E0307: Runtime error 
> [Configuration entry oozie.jobs.api.generated.xml not present]
>at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:172)
>at 
> org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:111)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>at 
> org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:305)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
>at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
>at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
>at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>at org.eclipse.jetty.server.Server.handle(Server.java:534)
>at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
>at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
>at 
> org.eclip

[jira] [Commented] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3386:
--

PreCommit-OOZIE-Build started


> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {code}
> The server.log contained the following:
> {code}
> 2018-11-19 15:07:13,244  WARN V1JobsServlet:523 - 
> SERVER[Budapests-MacBook-Pro-10.local] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] URL[POST 
> http://localhost:11000/oozie/v2/jobs?action=start&user=asasvari] 
> error[E0307], E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> org.apache.oozie.servlet.XServletException: E0307: Runtime error 
> [Configuration entry oozie.jobs.api.generated.xml not present]
>at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:172)
>at 
> org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:111)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>at 
> org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:305)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
>at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
>at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
>at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
>at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
>at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
>at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
>at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>at org.eclipse.jetty.server.Server.handle(Server.java:534)
>at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
>at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
>at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
>at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)
>at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectC

Re: Review Request 69330: OOZIE-3379 Auth token cache file name should include Oozie URL

2018-11-27 Thread zhang junfan

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

(Updated 十一月 27, 2018, 3:55 p.m.)


Review request for oozie, András Piros and Peter Bacsko.


Repository: oozie-git


Description
---

Auth token cache file name should include Oozie URL, link to oozie-3379.


Diffs
-

  client/src/main/java/org/apache/oozie/client/AuthOozieClient.java 3a8b5ab6 
  core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
fc9d840b 
  
core/src/test/java/org/apache/oozie/servlet/TestAuthFilterAuthOozieClient.java 
04fde730 


Diff: https://reviews.apache.org/r/69330/diff/1/


Testing
---

I added a test for authOozieClients with the different oozieUrl.
I changed the code for EmbeddedServletContainer. Because this patch needs to 
bind the cache file to oozieUrl, you need to test whether multiple different 
clients can use the cache. In the original EmbeddedServletContainer code, the 
port was random and could not get a given container context path. So the port 
binding needs to be added.


File Attachments (updated)


oozie-3379-6.patch
  
https://reviews.apache.org/media/uploaded/files/2018/11/27/ec465408-bcbc-44bc-a816-7ff73e3c0e68__oozie-3379-6.patch


Thanks,

zhang junfan



Re: Review Request 69330: OOZIE-3379 Auth token cache file name should include Oozie URL

2018-11-27 Thread zhang junfan


> On 十一月 20, 2018, 11:45 a.m., András Piros wrote:
> >

Thanks to András Piros for your comment. I re-uploaded the oozie-3379-6.patch. 
Please review it. Look forward to your reply.


- zhang


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


On 十一月 27, 2018, 3:55 p.m., zhang junfan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69330/
> ---
> 
> (Updated 十一月 27, 2018, 3:55 p.m.)
> 
> 
> Review request for oozie, András Piros and Peter Bacsko.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Auth token cache file name should include Oozie URL, link to oozie-3379.
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/client/AuthOozieClient.java 3a8b5ab6 
>   core/src/main/java/org/apache/oozie/test/EmbeddedServletContainer.java 
> fc9d840b 
>   
> core/src/test/java/org/apache/oozie/servlet/TestAuthFilterAuthOozieClient.java
>  04fde730 
> 
> 
> Diff: https://reviews.apache.org/r/69330/diff/1/
> 
> 
> Testing
> ---
> 
> I added a test for authOozieClients with the different oozieUrl.
> I changed the code for EmbeddedServletContainer. Because this patch needs to 
> bind the cache file to oozieUrl, you need to test whether multiple different 
> clients can use the cache. In the original EmbeddedServletContainer code, the 
> port was random and could not get a given container context path. So the port 
> binding needs to be added.
> 
> 
> File Attachments
> 
> 
> oozie-3379-6.patch
>   
> https://reviews.apache.org/media/uploaded/files/2018/11/27/ec465408-bcbc-44bc-a816-7ff73e3c0e68__oozie-3379-6.patch
> 
> 
> Thanks,
> 
> zhang junfan
> 
>



[jira] [Commented] (OOZIE-3379) Auth token cache file name should include Oozie URL

2018-11-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3379:
--

PreCommit-OOZIE-Build started


> Auth token cache file name should include Oozie URL
> ---
>
> Key: OOZIE-3379
> URL: https://issues.apache.org/jira/browse/OOZIE-3379
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: 5.0.0
>Reporter: Junfan Zhang
>Assignee: Junfan Zhang
>Priority: Major
> Attachments: oozie-3379-1.patch, oozie-3379-2.patch, 
> oozie-3379-3.patch, oozie-3379-4.patch, oozie-3379-5.patch, oozie-3379-6.patch
>
>
> We have a program that uses the oozie client, but when the client connects to 
> multiple clusters,
> the authOozieClient class frequently requests the kdc server because the 
> authentication token cache file is invalid.
> This will cause subsequent requests in our program to be blocked, resulting 
> in unstable services.
> So, oozie client's auth token cache file name should include Oozie URL.



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


[jira] [Updated] (OOZIE-3379) Auth token cache file name should include Oozie URL

2018-11-27 Thread Junfan Zhang (JIRA)


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

Junfan Zhang updated OOZIE-3379:

Attachment: oozie-3379-6.patch

> Auth token cache file name should include Oozie URL
> ---
>
> Key: OOZIE-3379
> URL: https://issues.apache.org/jira/browse/OOZIE-3379
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: 5.0.0
>Reporter: Junfan Zhang
>Assignee: Junfan Zhang
>Priority: Major
> Attachments: oozie-3379-1.patch, oozie-3379-2.patch, 
> oozie-3379-3.patch, oozie-3379-4.patch, oozie-3379-5.patch, oozie-3379-6.patch
>
>
> We have a program that uses the oozie client, but when the client connects to 
> multiple clusters,
> the authOozieClient class frequently requests the kdc server because the 
> authentication token cache file is invalid.
> This will cause subsequent requests in our program to be blocked, resulting 
> in unstable services.
> So, oozie client's auth token cache file name should include Oozie URL.



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


[jira] [Commented] (OOZIE-3379) Auth token cache file name should include Oozie URL

2018-11-27 Thread Junfan Zhang (JIRA)


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

Junfan Zhang commented on OOZIE-3379:
-

Thanks to [~andras.piros] for your review. I re-uploaded the 
oozie-3379-6.patch. Please review it, the ReviewBoard review link is 
[https://reviews.apache.org/r/69330/]

> Auth token cache file name should include Oozie URL
> ---
>
> Key: OOZIE-3379
> URL: https://issues.apache.org/jira/browse/OOZIE-3379
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: 5.0.0
>Reporter: Junfan Zhang
>Assignee: Junfan Zhang
>Priority: Major
> Attachments: oozie-3379-1.patch, oozie-3379-2.patch, 
> oozie-3379-3.patch, oozie-3379-4.patch, oozie-3379-5.patch, oozie-3379-6.patch
>
>
> We have a program that uses the oozie client, but when the client connects to 
> multiple clusters,
> the authOozieClient class frequently requests the kdc server because the 
> authentication token cache file is invalid.
> This will cause subsequent requests in our program to be blocked, resulting 
> in unstable services.
> So, oozie client's auth token cache file name should include Oozie URL.



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


Failed: OOZIE-3386 PreCommit Build #929

2018-11-27 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-3386
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/929/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.90 MB...]
[DEBUG] There are no new bugs found in [fluent-job/fluent-job-api].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[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 [core].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2561 bytes
[TRACE] Full summary file size is 1471 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-3386

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 star imports
+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 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
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 [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +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/distcp].
 +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/git].
 +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 [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
+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: 3075
Tests failed at first run:
TestCoordMaterializeTriggerService#testCoordMaterializeTriggerService3
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/929/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  34800 0  100  3480  0   3880 --:--:-- --:--:-- --:--:--  
3879{"self":"https://issues.apache.org/jira/rest/api/2/issue/13199547/comment/16700658","id":"16700658","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-338

[jira] [Commented] (OOZIE-3386) Misleading error message when workflow application does not exist

2018-11-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3386:
--


Testing JIRA OOZIE-3386

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 star imports
.{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}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 [sharelib/hive2].
. {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/oozie].
. {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/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/distcp].
. {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/git].
. {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 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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 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: 3075
.{color:orange}Tests failed at first run:{color}
TestCoordMaterializeTriggerService#testCoordMaterializeTriggerService3
.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/929/



> Misleading error message when workflow application does not exist
> -
>
> Key: OOZIE-3386
> URL: https://issues.apache.org/jira/browse/OOZIE-3386
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3386-001.patch, OOZIE-3386-002.patch
>
>
> Using 5.1.0 rc1, I tried to run an example workflow. Because of user error 
> {{oozie.wf.application.path}} in job.properties pointed to a directory in 
> HDFS that did not exist. Upon submitting the workflow, the following was 
> returned
> {code}
> bin/oozie job -oozie http://localhost:11000/oozie   -config 
> examples/apps/demo/job.properties -Dmode=client -Dmaster=yarn -run 
> -DnameNode=hdfs://localhost:9000
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Error: E0307 : E0307: Runtime error [Configuration entry 
> oozie.jobs.api.generated.xml not present]
> {

[jira] [Created] (OOZIE-3393) Add Oozie instrumentation delayed metric in CoordMaterializeTriggerService

2018-11-27 Thread Junfan Zhang (JIRA)
Junfan Zhang created OOZIE-3393:
---

 Summary: Add Oozie instrumentation delayed metric in 
CoordMaterializeTriggerService
 Key: OOZIE-3393
 URL: https://issues.apache.org/jira/browse/OOZIE-3393
 Project: Oozie
  Issue Type: Improvement
Reporter: Junfan Zhang
Assignee: Junfan Zhang


We have multiple Oozie scheduled clusters. The problem that is currently 
encountered is that some materialize queues are too late to process during the 
peak hours of the scheduled tasks. We need to get the metrics of the delay 
queue for alarm monitoring and adjust the configuration to optimize.
Currently we have added metrics for queue size and latency in Oozie 
CoordMaterializeTriggerService class, in order to reflect the general trend of 
current scheduling.



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


[jira] [Updated] (OOZIE-3393) Add Oozie instrumentation delayed metric in CoordMaterializeTriggerService

2018-11-27 Thread Junfan Zhang (JIRA)


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

Junfan Zhang updated OOZIE-3393:

Attachment: oozie-3393-1.patch

> Add Oozie instrumentation delayed metric in CoordMaterializeTriggerService
> --
>
> Key: OOZIE-3393
> URL: https://issues.apache.org/jira/browse/OOZIE-3393
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Junfan Zhang
>Assignee: Junfan Zhang
>Priority: Major
> Attachments: oozie-3393-1.patch
>
>
> We have multiple Oozie scheduled clusters. The problem that is currently 
> encountered is that some materialize queues are too late to process during 
> the peak hours of the scheduled tasks. We need to get the metrics of the 
> delay queue for alarm monitoring and adjust the configuration to optimize.
> Currently we have added metrics for queue size and latency in Oozie 
> CoordMaterializeTriggerService class, in order to reflect the general trend 
> of current scheduling.



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


Failed: OOZIE-3379 PreCommit Build #930

2018-11-27 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-3379
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/930/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.85 MB...]
[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 [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[ERROR] There are [1] new bugs found below threshold in total that must be 
fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2968 bytes
[TRACE] Full summary file size is 1879 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-3379

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 star imports
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 2 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
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 [1] new bugs found below threshold in total that must be fixed.
 -1 There are [1] new bugs found below threshold in [client] that must be fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
 The most important FindBugs errors are:
 At AuthOozieClient.java:[line 97]: 
java/io/File.(Ljava/lang/String;Ljava/lang/String;)V reads a file 
whose location might be specified by user input
 At AuthOozieClient.java:[line 96]
 +1 There are no new bugs found in [sharelib/hive].
 +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 [sharelib/streaming].
 +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/git].
 +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 [fluent-job/fluent-job-api].
 +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 [core].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [tools].
+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: 1607
+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/930/

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/13196233/comment/16700727","id":"16700727","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x

[jira] [Commented] (OOZIE-3379) Auth token cache file name should include Oozie URL

2018-11-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3379:
--


Testing JIRA OOZIE-3379

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 star imports
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch 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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}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:red}-1{color} There are [1] new bugs found below threshold in total that 
must be fixed.
. {color:red}-1{color} There are [1] new bugs found below threshold in [client] 
that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
. The most important FindBugs errors are:
. At AuthOozieClient.java:[line 97]: 
java/io/File.(Ljava/lang/String;Ljava/lang/String;)V reads a file 
whose location might be specified by user input
. At AuthOozieClient.java:[line 96]
. {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/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 [sharelib/streaming].
. {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/git].
. {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 
[fluent-job/fluent-job-api].
. {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 [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 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: 1607
{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/930/



> Auth token cache file name should include Oozie URL
> ---
>
> Key: OOZIE-3379
> URL: https://issues.apache.org/jira/browse/OOZIE-3379
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: 5.0.0
>Reporter: Junfan Zhang
>Assignee: Junfan Zhang
>Priority: Major
> Attachments: oozie-3379-1.patch, oozie-3379-2.patch, 
> oozie-3379-3.patch, oozie-3379-4.patch, oozie-3379-5.patch, oozie-3379-6.patch
>
>
> We have a program that uses the oozie client, but when the client connects to 
> multiple clusters,
> the authOozieClient class frequently requests the kdc server because the 
> authentication token cache file is invalid.
> This will cause subsequent requests in our program to be blocked, resulting 
> in unstable services.
> So, oozie client's auth token cache file name should include Oozie URL.



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


[jira] Subscription: Oozie Patch Available

2018-11-27 Thread jira
Issue Subscription
Filter: Oozie Patch Available (98 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3386  Misleading error message when workflow application does not exist
https://issues.apache.org/jira/browse/OOZIE-3386
OOZIE-3384  [tests] 
TestWorkflowActionRetryInfoXCommand#testRetryConsoleUrlForked() is flaky
https://issues.apache.org/jira/browse/OOZIE-3384
OOZIE-3382  Optimize SshActionExecutor's drainBuffers method
https://issues.apache.org/jira/browse/OOZIE-3382
OOZIE-3379  Auth token cache file name should include Oozie URL
https://issues.apache.org/jira/browse/OOZIE-3379
OOZIE-3375  Can't use empty  in coordinator
https://issues.apache.org/jira/browse/OOZIE-3375
OOZIE-3367  Using && in EL expressions in oozie bundle.xml files generates 
parse errors
https://issues.apache.org/jira/browse/OOZIE-3367
OOZIE-3366  Update workflow status and subworkflow status on suspend command
https://issues.apache.org/jira/browse/OOZIE-3366
OOZIE-3364  Rerunning Oozie bundle jobs starts the coordinators in 
indeterminate order
https://issues.apache.org/jira/browse/OOZIE-3364
OOZIE-3362  When killed, SSH action should kill the spawned processes on target 
host
https://issues.apache.org/jira/browse/OOZIE-3362
OOZIE-3326  Sqoop Action should support tez delegation tokens for hive-import
https://issues.apache.org/jira/browse/OOZIE-3326
OOZIE-3320  Oozie ShellAction should support absolute bash file path
https://issues.apache.org/jira/browse/OOZIE-3320
OOZIE-3319  Log SSH action callback error output
https://issues.apache.org/jira/browse/OOZIE-3319
OOZIE-3301  Update NOTICE file
https://issues.apache.org/jira/browse/OOZIE-3301
OOZIE-3274  Remove slf4j
https://issues.apache.org/jira/browse/OOZIE-3274
OOZIE-3266  Coord action rerun support RERUN_SKIP_NODES option
https://issues.apache.org/jira/browse/OOZIE-3266
OOZIE-3265  properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to 
appear together
https://issues.apache.org/jira/browse/OOZIE-3265
OOZIE-3256  refactor OozieCLI class
https://issues.apache.org/jira/browse/OOZIE-3256
OOZIE-3249  [tools] Instrumentation log parser
https://issues.apache.org/jira/browse/OOZIE-3249
OOZIE-3218  Oozie Sqoop action with command splits the select clause into 
multiple parts due to delimiter being space
https://issues.apache.org/jira/browse/OOZIE-3218
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
OOZIE-3196  Authorization: restrict world readability by user
https://issues.apache.org/jira/browse/OOZIE-3196
OOZIE-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3137  Add support for log4j2 in HiveMain
https://issues.apache.org/jira/browse/OOZIE-3137
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3120  maven-assembly-plugin fails when bumped from 2.2.1
https://issues.apache.org/jira/browse/OOZIE-3120
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-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-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
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-2812  Spar