[jira] [Assigned] (OOZIE-3447) Run test case in local : It shows oozie-hsqldb-orm.xml exception

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3447:
-

Assignee: (was: duan xiong)

> Run test case in local : It shows oozie-hsqldb-orm.xml exception
> 
>
> Key: OOZIE-3447
> URL: https://issues.apache.org/jira/browse/OOZIE-3447
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Priority: Major
> Attachments: OOZIE-3447-001.patch
>
>
> {code:java}
> 392 oozie-hsqldb WARN [main] openjpa.Enhance - An exception was thrown while 
> attempting to perform class file transformation on 
> "org/apache/oozie/util/db/ValidateConnectionBean":  nonfatal general error> org.apache.openjpa.util.GeneralException: 
> org.xml.sax.SAXException: 
> file:/D:/IdeaProjects/oozie/core/target/classes/META-INF/oozie-hsqldb-orm.xml 
> [Location: Line: 22, C: 32]: org.xml.sax.SAXParseException; systemId: 
> file:/D:/IdeaProjects/oozie/core/target/classes/META-INF/oozie-hsqldb-orm.xml;
>  lineNumber: 22; columnNumber: 32; cvc-complex-type.3.1: Value '1.0' of 
> attribute 'version' of element 'entity-mappings' is not valid with respect to 
> the corresponding attribute use. Attribute 'version' has a fixed value of 
> '2.0'.
> at 
> org.apache.openjpa.persistence.PersistenceMetaDataFactory.parseXML(PersistenceMetaDataFactory.java:294)
> at 
> org.apache.openjpa.persistence.PersistenceMetaDataFactory.load(PersistenceMetaDataFactory.java:227)
> at 
> org.apache.openjpa.meta.MetaDataRepository.getMetaDataInternal(MetaDataRepository.java:587)
> at 
> org.apache.openjpa.meta.MetaDataRepository.getMetaDataInternal(MetaDataRepository.java:397)
> at 
> org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:389)
> at org.apache.openjpa.enhance.PCEnhancer.(PCEnhancer.java:286)
> at org.apache.openjpa.enhance.PCEnhancer.(PCEnhancer.java:257)
> Caused by: java.io.IOException: org.xml.sax.SAXException: 
> file:oozie-hsqldb-orm.xml [Location: Line: 22, C: 32]: 
> org.xml.sax.SAXParseException; systemId: file:oozie-hsqldb-orm.xml; 
> lineNumber: 22; columnNumber: 32; cvc-complex-type.3.1: Value '1.0' of 
> attribute 'version' of element 'entity-mappings' is not valid with respect to 
> the corresponding attribute use. Attribute 'version' has a fixed value of 
> '2.0'.
> at 
> org.apache.openjpa.lib.meta.XMLMetaDataParser.parseNewResource(XMLMetaDataParser.java:426)
> at 
> org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:346)
> at 
> org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:323)
> at 
> org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:296)
> at 
> org.apache.openjpa.persistence.XMLPersistenceMetaDataParser.parse(XMLPersistenceMetaDataParser.java:406)
> at 
> org.apache.openjpa.persistence.PersistenceMetaDataFactory.parseXML(PersistenceMetaDataFactory.java:292)
> ... 58 more
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OOZIE-3461) CoordMaterializeTriggerService code cleanup

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3461:
-

Assignee: (was: duan xiong)

> CoordMaterializeTriggerService code cleanup
> ---
>
> Key: OOZIE-3461
> URL: https://issues.apache.org/jira/browse/OOZIE-3461
> Project: Oozie
>  Issue Type: Task
>Reporter: Andras Salamon
>Priority: Minor
> Attachments: OOZIE-3461-001.patch
>
>
> It seems to me don't really use the {{delayedCallables}} and {{delay}} 
> variables in 
> {{CoordMaterializeTriggerService.CoordMaterializeTriggerRunnable}} class. We 
> only add items to {{callables}} and not to {{delayedCallables}}. We could 
> remove this part of the class.
> It should be also useful to log the lock acquiring and not only the releasing 
> ( like in 
> [PauseTransitService|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/PauseTransitService.java#L86]
>  )
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OOZIE-3413) Cannot start Oozie Web UI after deleting /tmp/embedded-jetty-jsp

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3413:
-

Assignee: (was: duan xiong)

> Cannot start Oozie Web UI after deleting /tmp/embedded-jetty-jsp
> 
>
> Key: OOZIE-3413
> URL: https://issues.apache.org/jira/browse/OOZIE-3413
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Priority: Major
>
> After the following steps:
>  # Restart oozie server using {{oozied.sh}}
>  # {{rm -rf /tmp/embedded-jetty-jsp}}
>  # Open the Oozie Web UI in a browser: {{[http://localhost:11000/oozie/]}}
> Oozie Web UI does not start, it gives the following error message:
> {noformat}
> {
>   "errorMessage": "org.apache.jasper.JasperException: 
> java.lang.ClassNotFoundException: org.apache.jsp.index_jsp",
>   "httpStatusCode": 500
> }{noformat}
> jetty.log contains the following error message:
> {noformat}
> 2018-12-28 10:16:19,630  WARN ServletHandler:624 - 
> org.apache.jasper.JasperException: java.lang.ClassNotFoundException: 
> org.apache.jsp.index_jsp
> at 
> org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:176)
> at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
> at 
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)
> at 
> org.eclipse.jetty.jsp.JettyJspServlet.service(JettyJspServlet.java:112)
> 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:566)
> 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.Dispatcher.forward(Dispatcher.java:199)
> at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:74)
> at 
> org.eclipse.jetty.servlet.DefaultServlet.sendWelcome(DefaultServlet.java:599)
> at 
> org.eclipse.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:484)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> 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.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.jett

[jira] [Assigned] (OOZIE-3454) Fix oozie-setup.sh usage information

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3454:
-

Assignee: (was: duan xiong)

> Fix oozie-setup.sh usage information
> 
>
> Key: OOZIE-3454
> URL: https://issues.apache.org/jira/browse/OOZIE-3454
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Priority: Minor
>
> This is the usage information of {{oozie-setup.sh}}:
> {noformat}
> Usage  : oozie-setup.sh 
>   sharelib create -fs FS_URI [-locallib SHARED_LIBRARY] [-concurrency 
> CONCURRENCY]
> (create 
> sharelib for oozie,
> FS_URI is the 
> fs.default.name
> for hdfs uri; 
> SHARED_LIBRARY, path to the
> Oozie 
> sharelib to install, it can be a tarball
> or an 
> expanded version of it. If omitted,
> the Oozie 
> sharelib tarball from the Oozie
> installation 
> directory will be used.
> CONCURRENCY 
> is a number of threads to be used
> for copy 
> operations.
> By default 1 
> thread will be used)
> (action fails 
> if sharelib is already installed
> in HDFS)
>   sharelib upgrade -fs FS_URI [-locallib SHARED_LIBRARY] 
> ([deprecated][use create command to create new version]
>   upgrade 
> existing sharelib, fails if there
>   is no 
> existing sharelib installed in HDFS)
>   db create|upgrade|postupgrade -run [-sqlfile ] (create, 
> upgrade or postupgrade oozie db with an
> optional sql 
> File)
>   export  exports the 
> oozie database to the specified
> file in zip 
> format
>   import  imports the 
> oozie database from the zip file
> created by 
> export
>   (without options prints this usage information)
>  EXTJS can be downloaded from http://www.extjs.com/learn/Ext_Version_Archives
> {noformat}
> It sounds logical that without options the script prints of the usage 
> information, but this is not true:
> {noformat}
>  $ oozie-setup.sh
> INFO: Oozie webconsole disabled, ExtJS library not specified
> INFO: Oozie is ready to be started
> {noformat}
> Checking the source code also shows that in this case it will 
> [call|https://github.com/apache/oozie/blob/master/distro/src/main/bin/oozie-setup.sh#L249-L251]
>  the prepare_jetty part of the script. It only prints out the usage 
> information if we add an invalid option.
> Since calling the script without options is the only way to access the 
> prepare_jetty part and we want to keep the script compatible with the earlier 
> versions, probably we could just delete this sentence.
> The "EXTJS can be downloaded" part is also obsolete, it cannot be downloaded 
> from the link. I'm afraid this version is so old, it cannot be downloaded 
> from the official website anymore. This [stackoverflow 
> answer|https://stackoverflow.com/a/49298186/21348] suggests to download it 
> from the cloudera archive, but I'm not sure if it's a good idea to put that 
> link into the opensource Oozie.
> If we fix this, we also need to fix the 
> [documentation|https://oozie.apache.org/docs/5.1.0/AG_Install.html], since it 
> also contains the usage information.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OOZIE-3449) Make spark-2 as the default profile

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3449:
-

Assignee: (was: duan xiong)

> Make spark-2 as the default profile
> ---
>
> Key: OOZIE-3449
> URL: https://issues.apache.org/jira/browse/OOZIE-3449
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: trunk
>Reporter: Andras Salamon
>Priority: Major
> Fix For: 6.0
>
> Attachments: OOZIE-3449-001.patch
>
>
> OOZIE-2606 introduced spark-1 and spark-2 profiles more than 2 years ago. 
> Right now spark-1 profile is the default. I think it's time to make the 
> spark-2 profile as default.
> We need to check the unit tests and the demos before we change the default.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OOZIE-3512) Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3512:
-

Assignee: (was: duan xiong)

> Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA
> --
>
> Key: OOZIE-3512
> URL: https://issues.apache.org/jira/browse/OOZIE-3512
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: trunk
>Reporter: Andras Salamon
>Priority: Major
>
> {{TestActionStartXCommand.testActionWithEscapedStringAndCDATA}} is flaky, 
> sometimes (for instance: 
> https://issues.apache.org/jira/browse/OOZIE-3470?focusedCommentId=16817901&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16817901
>  ) it fails with the following error message:
> {noformat}junit.framework.AssertionFailedError: YARN App state for app 
> application_1559489642789_0018 expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> org.apache.oozie.test.XTestCase.waitUntilYarnAppDoneAndAssertSuccess(XTestCase.java:1358)
>   at 
> org.apache.oozie.command.wf.TestActionStartXCommand.testActionWithEscapedStringAndCDATA(TestActionStartXCommand.java:235)
> ...
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


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

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-2338:
-

Assignee: (was: duan xiong)

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



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OOZIE-3532) Confusing E1603 error message

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3532:
-

Assignee: (was: duan xiong)

> Confusing E1603 error message
> -
>
> Key: OOZIE-3532
> URL: https://issues.apache.org/jira/browse/OOZIE-3532
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Priority: Minor
>
> If we specify an invalid namenode for Oozie we get a useful error message:
> {noformat}
> Error message: E0901: NameNode [localhost:8020] not allowed, not in Oozie's 
> whitelist. Allowed values are: [machinename.com:8020]]{noformat}
> If we accidentally specify {{-DnameNode=hdfs:machinename.com:8020}} instead 
> of {{-DnameNode=hdfs://machinename.com:8020}} we get a very confusing error 
> message:
> {noformat}
> Error: E1603 : Can not create a Path from a null string{noformat}
> Checking the logs also not very helpful:
> {noformat}
> java.lang.IllegalArgumentException: Can not create a Path from a null string
> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:164)
> at org.apache.hadoop.fs.Path.(Path.java:180)
> at 
> org.apache.oozie.servlet.V1JobsServlet.existsOnDFS(V1JobsServlet.java:213)
> at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:162)
> 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:308)
> 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:1780)
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:644)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:592)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at 
> org.apache.oozie.servlet.HttpResponseHeaderFilter.doFilter(HttpResponseHeaderFilter.java:68)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> 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:513)
> 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:539)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)
> 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)
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
> at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
> 

[jira] [Assigned] (OOZIE-3565) Spark example fails with the default setting

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3565:
-

Assignee: (was: duan xiong)

> Spark example fails with the default setting
> 
>
> Key: OOZIE-3565
> URL: https://issues.apache.org/jira/browse/OOZIE-3565
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.2.0
>Reporter: Andras Salamon
>Priority: Major
>
> Spark 1 example with default settings (local mode) fails
> {noformat}
> $ bin/oozie job -oozie [http://localhost:11000/oozie] -config 
> examples/apps/spark/job.properties -run -DnameNode=hdfs://localhost:9000 
> -DjobTracker=localhost:8032
> Error: --deploy-mode must be either "client" or "cluster"
>  {noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3568:
-

Assignee: (was: duan xiong)

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, 
> OOZIE-3568-003.patch, OOZIE-3568-004.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OOZIE-2458) 'oozie-setup.sh sharelib create' should ensure uploaded jars are world readable

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-2458:
-

Assignee: (was: duan xiong)

> 'oozie-setup.sh sharelib create' should ensure uploaded jars are world 
> readable
> ---
>
> Key: OOZIE-2458
> URL: https://issues.apache.org/jira/browse/OOZIE-2458
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 4.1.0
>Reporter: Ferenc Denes
>Priority: Critical
> Attachments: OOZIE-2458-1.patch
>
>
> If the default umask of HDFS does not include world read then the Oozie 
> sharelib gets created accordingly, and then the jars can not be read at 
> runtime because Oozie workflows impersonate the submitting user.
> The 'oozie-setup.sh sharelib create' command should ensure that the installed 
> jars are world readable.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (OOZIE-3560) IDEA shows have some error in index.jsp

2021-11-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3560:
-

Assignee: (was: duan xiong)

> IDEA shows have some error  in index.jsp
> 
>
> Key: OOZIE-3560
> URL: https://issues.apache.org/jira/browse/OOZIE-3560
> Project: Oozie
>  Issue Type: Bug
>  Components: ui
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3560-001.patch
>
>
> :
> :
>  style="width:1048">:
>  
> Mismatched property value ( |   |  
>   | | 
> *{color:#ff6464}[initial | inherit | unset | revert]{color}*) 
> Inspection info: This inspection detects illegal property's values.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2020-02-24 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3568:
---

[~kmarton], I have try this parameter, It can't work.Can we use two patch for 
this issue?

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, 
> OOZIE-3568-003.patch, OOZIE-3568-004.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-27 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3568:
---

[~asalamon74],Hi . I can't make a correct patch for this issue, this git diff 
parameter can't work. I have try a lot times,It all doesn't work

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, 
> OOZIE-3568-003.patch, OOZIE-3568-004.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-18 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3568:
---

[~asalamon74]. Hi, I think this patch is good. Maybe this patch can't handle 
rename file correct? So can you tell me how to make a right patch for this 
issue? Thank you very much.

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, 
> OOZIE-3568-003.patch, OOZIE-3568-004.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-18 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3568:
--
Attachment: OOZIE-3568-004.patch

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, 
> OOZIE-3568-003.patch, OOZIE-3568-004.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-14 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3568:
--
Attachment: OOZIE-3568-003.patch

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch, 
> OOZIE-3568-003.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-14 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3568:
---

[~asalamon74],Hi,I have checked the test classes and you are right,This class 
have a misleading name,I have changed This class name to the right meaning.

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-11 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3568:
---

 

[~kmarton] ,Hi. Can you help me confirm this issue is a problem or not? Why we 
delete this class before? Maybe we need to delete this class's test class

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-08 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3568:
--
Description: 
Have large amount of log information “WARN messages [main] openjpa.MetaData” in 
jetty.out need to clean:

some not exists class need to enhanced in openjpa:

org.apache.oozie.client.rest.JsonWorkflowJob
 org.apache.oozie.client.rest.JsonWorkflowAction
 org.apache.oozie.client.rest.JsonCoordinatorJob
 org.apache.oozie.client.rest.JsonCoordinatorAction
 org.apache.oozie.client.rest.JsonBundleJob

for example:

 

3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
"org.apache.oozie.client.rest.JsonBundleJob" listed in the 
openjpa.MetaDataFactory configuration property could not be loaded by 
sun.misc.Launcher$AppClassLoader@33909752; ignoring.
3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
"org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
openjpa.MetaDataFactory configuration property could not be loaded by 
sun.misc.Launcher$AppClassLoader@33909752; ignoring.
3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
"org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
openjpa.MetaDataFactory configuration property could not be loaded by 
sun.misc.Launcher$AppClassLoader@33909752; ignoring.
3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
"org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
openjpa.MetaDataFactory configuration property could not be loaded by 
sun.misc.Launcher$AppClassLoader@33909752; ignoring.
3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
"org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
openjpa.MetaDataFactory configuration property could not be loaded by 
sun.misc.Launcher$AppClassLoader@33909752; ignoring.

 

  was:
Have large amount of log information “WARN messages [main] openjpa.MetaData” in 
jetty.log need to clean:

some not exists class need to enhanced in openjpa:

org.apache.oozie.client.rest.JsonWorkflowJob
org.apache.oozie.client.rest.JsonWorkflowAction
org.apache.oozie.client.rest.JsonCoordinatorJob
org.apache.oozie.client.rest.JsonCoordinatorAction
org.apache.oozie.client.rest.JsonBundleJob


> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.out need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
>  org.apache.oozie.client.rest.JsonWorkflowAction
>  org.apache.oozie.client.rest.JsonCoordinatorJob
>  org.apache.oozie.client.rest.JsonCoordinatorAction
>  org.apache.oozie.client.rest.JsonBundleJob
> for example:
>  
> 3493 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonBundleJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3494 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowJob" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3495 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonWorkflowAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
> 3496 oozie-postgresql WARN [main] openjpa.MetaData - The class 
> "org.apache.oozie.client.rest.JsonCoordinatorAction" listed in the 
> openjpa.MetaDataFactory configuration property could not be loaded by 
> sun.misc.Launcher$AppClassLoader@33909752; ignoring.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-07 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3568:
--
Attachment: OOZIE-3568-002.patch

> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean
> ---
>
> Key: OOZIE-3568
> URL: https://issues.apache.org/jira/browse/OOZIE-3568
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3568-001.patch, OOZIE-3568-002.patch
>
>
> Have large amount of log information “WARN messages [main] openjpa.MetaData” 
> in jetty.log need to clean:
> some not exists class need to enhanced in openjpa:
> org.apache.oozie.client.rest.JsonWorkflowJob
> org.apache.oozie.client.rest.JsonWorkflowAction
> org.apache.oozie.client.rest.JsonCoordinatorJob
> org.apache.oozie.client.rest.JsonCoordinatorAction
> org.apache.oozie.client.rest.JsonBundleJob



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (OOZIE-3568) Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean

2019-12-07 Thread duan xiong (Jira)
duan xiong created OOZIE-3568:
-

 Summary: Have large amount of log information “WARN messages 
[main] openjpa.MetaData” in jetty.log need to clean
 Key: OOZIE-3568
 URL: https://issues.apache.org/jira/browse/OOZIE-3568
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: 5.1.0
Reporter: duan xiong
Assignee: duan xiong
 Fix For: 5.2.0


Have large amount of log information “WARN messages [main] openjpa.MetaData” in 
jetty.log need to clean:

some not exists class need to enhanced in openjpa:

org.apache.oozie.client.rest.JsonWorkflowJob
org.apache.oozie.client.rest.JsonWorkflowAction
org.apache.oozie.client.rest.JsonCoordinatorJob
org.apache.oozie.client.rest.JsonCoordinatorAction
org.apache.oozie.client.rest.JsonBundleJob



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (OOZIE-3565) Spark example fails with the default setting

2019-12-05 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3565:
-

Assignee: duan xiong

> Spark example fails with the default setting
> 
>
> Key: OOZIE-3565
> URL: https://issues.apache.org/jira/browse/OOZIE-3565
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.2.0
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> Spark 1 example with default settings (local mode) fails
> {noformat}
> $ bin/oozie job -oozie [http://localhost:11000/oozie] -config 
> examples/apps/spark/job.properties -run -DnameNode=hdfs://localhost:9000 
> -DjobTracker=localhost:8032
> Error: --deploy-mode must be either "client" or "cluster"
>  {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-12-04 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3538:
---

[~asalamon74]. Hi. After [~hadoopqa] the test. Just modify this value to 
false,Then this work is very slow. So I just change 1 to true.

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch, OOZIE-3538-002.patch, 
> OOZIE-3538-003.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-12-04 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3538:
--
Attachment: OOZIE-3538-003.patch

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch, OOZIE-3538-002.patch, 
> OOZIE-3538-003.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-12-02 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3538:
---

[~asalamon74],Hi. I am sorry for can't test this patch in local.So I upload the 
patch want to test by [~hadoopqa].

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch, OOZIE-3538-002.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-12-02 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3538:
--
Attachment: OOZIE-3538-002.patch

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch, OOZIE-3538-002.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-11-19 Thread duan xiong (Jira)


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

duan xiong edited comment on OOZIE-3538 at 11/19/19 11:28 PM:
--

[~asalamon74], I have delete it, Because have some problem.Then I want to 
confirm one thing with you . I have  run to “mvn  clean test" in local right ? 
Because I run this order in oozie-master can't success. It failed shows "Failed 
to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test 
*(default-test)* on project oozie-core: *There was a timeout or other error in 
the fork" in module oozie-core.* Then I run "bin/test-patch 
--patch=../OOZIE--001.patch --reset-scm --tasks=TESTS"  have error I will 
check that.


was (Author: nobigo):
[~asalamon74], I have delete it, Because have some problem.Then I want to 
confirm one thing with you . I have  run to “mvn  clean test" in local right ? 
Because I run this order in oozie-master can't success. It failed shows "Failed 
to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test 
*(default-test)* on project oozie-core: *There was a timeout or other error in 
the fork" in module oozie-core*

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-11-19 Thread duan xiong (Jira)


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

duan xiong edited comment on OOZIE-3538 at 11/19/19 2:08 PM:
-

[~asalamon74], I have delete it, Because have some problem.Then I want to 
confirm one thing with you . I have  run to “mvn  clean test" in local right ? 
Because I run this order in oozie-master can't success. It failed shows "Failed 
to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test 
*(default-test)* on project oozie-core: *There was a timeout or other error in 
the fork" in module oozie-core*


was (Author: nobigo):
[~asalamon74], I have delete it, Because have some problem.Then I want to 
confirm one thing with you . I have  run to “mvn  clean test" in local right ? 
Because I run this order in oozie-master can't success.

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-11-18 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3538:
---

[~asalamon74], I have delete it, Because have some problem.Then I want to 
confirm one thing with you . I have  run to “mvn  clean test" in local right ? 
Because I run this order in oozie-master can't success.

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (OOZIE-3560) IDEA shows have some error in index.jsp

2019-11-17 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3560:
-

Assignee: duan xiong

> IDEA shows have some error  in index.jsp
> 
>
> Key: OOZIE-3560
> URL: https://issues.apache.org/jira/browse/OOZIE-3560
> Project: Oozie
>  Issue Type: Bug
>  Components: ui
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
>
> :
> :
>  style="width:1048">:
>  
> Mismatched property value ( |   |  
>   | | 
> *{color:#ff6464}[initial | inherit | unset | revert]{color}*) 
> Inspection info: This inspection detects illegal property's values.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (OOZIE-3560) IDEA shows have some error in index.jsp

2019-11-17 Thread duan xiong (Jira)
duan xiong created OOZIE-3560:
-

 Summary: IDEA shows have some error  in index.jsp
 Key: OOZIE-3560
 URL: https://issues.apache.org/jira/browse/OOZIE-3560
 Project: Oozie
  Issue Type: Bug
  Components: ui
Affects Versions: 5.1.0
Reporter: duan xiong
 Fix For: 5.3.0


:

:

:

 

Mismatched property value ( |   |  
  | | 
*{color:#ff6464}[initial | inherit | unset | revert]{color}*) 

Inspection info: This inspection detects illegal property's values.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-11-16 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3538:
--
Attachment: (was: OOZIE-3538-002.patch)

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-11-16 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3538:
--
Attachment: OOZIE-3538-002.patch

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch, OOZIE-3538-002.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3558) [Java 11] Compile error for Java 11, Linux, Hadoop 2.6

2019-11-14 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3558:
---

[~asalamon74], I have this problem, too. I just delete it.It can compile 
success,But I use -Dmaven.test.skip=true, So I will test this again.

> [Java 11] Compile error for Java 11, Linux, Hadoop 2.6
> --
>
> Key: OOZIE-3558
> URL: https://issues.apache.org/jira/browse/OOZIE-3558
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.1.0, 5.2.0
>Reporter: Andras Salamon
>Priority: Major
>
> Compiling Oozie  with Java 11 + Linux + Hadoop 2.6 gives the following error:
> {noformat}
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Oozie Main 5.3.0-SNAPSHOT ... SUCCESS [  1.771 
> s]
> [INFO] Apache Oozie Fluent Job  SUCCESS [  0.090 
> s]
> [INFO] Apache Oozie Fluent Job API  FAILURE [  0.363 
> 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 Git . 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 Fluent Job Client . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests 5.3.0-SNAPSHOT SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 4.424 s
> [INFO] Finished at: 2019-11-14T01:26:37-08:00
> [INFO] 
> 
> [ERROR] Failed to execute goal on project oozie-fluent-job-api: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-fluent-job-api:jar:5.3.0-SNAPSHOT: Could not find 
> artifact jdk.tools:jdk.tools:jar:1.6 at specified path 
> /home/systest/jdk-11.0.2/../lib/tools.jar -> [Help 1] {noformat}
> * I have tested several hadoop versions, all hadoop 2.6.x versions are 
> affected, but Oozie compiles correctly if I specify hadoop 2.7.0
> * Quite strange, but I only got the error message if I use Linux. It compiles 
> correctly if I compile Oozie using a Mac.
> * Using Java 10 instead of Java 11 gives the same error.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-11-14 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3538:
--
Attachment: OOZIE-3538-001.patch

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3538-001.patch
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3559) When use IDEA compile the whole project,the fluent-job-api generate code encoding is wrong

2019-11-14 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3559:
--
Attachment: OOZIE-3559-001.patch

> When use IDEA compile the whole project,the fluent-job-api generate code 
> encoding is wrong
> --
>
> Key: OOZIE-3559
> URL: https://issues.apache.org/jira/browse/OOZIE-3559
> Project: Oozie
>  Issue Type: Bug
>  Components: fluent-job
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3559-001.patch, errorInfo.PNG
>
>
> This is the info:    "Error:(2,4) java: 编码UTF-8的不可映射字符"
> !errorInfo.PNG!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (OOZIE-3559) When use IDEA compile the whole project,the fluent-job-api generate code encoding is wrong

2019-11-14 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3559:
-

Assignee: duan xiong

> When use IDEA compile the whole project,the fluent-job-api generate code 
> encoding is wrong
> --
>
> Key: OOZIE-3559
> URL: https://issues.apache.org/jira/browse/OOZIE-3559
> Project: Oozie
>  Issue Type: Bug
>  Components: fluent-job
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: errorInfo.PNG
>
>
> This is the info:    "Error:(2,4) java: 编码UTF-8的不可映射字符"
> !errorInfo.PNG!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (OOZIE-3559) When use IDEA compile the whole project,the fluent-job-api generate code encoding is wrong

2019-11-14 Thread duan xiong (Jira)
duan xiong created OOZIE-3559:
-

 Summary: When use IDEA compile the whole project,the 
fluent-job-api generate code encoding is wrong
 Key: OOZIE-3559
 URL: https://issues.apache.org/jira/browse/OOZIE-3559
 Project: Oozie
  Issue Type: Bug
  Components: fluent-job
Affects Versions: 5.1.0
Reporter: duan xiong
 Fix For: 5.3.0
 Attachments: errorInfo.PNG

This is the info:    "Error:(2,4) java: 编码UTF-8的不可映射字符"

!errorInfo.PNG!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3558) [Java 11] Compile error for Java 11, Linux, Hadoop 2.6

2019-11-14 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3558:
---

[~asalamon74],Hi,I have compile this oozie 5.1.0 in jdk11. So can you please 
share the error message.

> [Java 11] Compile error for Java 11, Linux, Hadoop 2.6
> --
>
> Key: OOZIE-3558
> URL: https://issues.apache.org/jira/browse/OOZIE-3558
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.1.0, 5.2.0
>Reporter: Andras Salamon
>Priority: Major
>
> Compiling Oozie  with Java 11 + Linux + Hadoop 2.6 gives the following error:
> {noformat}
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Oozie Main 5.3.0-SNAPSHOT ... SUCCESS [  1.771 
> s]
> [INFO] Apache Oozie Fluent Job  SUCCESS [  0.090 
> s]
> [INFO] Apache Oozie Fluent Job API  FAILURE [  0.363 
> 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 Git . 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 Fluent Job Client . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests 5.3.0-SNAPSHOT SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 4.424 s
> [INFO] Finished at: 2019-11-14T01:26:37-08:00
> [INFO] 
> 
> [ERROR] Failed to execute goal on project oozie-fluent-job-api: Could not 
> resolve dependencies for project 
> org.apache.oozie:oozie-fluent-job-api:jar:5.3.0-SNAPSHOT: Could not find 
> artifact jdk.tools:jdk.tools:jar:1.6 at specified path 
> /home/systest/jdk-11.0.2/../lib/tools.jar -> [Help 1] {noformat}
> * I have tested several hadoop versions, all hadoop 2.6.x versions are 
> affected, but Oozie compiles correctly if I specify hadoop 2.7.0
> * Quite strange, but I only got the error message if I use Linux. It compiles 
> correctly if I compile Oozie using a Mac.
> * Using Java 10 instead of Java 11 gives the same error.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-11-13 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3536:
--
Attachment: OOZIE-3536-002.patch

> oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade version caused 
> configuration can't find the Tag 
> --
>
> Key: OOZIE-3536
> URL: https://issues.apache.org/jira/browse/OOZIE-3536
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: trunk, 5.1.0, 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3536-001.patch, OOZIE-3536-002.patch, 捕获.PNG
>
>
> oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
> configuration can't find the Tag . In early version 
> 2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-11-12 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3536:
---

[~asalamon74] ,Can you help me review this? Thanks. If you think this is does't 
matter,I will close it. 

> oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade version caused 
> configuration can't find the Tag 
> --
>
> Key: OOZIE-3536
> URL: https://issues.apache.org/jira/browse/OOZIE-3536
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: trunk, 5.1.0, 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3536-001.patch, 捕获.PNG
>
>
> oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
> configuration can't find the Tag . In early version 
> 2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-11-09 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3536:
---

[~kmarton], This succeeds,But I find this issue in IDEA.In Idea this place have 
some error.

!捕获.PNG!

> oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade version caused 
> configuration can't find the Tag 
> --
>
> Key: OOZIE-3536
> URL: https://issues.apache.org/jira/browse/OOZIE-3536
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: trunk, 5.1.0, 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3536-001.patch, 捕获.PNG
>
>
> oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
> configuration can't find the Tag . In early version 
> 2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-11-09 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3536:
--
Attachment: 捕获.PNG

> oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade version caused 
> configuration can't find the Tag 
> --
>
> Key: OOZIE-3536
> URL: https://issues.apache.org/jira/browse/OOZIE-3536
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: trunk, 5.1.0, 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.3.0
>
> Attachments: OOZIE-3536-001.patch, 捕获.PNG
>
>
> oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
> configuration can't find the Tag . In early version 
> 2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-08-26 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3536:
---

[~asalamon74],Can you help me review this? Thanks.

> oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade version caused 
> configuration can't find the Tag 
> --
>
> Key: OOZIE-3536
> URL: https://issues.apache.org/jira/browse/OOZIE-3536
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: trunk, 5.1.0, 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3536-001.patch
>
>
> oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
> configuration can't find the Tag . In early version 
> 2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OOZIE-3537) When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects and findbugsXmlWithMessages can't find

2019-08-23 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3537:
---

In the new 5.2.0 version. the tag findbugsXmlWithMessages  has been delete. But 
the excludeSubProjects tag still exists

> When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects 
> and findbugsXmlWithMessages can't find
> 
>
> Key: OOZIE-3537
> URL: https://issues.apache.org/jira/browse/OOZIE-3537
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0, 5.1.0
>Reporter: duan xiong
>Priority: Major
>
> When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects 
> and findbugsXmlWithMessages can't find.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-08-23 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3538:
-

Assignee: duan xiong

> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong
> --
>
> Key: OOZIE-3538
> URL: https://issues.apache.org/jira/browse/OOZIE-3538
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.2.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
>
> oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
>  value is wrong. That value should be boolean not number. 
> " the parameter {{threadCount}} can be used with the optional parameter 
> {{perCoreThreadCount=true}} (true by default)"  can find this in 
> [http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (OOZIE-3538) oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong

2019-08-23 Thread duan xiong (Jira)
duan xiong created OOZIE-3538:
-

 Summary: oozie-main(pom.xml) plugin maven-surefire-plugin 
configuration the Tag  value is wrong
 Key: OOZIE-3538
 URL: https://issues.apache.org/jira/browse/OOZIE-3538
 Project: Oozie
  Issue Type: Bug
  Components: build
Affects Versions: 5.2.0
Reporter: duan xiong
 Fix For: 5.2.0


oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag 
 value is wrong. That value should be boolean not number. " 
the parameter {{threadCount}} can be used with the optional parameter 
{{perCoreThreadCount=true}} (true by default)"  can find this in 
[http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-08-23 Thread duan xiong (Jira)


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

duan xiong updated OOZIE-3536:
--
Attachment: OOZIE-3536-001.patch

> oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade version caused 
> configuration can't find the Tag 
> --
>
> Key: OOZIE-3536
> URL: https://issues.apache.org/jira/browse/OOZIE-3536
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3536-001.patch
>
>
> oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
> configuration can't find the Tag . In early version 
> 2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OOZIE-3537) When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects and findbugsXmlWithMessages can't find

2019-08-23 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3537:
---

[~asalamon74], May be the new 5.2.0 version because finished the findbugs -> 
spotbugs transition have not this problem.But in the old version this problem 
is still exists?

> When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects 
> and findbugsXmlWithMessages can't find
> 
>
> Key: OOZIE-3537
> URL: https://issues.apache.org/jira/browse/OOZIE-3537
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0, 5.1.0
>Reporter: duan xiong
>Priority: Major
>
> When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects 
> and findbugsXmlWithMessages can't find.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OOZIE-3537) When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects and findbugsXmlWithMessages can't find

2019-08-22 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3537:
---

May be we should change this findbugs-maven-plugin version to 3.0.1?

> When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects 
> and findbugsXmlWithMessages can't find
> 
>
> Key: OOZIE-3537
> URL: https://issues.apache.org/jira/browse/OOZIE-3537
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0, 5.1.0
>Reporter: duan xiong
>Priority: Major
>
> When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects 
> and findbugsXmlWithMessages can't find.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (OOZIE-3537) When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects and findbugsXmlWithMessages can't find

2019-08-22 Thread duan xiong (Jira)
duan xiong created OOZIE-3537:
-

 Summary: When use findbugs-maven-plugin in pom.xml(oozie-main), 
tag excludeSubProjects and findbugsXmlWithMessages can't find
 Key: OOZIE-3537
 URL: https://issues.apache.org/jira/browse/OOZIE-3537
 Project: Oozie
  Issue Type: Bug
  Components: build
Affects Versions: 5.1.0, 5.0.0
Reporter: duan xiong


When use findbugs-maven-plugin in pom.xml(oozie-main), tag excludeSubProjects 
and findbugsXmlWithMessages can't find.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-08-22 Thread duan xiong (Jira)


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

duan xiong commented on OOZIE-3536:
---

may be can find the problem in here: 
[https://stackoverflow.com/questions/52547306/maven-javadoc-plugin-not-accepting-additionalparam-xdoclintnone-additionalpa?r=SearchResults]

> oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade version caused 
> configuration can't find the Tag 
> --
>
> Key: OOZIE-3536
> URL: https://issues.apache.org/jira/browse/OOZIE-3536
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
>
> oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
> configuration can't find the Tag . In early version 
> 2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-08-22 Thread duan xiong (Jira)


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

duan xiong reassigned OOZIE-3536:
-

Assignee: duan xiong

> oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade version caused 
> configuration can't find the Tag 
> --
>
> Key: OOZIE-3536
> URL: https://issues.apache.org/jira/browse/OOZIE-3536
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.1.0
>Reporter: duan xiong
>Assignee: duan xiong
>Priority: Major
>
> oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
> configuration can't find the Tag . In early version 
> 2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (OOZIE-3536) oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade version caused configuration can't find the Tag

2019-08-22 Thread duan xiong (Jira)
duan xiong created OOZIE-3536:
-

 Summary: oozie-main(pom.xml)  plugin maven-javadoc-plugin upgrade 
version caused configuration can't find the Tag 
 Key: OOZIE-3536
 URL: https://issues.apache.org/jira/browse/OOZIE-3536
 Project: Oozie
  Issue Type: Bug
  Components: build
Affects Versions: 5.1.0
Reporter: duan xiong


oozie-main(pom.xml) plugin maven-javadoc-plugin upgrade 3.0.1version caused 
configuration can't find the Tag . In early version 
2.10.4,this plugin has this tag



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (OOZIE-3532) Confusing E1603 error message

2019-07-30 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3532:
-

Assignee: duan xiong

> Confusing E1603 error message
> -
>
> Key: OOZIE-3532
> URL: https://issues.apache.org/jira/browse/OOZIE-3532
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Minor
>
> If we specify an invalid namenode for Oozie we get a useful error message:
> {noformat}
> Error message: E0901: NameNode [localhost:8020] not allowed, not in Oozie's 
> whitelist. Allowed values are: [machinename.com:8020]]{noformat}
> If we accidentally specify {{-DnameNode=hdfs:machinename.com:8020}} instead 
> of {{-DnameNode=hdfs://machinename.com:8020}} we get a very confusing error 
> message:
> {noformat}
> Error: E1603 : Can not create a Path from a null string{noformat}
> Checking the logs also not very helpful:
> {noformat}
> java.lang.IllegalArgumentException: Can not create a Path from a null string
> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:164)
> at org.apache.hadoop.fs.Path.(Path.java:180)
> at 
> org.apache.oozie.servlet.V1JobsServlet.existsOnDFS(V1JobsServlet.java:213)
> at 
> org.apache.oozie.servlet.V1JobsServlet.checkAndWriteApplicationXMLToHDFS(V1JobsServlet.java:162)
> 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:308)
> 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:1780)
> at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:644)
> at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:592)
> at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at 
> org.apache.oozie.servlet.HttpResponseHeaderFilter.doFilter(HttpResponseHeaderFilter.java:68)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at 
> org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> 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:513)
> 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:539)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)
> 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)
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
> at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
> at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPo

[jira] [Updated] (OOZIE-3520) Upgrade Derby to 10.14.2.0

2019-06-28 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3520:
--
Attachment: OOZIE-3520-001.patch

> Upgrade Derby to 10.14.2.0
> --
>
> Key: OOZIE-3520
> URL: https://issues.apache.org/jira/browse/OOZIE-3520
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3520-001.patch
>
>
> Upgrade Derby to the latest in the 10.14.x line: 10.14.2.0.
> We cannot upgrade to 10.15, since it requires JDK9: 
> [https://db.apache.org/derby/derby_downloads.html]



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


[jira] [Assigned] (OOZIE-3520) Upgrade Derby to 10.14.2.0

2019-06-27 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3520:
-

Assignee: duan xiong

> Upgrade Derby to 10.14.2.0
> --
>
> Key: OOZIE-3520
> URL: https://issues.apache.org/jira/browse/OOZIE-3520
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> Upgrade Derby to the latest in the 10.14.x line: 10.14.2.0.
> We cannot upgrade to 10.15, since it requires JDK9: 
> [https://db.apache.org/derby/derby_downloads.html]



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


[jira] [Assigned] (OOZIE-3518) [docs] Dead links in DG_HCatalogIntegration

2019-06-21 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3518:
-

Assignee: duan xiong

> [docs] Dead links in DG_HCatalogIntegration
> ---
>
> Key: OOZIE-3518
> URL: https://issues.apache.org/jira/browse/OOZIE-3518
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3518-001.patch
>
>
> The [HCatalog 
> Integration|https://oozie.apache.org/docs/5.1.0/DG_HCatalogIntegration.html] 
> documentation contains lots of dead links.
> Quite a few links refer to {{http://incubator.apache.org/hcatalog}} which is 
> redirected to {{http://hive.apache.org}} but the files are missing,



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


[jira] [Updated] (OOZIE-3518) [docs] Dead links in DG_HCatalogIntegration

2019-06-21 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3518:
--
Attachment: OOZIE-3518-001.patch

> [docs] Dead links in DG_HCatalogIntegration
> ---
>
> Key: OOZIE-3518
> URL: https://issues.apache.org/jira/browse/OOZIE-3518
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Reporter: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3518-001.patch
>
>
> The [HCatalog 
> Integration|https://oozie.apache.org/docs/5.1.0/DG_HCatalogIntegration.html] 
> documentation contains lots of dead links.
> Quite a few links refer to {{http://incubator.apache.org/hcatalog}} which is 
> redirected to {{http://hive.apache.org}} but the files are missing,



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


[jira] [Commented] (OOZIE-3517) Invalid reference to xtheme-default.css

2019-06-20 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3517:
---

[~asalamon74], I have test the patch.

> Invalid reference to xtheme-default.css
> ---
>
> Key: OOZIE-3517
> URL: https://issues.apache.org/jira/browse/OOZIE-3517
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3517-001.patch
>
>
> [index.jsp|https://github.com/apache/oozie/blob/master/webapp/src/main/webapp/index.jsp#L23]
>  references the {{xtheme-default.css}} file
> {noformat}
>  href="ext-2.2/resources/css/xtheme-default.css"/>
> {noformat}
> This file is not part of the extjs library (ext-2-2.zip) so the browser will 
> not be able to load this css. We should remove the reference. 



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


[jira] [Updated] (OOZIE-3517) Invalid reference to xtheme-default.css

2019-06-20 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3517:
--
Attachment: OOZIE-3517-001.patch

> Invalid reference to xtheme-default.css
> ---
>
> Key: OOZIE-3517
> URL: https://issues.apache.org/jira/browse/OOZIE-3517
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3517-001.patch
>
>
> [index.jsp|https://github.com/apache/oozie/blob/master/webapp/src/main/webapp/index.jsp#L23]
>  references the {{xtheme-default.css}} file
> {noformat}
>  href="ext-2.2/resources/css/xtheme-default.css"/>
> {noformat}
> This file is not part of the extjs library (ext-2-2.zip) so the browser will 
> not be able to load this css. We should remove the reference. 



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


[jira] [Assigned] (OOZIE-3517) Invalid reference to xtheme-default.css

2019-06-20 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3517:
-

Assignee: duan xiong

> Invalid reference to xtheme-default.css
> ---
>
> Key: OOZIE-3517
> URL: https://issues.apache.org/jira/browse/OOZIE-3517
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> [index.jsp|https://github.com/apache/oozie/blob/master/webapp/src/main/webapp/index.jsp#L23]
>  references the {{xtheme-default.css}} file
> {noformat}
>  href="ext-2.2/resources/css/xtheme-default.css"/>
> {noformat}
> This file is not part of the extjs library (ext-2-2.zip) so the browser will 
> not be able to load this css. We should remove the reference. 



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


[jira] [Commented] (OOZIE-3512) Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA

2019-06-17 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3512:
---

[~asalamon74], Thank you very much. I will continue working on this until 
someone able to reproduce it.

> Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA
> --
>
> Key: OOZIE-3512
> URL: https://issues.apache.org/jira/browse/OOZIE-3512
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> {{TestActionStartXCommand.testActionWithEscapedStringAndCDATA}} is flaky, 
> sometimes (for instance: 
> https://issues.apache.org/jira/browse/OOZIE-3470?focusedCommentId=16817901&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16817901
>  ) it fails with the following error message:
> {noformat}junit.framework.AssertionFailedError: YARN App state for app 
> application_1559489642789_0018 expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> org.apache.oozie.test.XTestCase.waitUntilYarnAppDoneAndAssertSuccess(XTestCase.java:1358)
>   at 
> org.apache.oozie.command.wf.TestActionStartXCommand.testActionWithEscapedStringAndCDATA(TestActionStartXCommand.java:235)
> ...
> {noformat}



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


[jira] [Commented] (OOZIE-3512) Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA

2019-06-17 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3512:
---

[~asalamon74], I think the resource not enough really can cause the application 
ACCEPTED. Because I have try  to reproduce But it never show .This issue may be 
isn't need to repair . Otherwise we need more detailed steps to reproduce it.

> Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA
> --
>
> Key: OOZIE-3512
> URL: https://issues.apache.org/jira/browse/OOZIE-3512
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> {{TestActionStartXCommand.testActionWithEscapedStringAndCDATA}} is flaky, 
> sometimes (for instance: 
> https://issues.apache.org/jira/browse/OOZIE-3470?focusedCommentId=16817901&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16817901
>  ) it fails with the following error message:
> {noformat}junit.framework.AssertionFailedError: YARN App state for app 
> application_1559489642789_0018 expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> org.apache.oozie.test.XTestCase.waitUntilYarnAppDoneAndAssertSuccess(XTestCase.java:1358)
>   at 
> org.apache.oozie.command.wf.TestActionStartXCommand.testActionWithEscapedStringAndCDATA(TestActionStartXCommand.java:235)
> ...
> {noformat}



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


[jira] [Commented] (OOZIE-3512) Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA

2019-06-15 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3512:
---

[~asalamon74],I have try to reproduce it locally.I think this problem caused by 
the container resource for example memory/core number.Because In XTestCase
{code:java}
// code placeholder
private static final int DEFAULT_YARN_TIMEOUT = 60_000;{code}
When I set this TIMEOUT = 1000, It can reproduce. But In 60_000, It is  no  
problem. So I think the program is good.

So In some machine It shows failed , Just because the application in ACCEPTED 
State When the time out. If we give it more time, Maybe the application can run 
success. 

> Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA
> --
>
> Key: OOZIE-3512
> URL: https://issues.apache.org/jira/browse/OOZIE-3512
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> {{TestActionStartXCommand.testActionWithEscapedStringAndCDATA}} is flaky, 
> sometimes (for instance: 
> https://issues.apache.org/jira/browse/OOZIE-3470?focusedCommentId=16817901&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16817901
>  ) it fails with the following error message:
> {noformat}junit.framework.AssertionFailedError: YARN App state for app 
> application_1559489642789_0018 expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> org.apache.oozie.test.XTestCase.waitUntilYarnAppDoneAndAssertSuccess(XTestCase.java:1358)
>   at 
> org.apache.oozie.command.wf.TestActionStartXCommand.testActionWithEscapedStringAndCDATA(TestActionStartXCommand.java:235)
> ...
> {noformat}



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


[jira] [Updated] (OOZIE-3495) Upgrade hive version to 1.2.2

2019-06-10 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3495:
--
Attachment: OOZIE-3495-002.patch

> Upgrade hive version to 1.2.2
> -
>
> Key: OOZIE-3495
> URL: https://issues.apache.org/jira/browse/OOZIE-3495
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3495-001.patch, OOZIE-3495-002.patch
>
>
> Oozie still uses hive 1.2.0 which was released in 2015. Upgrading to 2.x (or 
> 3.x) is probably not a good idea in an Oozie minor release, but we could 
> safely upgrade it to the latest 1.2.x version which is 1.2.2 (released in 
> 2017). 



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


[jira] [Assigned] (OOZIE-3512) Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA

2019-06-10 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3512:
-

Assignee: duan xiong

> Flaky test TestActionStartXCommand.testActionWithEscapedStringAndCDATA
> --
>
> Key: OOZIE-3512
> URL: https://issues.apache.org/jira/browse/OOZIE-3512
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> {{TestActionStartXCommand.testActionWithEscapedStringAndCDATA}} is flaky, 
> sometimes (for instance: 
> https://issues.apache.org/jira/browse/OOZIE-3470?focusedCommentId=16817901&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16817901
>  ) it fails with the following error message:
> {noformat}junit.framework.AssertionFailedError: YARN App state for app 
> application_1559489642789_0018 expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> org.apache.oozie.test.XTestCase.waitUntilYarnAppDoneAndAssertSuccess(XTestCase.java:1358)
>   at 
> org.apache.oozie.command.wf.TestActionStartXCommand.testActionWithEscapedStringAndCDATA(TestActionStartXCommand.java:235)
> ...
> {noformat}



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


[jira] [Commented] (OOZIE-3495) Upgrade hive version to 1.2.2

2019-06-10 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3495:
---

Hi,[~asalamon74],I have test this patch. The hive job can success. and Sorry, I 
take long time to do this.I will upload another  patch with the documentations 
later. Thank you!

> Upgrade hive version to 1.2.2
> -
>
> Key: OOZIE-3495
> URL: https://issues.apache.org/jira/browse/OOZIE-3495
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3495-001.patch
>
>
> Oozie still uses hive 1.2.0 which was released in 2015. Upgrading to 2.x (or 
> 3.x) is probably not a good idea in an Oozie minor release, but we could 
> safely upgrade it to the latest 1.2.x version which is 1.2.2 (released in 
> 2017). 



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


[jira] [Updated] (OOZIE-3495) Upgrade hive version to 1.2.2

2019-05-24 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3495:
--
Attachment: OOZIE-3495-001.patch

> Upgrade hive version to 1.2.2
> -
>
> Key: OOZIE-3495
> URL: https://issues.apache.org/jira/browse/OOZIE-3495
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3495-001.patch
>
>
> Oozie still uses hive 1.2.0 which was released in 2015. Upgrading to 2.x (or 
> 3.x) is probably not a good idea in an Oozie minor release, but we could 
> safely upgrade it to the latest 1.2.x version which is 1.2.2 (released in 
> 2017). 



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


[jira] [Assigned] (OOZIE-3495) Upgrade hive version to 1.2.2

2019-05-24 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3495:
-

Assignee: duan xiong

> Upgrade hive version to 1.2.2
> -
>
> Key: OOZIE-3495
> URL: https://issues.apache.org/jira/browse/OOZIE-3495
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Fix For: 5.2.0
>
>
> Oozie still uses hive 1.2.0 which was released in 2015. Upgrading to 2.x (or 
> 3.x) is probably not a good idea in an Oozie minor release, but we could 
> safely upgrade it to the latest 1.2.x version which is 1.2.2 (released in 
> 2017). 



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


[jira] [Updated] (OOZIE-3464) Use UTF8 charset instead of default one

2019-05-18 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3464:
--
Attachment: OOZIE-3464-005.patch

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3464-001.patch, OOZIE-3464-002.patch, 
> OOZIE-3464-003.patch, OOZIE-3464-004.patch, OOZIE-3464-005.patch
>
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Updated] (OOZIE-3464) Use UTF8 charset instead of default one

2019-05-08 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3464:
--
Attachment: OOZIE-3464-004.patch

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3464-001.patch, OOZIE-3464-002.patch, 
> OOZIE-3464-003.patch, OOZIE-3464-004.patch
>
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Commented] (OOZIE-3464) Use UTF8 charset instead of default one

2019-04-18 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3464:
---

HI,[~asalamon74]. Can you help me review this? Thank  you very much.

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3464-001.patch, OOZIE-3464-002.patch, 
> OOZIE-3464-003.patch
>
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Commented] (OOZIE-3464) Use UTF8 charset instead of default one

2019-04-15 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3464:
---

Hi,[~asalamon74]. Can you help me review this? Thank  you very much

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3464-001.patch, OOZIE-3464-002.patch, 
> OOZIE-3464-003.patch
>
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Updated] (OOZIE-3464) Use UTF8 charset instead of default one

2019-04-14 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3464:
--
Attachment: OOZIE-3464-003.patch

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3464-001.patch, OOZIE-3464-002.patch, 
> OOZIE-3464-003.patch
>
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Updated] (OOZIE-3464) Use UTF8 charset instead of default one

2019-04-14 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3464:
--
Attachment: OOZIE-3464-002.patch

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3464-001.patch, OOZIE-3464-002.patch
>
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Commented] (OOZIE-3464) Use UTF8 charset instead of default one

2019-04-12 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3464:
---

[~asalamon74]. Can you help me review this? Thank you !

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3464-001.patch
>
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Updated] (OOZIE-3464) Use UTF8 charset instead of default one

2019-04-12 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3464:
--
Attachment: OOZIE-3464-001.patch

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3464-001.patch
>
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Commented] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-09 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3463:
---

[~asalamon74],I have use the mvn dependency:analyze command. But in Unused 
declared dependencies found list have not com.google.guava.

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch, OOZIE-3463-002.patch, 
> OOZIE-3463-003.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Commented] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-09 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3463:
---

[~asalamon74], Thank you very much. I will try to resolve this.

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch, OOZIE-3463-002.patch, 
> OOZIE-3463-003.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Comment Edited] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-08 Thread duan xiong (JIRA)


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

duan xiong edited comment on OOZIE-3463 at 4/9/19 12:55 AM:


HI,[~kmarton],I have read the pom  about the problem. Can we first submit this 
issue, Then resolve this pom problem  in new issue? Because this patch have too 
many changes. 


was (Author: nobigo):
HI,[~kmarton],I have read the pom  about the problem. Can we first submit this 
issue, Then resolve this pom problem  in new issue?

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch, OOZIE-3463-002.patch, 
> OOZIE-3463-003.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Commented] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-08 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3463:
---

HI,[~kmarton],I have read the pom  about the problem. Can we first submit this 
issue, Then resolve this pom problem  in new issue?

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch, OOZIE-3463-002.patch, 
> OOZIE-3463-003.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Commented] (OOZIE-3464) Use UTF8 charset instead of default one

2019-04-08 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3464:
---

HI,[~kmarton],I have noticed this problem. Because findbugs always warning 
about this issue.

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Assigned] (OOZIE-3464) Use UTF8 charset instead of default one

2019-04-08 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3464:
-

Assignee: duan xiong

> Use UTF8 charset instead of default one
> ---
>
> Key: OOZIE-3464
> URL: https://issues.apache.org/jira/browse/OOZIE-3464
> Project: Oozie
>  Issue Type: Bug
>Reporter: Julia Kinga Marton
>Assignee: duan xiong
>Priority: Major
>
> There are some places in code, when we are reading/writing to files and we do 
> not define any character set, so the default one will be used. Since the 
> default implementation may change between the java versions our output will 
> be platform dependent.
> For example if we have a shell action with a script that will echo something 
> using Chinese text, '' are be printed in case of jdk1.8.0_141.



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


[jira] [Updated] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-07 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3463:
--
Attachment: OOZIE-3463-003.patch

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch, OOZIE-3463-002.patch, 
> OOZIE-3463-003.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Updated] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-07 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3463:
--
Attachment: OOZIE-3463-002.patch

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch, OOZIE-3463-002.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Commented] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-05 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3463:
---

Hi,[~asalamon74],Can you help me review this.Thank you !

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Updated] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-05 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3463:
--
Attachment: OOZIE-3463-001.patch

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Assigned] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets

2019-04-05 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3463:
-

Assignee: duan xiong

> Migrate from com.google.common.base.Charsets to 
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java 
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}} 
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.



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


[jira] [Updated] (OOZIE-3458) Can no longer submit a coordinator job which has oozie.libpath and oozie.coord.application.path set

2019-04-05 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3458:
--
Attachment: OOZIE-3463-001.patch

> Can no longer submit a coordinator job which has oozie.libpath and 
> oozie.coord.application.path set
> ---
>
> Key: OOZIE-3458
> URL: https://issues.apache.org/jira/browse/OOZIE-3458
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Jerry Chabot
>Priority: Critical
> Attachments: OOZIE-3463-001.patch
>
>
> This bug is related to https://issues.apache.org/jira/browse/OOZIE-3457. Our 
> Production environment is currently running Amazon EMR 5.19. We want to 
> upgrade to EMR 5.22. Oozie will be upgraded from 5.0.0 to 5.1.0. Our 
> deployment scripts can no longer submit coordinator jobs after upgrading a 
> test environment. Here is a sample post from the oozie client.
> POST [http://hbase.qa.local:11000/oozie/v2/jobs?action=start]
> 
> nameNodehdfs://hbase.qa.local:8020
> oozie.use.system.libpathtrue
> startTime2018-03-28T00:00Z
> queueNameoozie
> jobTrackerhbase.qa.local:8032
> oozie.libpathhdfs://hbase.qa.local:8020/user/oozie/cmx
> endTime2020-01-01:00Z
> applicationConfigFilehdfs://hbase.qa.local:8020/usr/share/cmx/conf/app.properties,hdfs://hbase.qa.local:8020/usr/share/cmx/conf/crypto.properties
> frequency240
> user.nameoozie
> oozie.coord.application.pathhdfs://hbase.qa.local:8020/user/oozie/reporting/workspaceDimToVertica/
> 
> Error: E0307 : E0307: Runtime error [App directory [null] does not exist and 
> app definition cannot be created because of missing config value 
> [oozie.jobs.api.generated.xml]]
> Note, our code specifies oozie.libpath and oozie.coord.application.path. Is 
> this no longer allowed?
> I've narrowed down the problem to the checkAndWriteApplicationXMLToHDFS(...) 
> method in V1JobsServlet.java. It is related to the new feature for submitting 
> embedded XML within the job submission. This method is check whether the 
> workflow.xml or coodinator.xml exists in either oozie.wf.application.path, 
> oozie.libpath, oozie.coord.application.path or oozie.bundle.application.path.
> First, why is it checking oozie.libpath? That is not an application path.
> Second, it stops looking as soon as findAppPathsWithFileNames() returns  a 
> value. Which it will always do when oozie.libpath is set even if an xml 
> doesn't exist there. It does not continue looking for an xml file in 
> oozie.coord.application.path or oozie.bundle.application.path.  I realize 
> only one application path should be specified. IIMO, its the oozie.libpath 
> check that is the problem.
> Third, the logic is inefficient. Here are two lines. Why call the same method 
> again with the same params. You already have the result!
> if (!findAppPathsWithFileNames(appPath, "workflow.xml").isEmpty()) {
>  appPathsWithFileNames = findAppPathsWithFileNames(appPath, "workflow.xml");
>  }
> It is critical that we upgrade to EMR 5.22. However, we are blocked until we 
> figure out a way to get the job submitted and completing successfully. Any 
> suggested workarounds would be greatly appreciated. But, I am filing this bug 
> to get it fixed so an upgraded Oozie will make it into a future EMR release. 



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


[jira] [Commented] (OOZIE-3460) Remove apache-curator pom files from Oozie hive sharelib

2019-04-03 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3460:
---

Hi,[~asalamon74],Can you help me review this issue? Thank you very much.

> Remove apache-curator pom files from Oozie hive sharelib
> 
>
> Key: OOZIE-3460
> URL: https://issues.apache.org/jira/browse/OOZIE-3460
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Minor
> Attachments: OOZIE-3460-001.patch
>
>
> Oozie hive sharelib contain not only jar files but also a pom file 
> ({{apache-curator-2.12.0.pom}}). We don't need this file in the sharelibs, we 
> should remove it.



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


[jira] [Commented] (OOZIE-3461) CoordMaterializeTriggerService code cleanup

2019-04-03 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3461:
---

Hi,[~asalamon74],Ok, I will address these issues.

> CoordMaterializeTriggerService code cleanup
> ---
>
> Key: OOZIE-3461
> URL: https://issues.apache.org/jira/browse/OOZIE-3461
> Project: Oozie
>  Issue Type: Task
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Minor
> Attachments: OOZIE-3461-001.patch
>
>
> It seems to me don't really use the {{delayedCallables}} and {{delay}} 
> variables in 
> {{CoordMaterializeTriggerService.CoordMaterializeTriggerRunnable}} class. We 
> only add items to {{callables}} and not to {{delayedCallables}}. We could 
> remove this part of the class.
> It should be also useful to log the lock acquiring and not only the releasing 
> ( like in 
> [PauseTransitService|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/PauseTransitService.java#L86]
>  )
>  



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


[jira] [Updated] (OOZIE-3461) CoordMaterializeTriggerService code cleanup

2019-04-02 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3461:
--
Attachment: OOZIE-3461-001.patch

> CoordMaterializeTriggerService code cleanup
> ---
>
> Key: OOZIE-3461
> URL: https://issues.apache.org/jira/browse/OOZIE-3461
> Project: Oozie
>  Issue Type: Task
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Minor
> Attachments: OOZIE-3461-001.patch
>
>
> It seems to me don't really use the {{delayedCallables}} and {{delay}} 
> variables in 
> {{CoordMaterializeTriggerService.CoordMaterializeTriggerRunnable}} class. We 
> only add items to {{callables}} and not to {{delayedCallables}}. We could 
> remove this part of the class.
> It should be also useful to log the lock acquiring and not only the releasing 
> ( like in 
> [PauseTransitService|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/PauseTransitService.java#L86]
>  )
>  



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


[jira] [Updated] (OOZIE-3460) Remove apache-curator pom files from Oozie hive sharelib

2019-04-02 Thread duan xiong (JIRA)


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

duan xiong updated OOZIE-3460:
--
Attachment: OOZIE-3460-001.patch

> Remove apache-curator pom files from Oozie hive sharelib
> 
>
> Key: OOZIE-3460
> URL: https://issues.apache.org/jira/browse/OOZIE-3460
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Minor
> Attachments: OOZIE-3460-001.patch
>
>
> Oozie hive sharelib contain not only jar files but also a pom file 
> ({{apache-curator-2.12.0.pom}}). We don't need this file in the sharelibs, we 
> should remove it.



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


[jira] [Comment Edited] (OOZIE-3459) Oozie cannot be built using Java 11

2019-04-01 Thread duan xiong (JIRA)


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

duan xiong edited comment on OOZIE-3459 at 4/2/19 1:05 AM:
---

Hi,[~dionusos]. Sorry ,I use the openJdk11.So maybe that's different.

Do you try change this java version  to 11? 

```

1.8

1.8

1.8

```


was (Author: nobigo):
Hi,[~dionusos]. Sorry ,I use the openJdk11.So maybe that's different. 

> Oozie cannot be built using Java 11
> ---
>
> Key: OOZIE-3459
> URL: https://issues.apache.org/jira/browse/OOZIE-3459
> Project: Oozie
>  Issue Type: Bug
>  Components: core, fluent-job
>Affects Versions: 5.1.0
>Reporter: Denes Bodo
>Priority: Major
>
> Using OpenJDK 11 I am not able to build Oozie using {{mvn clean install}}.
> I found two issues:
>  * Fluent job API build fails due to Jaxb2 maven plugin.
>  * No {{com.sun.tools.}} package is available so *TestMetricsInstrumentation* 
> will not work.
>  * Maven surefire plugin has to be updated. It works with 3.0.0-M3



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


[jira] [Commented] (OOZIE-3459) Oozie cannot be built using Java 11

2019-04-01 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-3459:
---

Hi,[~dionusos]. Sorry ,I use the openJdk11.So maybe that's different. 

> Oozie cannot be built using Java 11
> ---
>
> Key: OOZIE-3459
> URL: https://issues.apache.org/jira/browse/OOZIE-3459
> Project: Oozie
>  Issue Type: Bug
>  Components: core, fluent-job
>Affects Versions: 5.1.0
>Reporter: Denes Bodo
>Priority: Major
>
> Using OpenJDK 11 I am not able to build Oozie using {{mvn clean install}}.
> I found two issues:
>  * Fluent job API build fails due to Jaxb2 maven plugin.
>  * No {{com.sun.tools.}} package is available so *TestMetricsInstrumentation* 
> will not work.
>  * Maven surefire plugin has to be updated. It works with 3.0.0-M3



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


[jira] [Assigned] (OOZIE-3461) CoordMaterializeTriggerService code cleanup

2019-04-01 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3461:
-

Assignee: duan xiong

> CoordMaterializeTriggerService code cleanup
> ---
>
> Key: OOZIE-3461
> URL: https://issues.apache.org/jira/browse/OOZIE-3461
> Project: Oozie
>  Issue Type: Task
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Minor
>
> It seems to me don't really use the {{delayedCallables}} and {{delay}} 
> variables in 
> {{CoordMaterializeTriggerService.CoordMaterializeTriggerRunnable}} class. We 
> only add items to {{callables}} and not to {{delayedCallables}}. We could 
> remove this part of the class.



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


[jira] [Assigned] (OOZIE-3460) Remove apache-curator pom files from Oozie hive sharelib

2019-04-01 Thread duan xiong (JIRA)


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

duan xiong reassigned OOZIE-3460:
-

Assignee: duan xiong

> Remove apache-curator pom files from Oozie hive sharelib
> 
>
> Key: OOZIE-3460
> URL: https://issues.apache.org/jira/browse/OOZIE-3460
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Minor
>
> Oozie hive sharelib contain not only jar files but also a pom file 
> ({{apache-curator-2.12.0.pom}}). We don't need this file in the sharelibs, we 
> should remove it.



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


[jira] [Commented] (OOZIE-2952) Fix Findbugs warnings in oozie-sharelib-oozie

2019-04-01 Thread duan xiong (JIRA)


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

duan xiong commented on OOZIE-2952:
---

Hi,[~Jan Hentschel],If you don't mind I will take over it.If you have any 
concern please let me know.

> Fix Findbugs warnings in oozie-sharelib-oozie
> -
>
> Key: OOZIE-2952
> URL: https://issues.apache.org/jira/browse/OOZIE-2952
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Major
> Attachments: OOZIE-2952-1.patch
>
>
> Currently Findbugs complains about the following warnings in the 
> *oozie-sharelib-oozie* module:
> {code}
> [INFO] The class org.apache.oozie.action.hadoop.HdfsOperations$2 could be 
> refactored into a named _static_ inner class 
> [org.apache.oozie.action.hadoop.HdfsOperations] At HdfsOperations.java:[line 
> 80]
> [INFO] The class org.apache.oozie.action.hadoop.HdfsOperations$3 could be 
> refactored into a named _static_ inner class 
> [org.apache.oozie.action.hadoop.HdfsOperations] At HdfsOperations.java:[line 
> 91]
> [INFO] The class org.apache.oozie.action.hadoop.HdfsOperations$4 could be 
> refactored into a named _static_ inner class 
> [org.apache.oozie.action.hadoop.HdfsOperations] At HdfsOperations.java:[line 
> 105]
> [INFO] Use of non-localized String.toUpperCase() or String.toLowerCase() in 
> org.apache.oozie.action.hadoop.LauncherMain.printArgs(String, String[]) 
> [org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 416]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMain.getHadoopJobIds(String, 
> Pattern[]): new java.io.FileReader(String) 
> [org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 139]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMain.writeExternalChildIDs(String, 
> Pattern[], String): String.getBytes() 
> [org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 175]
> [INFO] org.apache.oozie.action.hadoop.LauncherMain.HADOOP_SITE_FILES should 
> be both final and package protected 
> [org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 76]
> [INFO] Exceptional return value of java.io.File.mkdirs() ignored in 
> org.apache.oozie.action.hadoop.LauncherMain.writeHadoopConfig(String, File) 
> [org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 394]
> [INFO] Use of non-localized String.toUpperCase() or String.toLowerCase() in 
> org.apache.oozie.action.hadoop.LauncherMapper.printArgs(String, String[]) 
> [org.apache.oozie.action.hadoop.LauncherMapper] At LauncherMapper.java:[line 
> 660]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMapper.getLocalFileContentStr(File, 
> String, int): new java.io.FileReader(File) 
> [org.apache.oozie.action.hadoop.LauncherMapper] At LauncherMapper.java:[line 
> 407]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMapper.propagateToHadoopConf(): new 
> java.io.FileWriter(String) [org.apache.oozie.action.hadoop.LauncherMapper] At 
> LauncherMapper.java:[line 355]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMapper.propagateToHadoopConf(): new 
> java.io.OutputStreamWriter(OutputStream) 
> [org.apache.oozie.action.hadoop.LauncherMapper] At LauncherMapper.java:[line 
> 356]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMapper.setRecoveryId(Configuration, 
> Path, String): new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.hadoop.LauncherMapper] At LauncherMapper.java:[line 
> 107]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMapper.setRecoveryId(Configuration, 
> Path, String): new java.io.OutputStreamWriter(OutputStream) 
> [org.apache.oozie.action.hadoop.LauncherMapper] At LauncherMapper.java:[line 
> 97]
> [INFO] 
> org.apache.oozie.action.hadoop.LauncherMapper.getLocalFileContentStr(File, 
> String, int) may fail to clean up java.io.Reader on checked exception 
> [org.apache.oozie.action.hadoop.LauncherMapper, 
> org.apache.oozie.action.hadoop.LauncherMapper, 
> org.apache.oozie.action.hadoop.LauncherMapper, 
> org.apache.oozie.action.hadoop.LauncherMapper] Obligation to clean up 
> resource created at LauncherMapper.java:[line 407] is not dischargedPath 
> continues at LauncherMapper.java:[line 408]Path continues at 
> LauncherMapper.java:[line 410]Path continues at LauncherMapper.java:[line 411]
> [INFO] org.apache.oozie.action.hadoop.LauncherMapper.propagateToHadoopConf() 
> may fail to clean up java.io.Writer on checked exception 
> [org.apache

  1   2   3   >