[jira] [Assigned] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar reassigned AMBARI-21569:
-
Assignee: venkat (was: Gaurav Nagar)
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at
>
[jira] [Created] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
Gaurav Nagar created AMBARI-21569:
-
Summary: Users randomly getting "HDFS020 Could not write file"
exceptions while running query from Hive View
Key: AMBARI-21569
URL: https://issues.apache.org/jira/browse/AMBARI-21569
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
Running queries from Hive View are reporting intermittent issues with the Hive
view. They get the exceptions as reported below
{code:java}
ServiceFormattedException:100 -
org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
at
org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
at
org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
at
org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
at
org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
at
org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
at
org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
[jira] [Updated] (AMBARI-20888) wrong ZK parent node (hbase-unsecure) getting configured as part of the jdbc(phoenix) URL on ubuntu secured cluster
[ https://issues.apache.org/jira/browse/AMBARI-20888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20888: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > wrong ZK parent node (hbase-unsecure) getting configured as part of the > jdbc(phoenix) URL on ubuntu secured cluster > --- > > Key: AMBARI-20888 > URL: https://issues.apache.org/jira/browse/AMBARI-20888 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.1 > > Attachments: AMBARI-20888_trunk_v1.patch > > > wrong ZK parent node (hbase-unsecure) getting configured as part of the > jdbc(phoenix) URL on ubuntu secured cluster the jdbc(phoenix) url was getting > appended as /hbase-unsecure which is not correct > If you check the hbase-site.xml > > zookeeper.znode.parent > /hbase-secure > > I think how the phoenix URL is being constructed is not consistent across the > configs and we need to see why. On some of the other platforms, I have seen > it getting configured correctly (for e.g. Centos6 secured wire-encrypted) > Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20888) wrong ZK parent node (hbase-unsecure) getting configured as part of the jdbc(phoenix) URL on ubuntu secured cluster
[ https://issues.apache.org/jira/browse/AMBARI-20888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20888: -- Fix Version/s: (was: 2.5.2) 2.5.1 > wrong ZK parent node (hbase-unsecure) getting configured as part of the > jdbc(phoenix) URL on ubuntu secured cluster > --- > > Key: AMBARI-20888 > URL: https://issues.apache.org/jira/browse/AMBARI-20888 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.1 > > Attachments: AMBARI-20888_trunk_v1.patch > > > wrong ZK parent node (hbase-unsecure) getting configured as part of the > jdbc(phoenix) URL on ubuntu secured cluster the jdbc(phoenix) url was getting > appended as /hbase-unsecure which is not correct > If you check the hbase-site.xml > > zookeeper.znode.parent > /hbase-secure > > I think how the phoenix URL is being constructed is not consistent across the > configs and we need to see why. On some of the other platforms, I have seen > it getting configured correctly (for e.g. Centos6 secured wire-encrypted) > Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20888) wrong ZK parent node (hbase-unsecure) getting configured as part of the jdbc(phoenix) URL on ubuntu secured cluster
[ https://issues.apache.org/jira/browse/AMBARI-20888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20888: -- Fix Version/s: 2.5.2 > wrong ZK parent node (hbase-unsecure) getting configured as part of the > jdbc(phoenix) URL on ubuntu secured cluster > --- > > Key: AMBARI-20888 > URL: https://issues.apache.org/jira/browse/AMBARI-20888 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.2 > > Attachments: AMBARI-20888_trunk_v1.patch > > > wrong ZK parent node (hbase-unsecure) getting configured as part of the > jdbc(phoenix) URL on ubuntu secured cluster the jdbc(phoenix) url was getting > appended as /hbase-unsecure which is not correct > If you check the hbase-site.xml > > zookeeper.znode.parent > /hbase-secure > > I think how the phoenix URL is being constructed is not consistent across the > configs and we need to see why. On some of the other platforms, I have seen > it getting configured correctly (for e.g. Centos6 secured wire-encrypted) > Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-18387) Unable to delete Hive view
[
https://issues.apache.org/jira/browse/AMBARI-18387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982441#comment-15982441
]
Gaurav Nagar commented on AMBARI-18387:
---
Committed to branch-2.4
> Unable to delete Hive view
> --
>
> Key: AMBARI-18387
> URL: https://issues.apache.org/jira/browse/AMBARI-18387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0, 2.4.3
>
> Attachments: AMBARI-18387.branch-2.5.patch
>
>
> STR:
> 1. Install cluster without Hive.
> 2. Create Hive view.
> 3. Try to remove Hive view.
> Error is returned.
> {noformat}
> {
> "status": 500,
> "message": "Server Error"
> }
> {noformat}
> Then the same error is returned when you are trying to open edit view page
> and as result UI is unable to load data about instance.
> From ambari-server.log:
> {noformat}
> 02 Aug 2016 11:57:04,669 ERROR [ambari-client-thread-118]
> ContainerResponse:419 - The RuntimeException could not be mapped to a
> response, re-throwing to the HTTP container
> com.typesafe.config.ConfigException$Missing: No configuration setting found
> for key 'akka'
> at com.typesafe.config.impl.SimpleConfig.findKey(SimpleConfig.java:124)
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:147)
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:159)
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:164)
> at
> com.typesafe.config.impl.SimpleConfig.getString(SimpleConfig.java:206)
> at akka.actor.ActorSystem$Settings.(ActorSystem.scala:169)
> at akka.actor.ActorSystemImpl.(ActorSystem.scala:505)
> at akka.actor.ActorSystem$.apply(ActorSystem.scala:142)
> at akka.actor.ActorSystem$.apply(ActorSystem.scala:109)
> at akka.actor.ActorSystem$.create(ActorSystem.scala:57)
> at akka.actor.ActorSystem.create(ActorSystem.scala)
> at
> org.apache.ambari.view.hive2.ConnectionSystem.(ConnectionSystem.java:45)
> at
> org.apache.ambari.view.hive2.ConnectionSystem.getInstance(ConnectionSystem.java:53)
> at
> org.apache.ambari.view.hive2.HiveViewImpl.onDestroy(HiveViewImpl.java:42)
> at
> org.apache.ambari.server.view.ViewRegistry.removeInstanceDefinition(ViewRegistry.java:475)
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20641) Pig view fails to load when using ambari thru KNOX
[ https://issues.apache.org/jira/browse/AMBARI-20641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20641: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Pig view fails to load when using ambari thru KNOX > --- > > Key: AMBARI-20641 > URL: https://issues.apache.org/jira/browse/AMBARI-20641 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > Attachments: AMBARI-20641_branch-2.5.patch > > > Problem seems to be caused by pig view java scripts making async postbacks to > context that is not being handled by knox. > Direct url without Knox: > http://:8080/#/main/views/PIG/1.0.0/PIG > working script url: > http://:8080/api/v1/views/PIG/versions/1.0.0/instances/PIG/scripts?_=1482263718137 > > Knox url > https://:8443/gateway/default/ambari/#/main/views/PIG/1.0.0/ > 404 link url: > https://:8443/api/v1/views/default/versions/ambari/instances/views/scripts?_=1482263506651 > > There are few more 404 links broken following same pattern as the above one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20642) Knox Proxy - Pig view fails to load when using ambari thru KNOX
[ https://issues.apache.org/jira/browse/AMBARI-20642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar resolved AMBARI-20642. --- Resolution: Duplicate Duplicate of AMBARI-20641 > Knox Proxy - Pig view fails to load when using ambari thru KNOX > --- > > Key: AMBARI-20642 > URL: https://issues.apache.org/jira/browse/AMBARI-20642 > Project: Ambari > Issue Type: Bug >Reporter: Gaurav Nagar > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20642) Knox Proxy - Pig view fails to load when using ambari thru KNOX
Gaurav Nagar created AMBARI-20642: - Summary: Knox Proxy - Pig view fails to load when using ambari thru KNOX Key: AMBARI-20642 URL: https://issues.apache.org/jira/browse/AMBARI-20642 Project: Ambari Issue Type: Bug Reporter: Gaurav Nagar -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20641) Pig view fails to load when using ambari thru KNOX
[ https://issues.apache.org/jira/browse/AMBARI-20641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20641: -- Status: Patch Available (was: Open) > Pig view fails to load when using ambari thru KNOX > --- > > Key: AMBARI-20641 > URL: https://issues.apache.org/jira/browse/AMBARI-20641 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > Attachments: AMBARI-20641_branch-2.5.patch > > > Problem seems to be caused by pig view java scripts making async postbacks to > context that is not being handled by knox. > Direct url without Knox: > http://:8080/#/main/views/PIG/1.0.0/PIG > working script url: > http://:8080/api/v1/views/PIG/versions/1.0.0/instances/PIG/scripts?_=1482263718137 > > Knox url > https://:8443/gateway/default/ambari/#/main/views/PIG/1.0.0/ > 404 link url: > https://:8443/api/v1/views/default/versions/ambari/instances/views/scripts?_=1482263506651 > > There are few more 404 links broken following same pattern as the above one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20641) Pig view fails to load when using ambari thru KNOX
[ https://issues.apache.org/jira/browse/AMBARI-20641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20641: -- Attachment: AMBARI-20641_branch-2.5.patch > Pig view fails to load when using ambari thru KNOX > --- > > Key: AMBARI-20641 > URL: https://issues.apache.org/jira/browse/AMBARI-20641 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > Attachments: AMBARI-20641_branch-2.5.patch > > > Problem seems to be caused by pig view java scripts making async postbacks to > context that is not being handled by knox. > Direct url without Knox: > http://:8080/#/main/views/PIG/1.0.0/PIG > working script url: > http://:8080/api/v1/views/PIG/versions/1.0.0/instances/PIG/scripts?_=1482263718137 > > Knox url > https://:8443/gateway/default/ambari/#/main/views/PIG/1.0.0/ > 404 link url: > https://:8443/api/v1/views/default/versions/ambari/instances/views/scripts?_=1482263506651 > > There are few more 404 links broken following same pattern as the above one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20641) Pig view fails to load when using ambari thru KNOX
[ https://issues.apache.org/jira/browse/AMBARI-20641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20641: -- Component/s: ambari-views > Pig view fails to load when using ambari thru KNOX > --- > > Key: AMBARI-20641 > URL: https://issues.apache.org/jira/browse/AMBARI-20641 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > > Problem seems to be caused by pig view java scripts making async postbacks to > context that is not being handled by knox. > Direct url without Knox: > http://:8080/#/main/views/PIG/1.0.0/PIG > working script url: > http://:8080/api/v1/views/PIG/versions/1.0.0/instances/PIG/scripts?_=1482263718137 > > Knox url > https://:8443/gateway/default/ambari/#/main/views/PIG/1.0.0/ > 404 link url: > https://:8443/api/v1/views/default/versions/ambari/instances/views/scripts?_=1482263506651 > > There are few more 404 links broken following same pattern as the above one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20641) Pig view fails to load when using ambari thru KNOX
Gaurav Nagar created AMBARI-20641: - Summary: Pig view fails to load when using ambari thru KNOX Key: AMBARI-20641 URL: https://issues.apache.org/jira/browse/AMBARI-20641 Project: Ambari Issue Type: Bug Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.1 Problem seems to be caused by pig view java scripts making async postbacks to context that is not being handled by knox. Direct url without Knox: http://:8080/#/main/views/PIG/1.0.0/PIG working script url: http://:8080/api/v1/views/PIG/versions/1.0.0/instances/PIG/scripts?_=1482263718137 Knox url https://:8443/gateway/default/ambari/#/main/views/PIG/1.0.0/ 404 link url: https://:8443/api/v1/views/default/versions/ambari/instances/views/scripts?_=1482263506651 There are few more 404 links broken following same pattern as the above one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20574) Hive View 2.0 On SLES12-Table created on Upload throws error
[
https://issues.apache.org/jira/browse/AMBARI-20574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942335#comment-15942335
]
Gaurav Nagar commented on AMBARI-20574:
---
Committed to trunk
> Hive View 2.0 On SLES12-Table created on Upload throws error
> -
>
> Key: AMBARI-20574
> URL: https://issues.apache.org/jira/browse/AMBARI-20574
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20574_branch-2.5.patch
>
>
> Caused by: java.sql.SQLException: Error while processing statement: FAILED:
> Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask.
> MetaException(message:javax.jdo.JDODataStoreException: Put request failed :
> INSERT INTO "SERDE_PARAMS" ("PARAM_VALUE","SERDE_ID","PARAM_KEY") VALUES
> (?,?,?)
> at
> org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:543)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:720)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:740)
> at
> org.apache.hadoop.hive.metastore.ObjectStore.createTable(ObjectStore.java:921)
> at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:103)
> at com.sun.proxy.$Proxy8.createTable(Unknown Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1534)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:1579)
> at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
> at com.sun.proxy.$Proxy12.create_table_with_environment_context(Unknown
> Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.create_table_with_environment_context(HiveMetaStoreClient.java:2167)
> at
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.create_table_with_environment_context(SessionHiveMetaStoreClient.java:97)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:735)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:723)
> at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:178)
> at com.sun.proxy.$Proxy13.createTable(Unknown Source)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:762)
> at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:4409)
> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:316)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
> at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1748)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1494)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1291)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1158)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1153)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:253)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
>
[jira] [Updated] (AMBARI-20574) Hive View 2.0 On SLES12-Table created on Upload throws error
[
https://issues.apache.org/jira/browse/AMBARI-20574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20574:
--
Attachment: AMBARI-20574_branch-2.5.patch
> Hive View 2.0 On SLES12-Table created on Upload throws error
> -
>
> Key: AMBARI-20574
> URL: https://issues.apache.org/jira/browse/AMBARI-20574
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20574_branch-2.5.patch
>
>
> Caused by: java.sql.SQLException: Error while processing statement: FAILED:
> Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask.
> MetaException(message:javax.jdo.JDODataStoreException: Put request failed :
> INSERT INTO "SERDE_PARAMS" ("PARAM_VALUE","SERDE_ID","PARAM_KEY") VALUES
> (?,?,?)
> at
> org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:543)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:720)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:740)
> at
> org.apache.hadoop.hive.metastore.ObjectStore.createTable(ObjectStore.java:921)
> at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:103)
> at com.sun.proxy.$Proxy8.createTable(Unknown Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1534)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:1579)
> at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
> at com.sun.proxy.$Proxy12.create_table_with_environment_context(Unknown
> Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.create_table_with_environment_context(HiveMetaStoreClient.java:2167)
> at
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.create_table_with_environment_context(SessionHiveMetaStoreClient.java:97)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:735)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:723)
> at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:178)
> at com.sun.proxy.$Proxy13.createTable(Unknown Source)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:762)
> at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:4409)
> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:316)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
> at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1748)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1494)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1291)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1158)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1153)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:253)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2.run(SQLOperation.java:264)
>
[jira] [Updated] (AMBARI-20574) Hive View 2.0 On SLES12-Table created on Upload throws error
[
https://issues.apache.org/jira/browse/AMBARI-20574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20574:
--
Status: Patch Available (was: Open)
> Hive View 2.0 On SLES12-Table created on Upload throws error
> -
>
> Key: AMBARI-20574
> URL: https://issues.apache.org/jira/browse/AMBARI-20574
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20574_branch-2.5.patch
>
>
> Caused by: java.sql.SQLException: Error while processing statement: FAILED:
> Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask.
> MetaException(message:javax.jdo.JDODataStoreException: Put request failed :
> INSERT INTO "SERDE_PARAMS" ("PARAM_VALUE","SERDE_ID","PARAM_KEY") VALUES
> (?,?,?)
> at
> org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:543)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:720)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:740)
> at
> org.apache.hadoop.hive.metastore.ObjectStore.createTable(ObjectStore.java:921)
> at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:103)
> at com.sun.proxy.$Proxy8.createTable(Unknown Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1534)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:1579)
> at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
> at com.sun.proxy.$Proxy12.create_table_with_environment_context(Unknown
> Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.create_table_with_environment_context(HiveMetaStoreClient.java:2167)
> at
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.create_table_with_environment_context(SessionHiveMetaStoreClient.java:97)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:735)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:723)
> at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:178)
> at com.sun.proxy.$Proxy13.createTable(Unknown Source)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:762)
> at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:4409)
> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:316)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
> at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1748)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1494)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1291)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1158)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1153)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:253)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2.run(SQLOperation.java:264)
>
[jira] [Updated] (AMBARI-20574) Hive View 2.0 On SLES12-Table created on Upload throws error
[
https://issues.apache.org/jira/browse/AMBARI-20574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20574:
--
Summary: Hive View 2.0 On SLES12-Table created on Upload throws error
(was: On SLES12-Table created on Upload throws error )
> Hive View 2.0 On SLES12-Table created on Upload throws error
> -
>
> Key: AMBARI-20574
> URL: https://issues.apache.org/jira/browse/AMBARI-20574
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
>Priority: Blocker
> Fix For: 2.5.1
>
>
> Caused by: java.sql.SQLException: Error while processing statement: FAILED:
> Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask.
> MetaException(message:javax.jdo.JDODataStoreException: Put request failed :
> INSERT INTO "SERDE_PARAMS" ("PARAM_VALUE","SERDE_ID","PARAM_KEY") VALUES
> (?,?,?)
> at
> org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:543)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:720)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:740)
> at
> org.apache.hadoop.hive.metastore.ObjectStore.createTable(ObjectStore.java:921)
> at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:103)
> at com.sun.proxy.$Proxy8.createTable(Unknown Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1534)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:1579)
> at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
> at com.sun.proxy.$Proxy12.create_table_with_environment_context(Unknown
> Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.create_table_with_environment_context(HiveMetaStoreClient.java:2167)
> at
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.create_table_with_environment_context(SessionHiveMetaStoreClient.java:97)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:735)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:723)
> at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:178)
> at com.sun.proxy.$Proxy13.createTable(Unknown Source)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:762)
> at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:4409)
> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:316)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
> at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1748)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1494)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1291)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1158)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1153)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:253)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
>
[jira] [Updated] (AMBARI-20574) On SLES12-Table created on Upload throws error
[
https://issues.apache.org/jira/browse/AMBARI-20574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20574:
--
Fix Version/s: (was: 2.5.0)
2.5.1
> On SLES12-Table created on Upload throws error
> ---
>
> Key: AMBARI-20574
> URL: https://issues.apache.org/jira/browse/AMBARI-20574
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
>Priority: Blocker
> Fix For: 2.5.1
>
>
> Caused by: java.sql.SQLException: Error while processing statement: FAILED:
> Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask.
> MetaException(message:javax.jdo.JDODataStoreException: Put request failed :
> INSERT INTO "SERDE_PARAMS" ("PARAM_VALUE","SERDE_ID","PARAM_KEY") VALUES
> (?,?,?)
> at
> org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:543)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:720)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:740)
> at
> org.apache.hadoop.hive.metastore.ObjectStore.createTable(ObjectStore.java:921)
> at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:103)
> at com.sun.proxy.$Proxy8.createTable(Unknown Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1534)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:1579)
> at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
> at com.sun.proxy.$Proxy12.create_table_with_environment_context(Unknown
> Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.create_table_with_environment_context(HiveMetaStoreClient.java:2167)
> at
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.create_table_with_environment_context(SessionHiveMetaStoreClient.java:97)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:735)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:723)
> at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:178)
> at com.sun.proxy.$Proxy13.createTable(Unknown Source)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:762)
> at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:4409)
> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:316)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
> at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1748)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1494)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1291)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1158)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1153)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:253)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2.run(SQLOperation.java:264)
> at
>
[jira] [Updated] (AMBARI-20573) Hive view 2.0 fails on LLAP
[ https://issues.apache.org/jira/browse/AMBARI-20573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20573: -- Attachment: AMBARI-20573_branch-2.5.patch > Hive view 2.0 fails on LLAP > --- > > Key: AMBARI-20573 > URL: https://issues.apache.org/jira/browse/AMBARI-20573 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > Attachments: AMBARI-20573_branch-2.5.patch > > > Hive View 2.0.0 with default configuration fails with llap. > Ambari server logs show below failure > 22 Mar 2017 00:11:56,882 INFO [ambari-client-thread-30] ZooKeeper:684 - > Session: 0x25af27aae5a014f closed > 22 Mar 2017 00:11:56,882 INFO [ambari-client-thread-30-EventThread] > ClientCnxn:524 - EventThread shut down > 22 Mar 2017 00:11:56,894 ERROR [ambari-client-thread-30] > ContainerResponse:537 - Mapped exception to response: 500 (Internal Server > Error) > org.apache.ambari.view.hive20.utils.ServiceFormattedException > at > org.apache.ambari.view.hive20.resources.browser.ConnectionService.attemptHiveConnection(ConnectionService.java:111) > at > org.apache.ambari.view.hive20.resources.browser.ConnectionService.attemptConnection(ConnectionService.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20573) Hive view 2.0 fails on LLAP
[ https://issues.apache.org/jira/browse/AMBARI-20573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20573: -- Status: Patch Available (was: Open) > Hive view 2.0 fails on LLAP > --- > > Key: AMBARI-20573 > URL: https://issues.apache.org/jira/browse/AMBARI-20573 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > Attachments: AMBARI-20573_branch-2.5.patch > > > Hive View 2.0.0 with default configuration fails with llap. > Ambari server logs show below failure > 22 Mar 2017 00:11:56,882 INFO [ambari-client-thread-30] ZooKeeper:684 - > Session: 0x25af27aae5a014f closed > 22 Mar 2017 00:11:56,882 INFO [ambari-client-thread-30-EventThread] > ClientCnxn:524 - EventThread shut down > 22 Mar 2017 00:11:56,894 ERROR [ambari-client-thread-30] > ContainerResponse:537 - Mapped exception to response: 500 (Internal Server > Error) > org.apache.ambari.view.hive20.utils.ServiceFormattedException > at > org.apache.ambari.view.hive20.resources.browser.ConnectionService.attemptHiveConnection(ConnectionService.java:111) > at > org.apache.ambari.view.hive20.resources.browser.ConnectionService.attemptConnection(ConnectionService.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20573) Hive view 2.0 fails on LLAP
[ https://issues.apache.org/jira/browse/AMBARI-20573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20573: -- Component/s: ambari-views > Hive view 2.0 fails on LLAP > --- > > Key: AMBARI-20573 > URL: https://issues.apache.org/jira/browse/AMBARI-20573 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > > Hive View 2.0.0 with default configuration fails with llap. > Ambari server logs show below failure > 22 Mar 2017 00:11:56,882 INFO [ambari-client-thread-30] ZooKeeper:684 - > Session: 0x25af27aae5a014f closed > 22 Mar 2017 00:11:56,882 INFO [ambari-client-thread-30-EventThread] > ClientCnxn:524 - EventThread shut down > 22 Mar 2017 00:11:56,894 ERROR [ambari-client-thread-30] > ContainerResponse:537 - Mapped exception to response: 500 (Internal Server > Error) > org.apache.ambari.view.hive20.utils.ServiceFormattedException > at > org.apache.ambari.view.hive20.resources.browser.ConnectionService.attemptHiveConnection(ConnectionService.java:111) > at > org.apache.ambari.view.hive20.resources.browser.ConnectionService.attemptConnection(ConnectionService.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20573) Hive view 2.0 fails on LLAP
Gaurav Nagar created AMBARI-20573: - Summary: Hive view 2.0 fails on LLAP Key: AMBARI-20573 URL: https://issues.apache.org/jira/browse/AMBARI-20573 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.1 Hive View 2.0.0 with default configuration fails with llap. Ambari server logs show below failure 22 Mar 2017 00:11:56,882 INFO [ambari-client-thread-30] ZooKeeper:684 - Session: 0x25af27aae5a014f closed 22 Mar 2017 00:11:56,882 INFO [ambari-client-thread-30-EventThread] ClientCnxn:524 - EventThread shut down 22 Mar 2017 00:11:56,894 ERROR [ambari-client-thread-30] ContainerResponse:537 - Mapped exception to response: 500 (Internal Server Error) org.apache.ambari.view.hive20.utils.ServiceFormattedException at org.apache.ambari.view.hive20.resources.browser.ConnectionService.attemptHiveConnection(ConnectionService.java:111) at org.apache.ambari.view.hive20.resources.browser.ConnectionService.attemptConnection(ConnectionService.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20558) HiveView does not work on WASB ACLs cluster
[ https://issues.apache.org/jira/browse/AMBARI-20558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20558: -- Attachment: AMBARI-20558_branch-2.5.patch > HiveView does not work on WASB ACLs cluster > --- > > Key: AMBARI-20558 > URL: https://issues.apache.org/jira/browse/AMBARI-20558 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > Attachments: AMBARI-20558_branch-2.5.patch > > > org.apache.hadoop.fs.azure.AzureException: > com.microsoft.azure.storage.StorageException: Encountered SASKeyGeneration > exception while generating SAS Key for container : inside Storage > account : > at > org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:1024) > at > org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.initialize(AzureNativeFileSystemStore.java:487) > at > org.apache.hadoop.fs.azure.NativeAzureFileSystem.initialize(NativeAzureFileSystem.java:1249) > at > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) > at > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829) > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811) > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390) > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:179) > at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:73) > at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:71) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866) > at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:400) > at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:71) > at > org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:150) > ... 104 more > Caused by: com.microsoft.azure.storage.StorageException: Encountered > SASKeyGeneration exception while generating SAS Key for container : > ambhviewl-ams26 inside Storage account : humbtesting101.blob.core.windows.net > at > org.apache.hadoop.fs.azure.SecureStorageInterfaceImpl.getContainerReference(SecureStorageInterfaceImpl.java:143) > at > org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.connectToAzureStorageInSecureMode(AzureNativeFileSystemStore.java:848) > at > org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:989) > ... 120 more > Caused by: org.apache.hadoop.fs.azure.SASKeyGenerationException: Encountered > IOException while building the HttpGetRequest to remote service > at > org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getContainerSASUri(RemoteSASKeyGeneratorImpl.java:185) > at > org.apache.hadoop.fs.azure.SecureStorageInterfaceImpl.getContainerReference(SecureStorageInterfaceImpl.java:135) > ... 122 more > Caused by: org.apache.hadoop.fs.azure.SASKeyGenerationException: > RemoteSASKeyGenerationResponse object null from remote call > at > org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getSASKey(RemoteSASKeyGeneratorImpl.java:257) > at > org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getContainerSASUri(RemoteSASKeyGeneratorImpl.java:179) > ... 123 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20558) HiveView does not work on WASB ACLs cluster
[ https://issues.apache.org/jira/browse/AMBARI-20558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20558: -- Status: Patch Available (was: Open) > HiveView does not work on WASB ACLs cluster > --- > > Key: AMBARI-20558 > URL: https://issues.apache.org/jira/browse/AMBARI-20558 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.1 > > Attachments: AMBARI-20558_branch-2.5.patch > > > org.apache.hadoop.fs.azure.AzureException: > com.microsoft.azure.storage.StorageException: Encountered SASKeyGeneration > exception while generating SAS Key for container : inside Storage > account : > at > org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:1024) > at > org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.initialize(AzureNativeFileSystemStore.java:487) > at > org.apache.hadoop.fs.azure.NativeAzureFileSystem.initialize(NativeAzureFileSystem.java:1249) > at > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) > at > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829) > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811) > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390) > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:179) > at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:73) > at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:71) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866) > at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:400) > at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:71) > at > org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:150) > ... 104 more > Caused by: com.microsoft.azure.storage.StorageException: Encountered > SASKeyGeneration exception while generating SAS Key for container : > ambhviewl-ams26 inside Storage account : humbtesting101.blob.core.windows.net > at > org.apache.hadoop.fs.azure.SecureStorageInterfaceImpl.getContainerReference(SecureStorageInterfaceImpl.java:143) > at > org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.connectToAzureStorageInSecureMode(AzureNativeFileSystemStore.java:848) > at > org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:989) > ... 120 more > Caused by: org.apache.hadoop.fs.azure.SASKeyGenerationException: Encountered > IOException while building the HttpGetRequest to remote service > at > org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getContainerSASUri(RemoteSASKeyGeneratorImpl.java:185) > at > org.apache.hadoop.fs.azure.SecureStorageInterfaceImpl.getContainerReference(SecureStorageInterfaceImpl.java:135) > ... 122 more > Caused by: org.apache.hadoop.fs.azure.SASKeyGenerationException: > RemoteSASKeyGenerationResponse object null from remote call > at > org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getSASKey(RemoteSASKeyGeneratorImpl.java:257) > at > org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getContainerSASUri(RemoteSASKeyGeneratorImpl.java:179) > ... 123 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20549) upgrade frontend-maven-plugin to latest >= 1.3 to make use of ignore proxy feature
[
https://issues.apache.org/jira/browse/AMBARI-20549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941883#comment-15941883
]
Gaurav Nagar commented on AMBARI-20549:
---
Committed to trunk.
> upgrade frontend-maven-plugin to latest >= 1.3 to make use of ignore proxy
> feature
> --
>
> Key: AMBARI-20549
> URL: https://issues.apache.org/jira/browse/AMBARI-20549
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin, ambari-views, ambari-web
>Affects Versions: 2.5.1
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20549.patch, AMBARI-20549-trunk.patch
>
>
> frontend-maven-plugin inherits maven settings.xml proxy values, in latest
> version >=1.3 proxy settings can be ignore by setting
> 'npmInheritsProxyConfigFromMaven' to 'false'
> REF: https://github.com/eirslett/frontend-maven-plugin/pull/387
> The following files contain the plugin
> {noformat}
> ambari-admin/pom.xml
> ambari-web/pom.xml
> contrib/views/capacity-scheduler/pom.xml
> contrib/views/files/pom.xml
> contrib/views/hawq/pom.xml
> contrib/views/hive-next/pom.xml
> contrib/views/hive20/pom.xml
> contrib/views/hueambarimigration/pom.xml
> contrib/views/jobs/pom.xml
> contrib/views/pig/pom.xml
> contrib/views/wfmanager/pom.xml
> contrib/views/wfmanager/src/main/resources/ui/pom.xml
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20563) Zeppelin : livy2 interpreter is not getting created by default
[ https://issues.apache.org/jira/browse/AMBARI-20563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941876#comment-15941876 ] Gaurav Nagar commented on AMBARI-20563: --- Committed to trunk. > Zeppelin : livy2 interpreter is not getting created by default > -- > > Key: AMBARI-20563 > URL: https://issues.apache.org/jira/browse/AMBARI-20563 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.1 >Reporter: Kshitij Badani >Assignee: Renjith Kamath > Fix For: 2.5.1 > > Attachments: AMBARI-20563-trunk-v1.patch > > > Whenever Spark2 and Livy2 is installed on the cluster, I can see only Spark2 > interpreter getting created in Zeppelin and not the Livy2 interpreter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20539) Interpreters that are not listed under "zeppelin.interpreter.group.order" in zeppelin-site.xml should not get installed
[ https://issues.apache.org/jira/browse/AMBARI-20539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940434#comment-15940434 ] Gaurav Nagar commented on AMBARI-20539: --- Committed to trunk > Interpreters that are not listed under "zeppelin.interpreter.group.order" in > zeppelin-site.xml should not get installed > --- > > Key: AMBARI-20539 > URL: https://issues.apache.org/jira/browse/AMBARI-20539 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.1 > > Attachments: AMBARI-20539_trunk_v1.patch > > > Interpreters that are not listed under "zeppelin.interpreter.group.order" in > zeppelin-site.xml should not get installed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20558) HiveView does not work on WASB ACLs cluster
[ https://issues.apache.org/jira/browse/AMBARI-20558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20558: -- Description: org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException: Encountered SASKeyGeneration exception while generating SAS Key for container : inside Storage account : at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:1024) at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.initialize(AzureNativeFileSystemStore.java:487) at org.apache.hadoop.fs.azure.NativeAzureFileSystem.initialize(NativeAzureFileSystem.java:1249) at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829) at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:179) at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:73) at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:71) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866) at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:400) at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:71) at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:150) ... 104 more Caused by: com.microsoft.azure.storage.StorageException: Encountered SASKeyGeneration exception while generating SAS Key for container : ambhviewl-ams26 inside Storage account : humbtesting101.blob.core.windows.net at org.apache.hadoop.fs.azure.SecureStorageInterfaceImpl.getContainerReference(SecureStorageInterfaceImpl.java:143) at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.connectToAzureStorageInSecureMode(AzureNativeFileSystemStore.java:848) at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:989) ... 120 more Caused by: org.apache.hadoop.fs.azure.SASKeyGenerationException: Encountered IOException while building the HttpGetRequest to remote service at org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getContainerSASUri(RemoteSASKeyGeneratorImpl.java:185) at org.apache.hadoop.fs.azure.SecureStorageInterfaceImpl.getContainerReference(SecureStorageInterfaceImpl.java:135) ... 122 more Caused by: org.apache.hadoop.fs.azure.SASKeyGenerationException: RemoteSASKeyGenerationResponse object null from remote call at org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getSASKey(RemoteSASKeyGeneratorImpl.java:257) at org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getContainerSASUri(RemoteSASKeyGeneratorImpl.java:179) ... 123 more was: org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException: Encountered SASKeyGeneration exception while generating SAS Key for container : ambhviewl-ams26 inside Storage account : humbtesting101.blob.core.windows.net at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:1024) at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.initialize(AzureNativeFileSystemStore.java:487) at org.apache.hadoop.fs.azure.NativeAzureFileSystem.initialize(NativeAzureFileSystem.java:1249) at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829) at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:179) at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:73) at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:71) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866) at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:400) at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:71) at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:150) ... 104 more Caused by:
[jira] [Created] (AMBARI-20558) HiveView does not work on WASB ACLs cluster
Gaurav Nagar created AMBARI-20558: - Summary: HiveView does not work on WASB ACLs cluster Key: AMBARI-20558 URL: https://issues.apache.org/jira/browse/AMBARI-20558 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.1 org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException: Encountered SASKeyGeneration exception while generating SAS Key for container : ambhviewl-ams26 inside Storage account : humbtesting101.blob.core.windows.net at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:1024) at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.initialize(AzureNativeFileSystemStore.java:487) at org.apache.hadoop.fs.azure.NativeAzureFileSystem.initialize(NativeAzureFileSystem.java:1249) at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795) at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99) at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829) at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:179) at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:73) at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:71) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866) at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:400) at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:71) at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:150) ... 104 more Caused by: com.microsoft.azure.storage.StorageException: Encountered SASKeyGeneration exception while generating SAS Key for container : ambhviewl-ams26 inside Storage account : humbtesting101.blob.core.windows.net at org.apache.hadoop.fs.azure.SecureStorageInterfaceImpl.getContainerReference(SecureStorageInterfaceImpl.java:143) at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.connectToAzureStorageInSecureMode(AzureNativeFileSystemStore.java:848) at org.apache.hadoop.fs.azure.AzureNativeFileSystemStore.createAzureStorageSession(AzureNativeFileSystemStore.java:989) ... 120 more Caused by: org.apache.hadoop.fs.azure.SASKeyGenerationException: Encountered IOException while building the HttpGetRequest to remote service at org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getContainerSASUri(RemoteSASKeyGeneratorImpl.java:185) at org.apache.hadoop.fs.azure.SecureStorageInterfaceImpl.getContainerReference(SecureStorageInterfaceImpl.java:135) ... 122 more Caused by: org.apache.hadoop.fs.azure.SASKeyGenerationException: RemoteSASKeyGenerationResponse object null from remote call at org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getSASKey(RemoteSASKeyGeneratorImpl.java:257) at org.apache.hadoop.fs.azure.RemoteSASKeyGeneratorImpl.getContainerSASUri(RemoteSASKeyGeneratorImpl.java:179) ... 123 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20492) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
[ https://issues.apache.org/jira/browse/AMBARI-20492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20492: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues > -- > > Key: AMBARI-20492 > URL: https://issues.apache.org/jira/browse/AMBARI-20492 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20492_branch-2.5.patch, Screen Shot 2017-02-13 at > 1.23.56 PM.png > > > Ambari URL:- > http://:8080/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > Knox proxy enabled for Ambari:- > https://:8443/gateway/ui/ambari/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > steps to reproduce:- > 1- Configure Knox Proxy for Ambari. > create ui.xml in /usr/hdp/current/knox-server/conf/topologies > Note:- I have already deployed ui.xml topology in this path. There is no Knox > restart required. > Attached is ui.xml > 2- Invoke Ambari through knox proxy > https://:8443/gateway/ui/ambari/#/login > 3- Click on hive2.0 view > Notice all the service checks failed messages. Attached is screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20492) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
[ https://issues.apache.org/jira/browse/AMBARI-20492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20492: -- Status: Patch Available (was: Open) > Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues > -- > > Key: AMBARI-20492 > URL: https://issues.apache.org/jira/browse/AMBARI-20492 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20492_branch-2.5.patch, Screen Shot 2017-02-13 at > 1.23.56 PM.png > > > Ambari URL:- > http://:8080/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > Knox proxy enabled for Ambari:- > https://:8443/gateway/ui/ambari/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > steps to reproduce:- > 1- Configure Knox Proxy for Ambari. > create ui.xml in /usr/hdp/current/knox-server/conf/topologies > Note:- I have already deployed ui.xml topology in this path. There is no Knox > restart required. > Attached is ui.xml > 2- Invoke Ambari through knox proxy > https://:8443/gateway/ui/ambari/#/login > 3- Click on hive2.0 view > Notice all the service checks failed messages. Attached is screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20492) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
[ https://issues.apache.org/jira/browse/AMBARI-20492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20492: -- Attachment: AMBARI-20492_branch-2.5.patch > Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues > -- > > Key: AMBARI-20492 > URL: https://issues.apache.org/jira/browse/AMBARI-20492 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20492_branch-2.5.patch, Screen Shot 2017-02-13 at > 1.23.56 PM.png > > > Ambari URL:- > http://:8080/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > Knox proxy enabled for Ambari:- > https://:8443/gateway/ui/ambari/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > steps to reproduce:- > 1- Configure Knox Proxy for Ambari. > create ui.xml in /usr/hdp/current/knox-server/conf/topologies > Note:- I have already deployed ui.xml topology in this path. There is no Knox > restart required. > Attached is ui.xml > 2- Invoke Ambari through knox proxy > https://:8443/gateway/ui/ambari/#/login > 3- Click on hive2.0 view > Notice all the service checks failed messages. Attached is screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20492) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
[ https://issues.apache.org/jira/browse/AMBARI-20492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20492: -- Attachment: Screen Shot 2017-02-13 at 1.23.56 PM.png > Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues > -- > > Key: AMBARI-20492 > URL: https://issues.apache.org/jira/browse/AMBARI-20492 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: Screen Shot 2017-02-13 at 1.23.56 PM.png > > > Ambari URL:- > http://:8080/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > Knox proxy enabled for Ambari:- > https://:8443/gateway/ui/ambari/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > steps to reproduce:- > 1- Configure Knox Proxy for Ambari. > create ui.xml in /usr/hdp/current/knox-server/conf/topologies > Note:- I have already deployed ui.xml topology in this path. There is no Knox > restart required. > Attached is ui.xml > 2- Invoke Ambari through knox proxy > https://:8443/gateway/ui/ambari/#/login > 3- Click on hive2.0 view > Notice all the service checks failed messages. Attached is screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20492) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
[ https://issues.apache.org/jira/browse/AMBARI-20492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20492: -- Description: Ambari URL:- http://:8080/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE Knox proxy enabled for Ambari:- https://:8443/gateway/ui/ambari/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE steps to reproduce:- 1- Configure Knox Proxy for Ambari. create ui.xml in /usr/hdp/current/knox-server/conf/topologies Note:- I have already deployed ui.xml topology in this path. There is no Knox restart required. Attached is ui.xml 2- Invoke Ambari through knox proxy https://:8443/gateway/ui/ambari/#/login 3- Click on hive2.0 view Notice all the service checks failed messages. Attached is screenshot > Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues > -- > > Key: AMBARI-20492 > URL: https://issues.apache.org/jira/browse/AMBARI-20492 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > > Ambari URL:- > http://:8080/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > Knox proxy enabled for Ambari:- > https://:8443/gateway/ui/ambari/#/main/views/HIVE/2.0.0/AUTO_HIVE20_INSTANCE > steps to reproduce:- > 1- Configure Knox Proxy for Ambari. > create ui.xml in /usr/hdp/current/knox-server/conf/topologies > Note:- I have already deployed ui.xml topology in this path. There is no Knox > restart required. > Attached is ui.xml > 2- Invoke Ambari through knox proxy > https://:8443/gateway/ui/ambari/#/login > 3- Click on hive2.0 view > Notice all the service checks failed messages. Attached is screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20492) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
Gaurav Nagar created AMBARI-20492: - Summary: Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues Key: AMBARI-20492 URL: https://issues.apache.org/jira/browse/AMBARI-20492 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20337) Need to show timer while loading coordinator name while bundle creation
[ https://issues.apache.org/jira/browse/AMBARI-20337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20337: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Need to show timer while loading coordinator name while bundle creation > --- > > Key: AMBARI-20337 > URL: https://issues.apache.org/jira/browse/AMBARI-20337 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20337_trunk.patch > > > Need to show timer while loading coordinator name while bundle creation. > Issue 1 : Some times coordinator name is not fetch even after 5secs. So its > better to show timer to indicate that name is getting loaded. > Issue 2: If user provides invalid coordinator path, then appropriate error > message should be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20353) Log error while importing the workflow from encrypted path
[ https://issues.apache.org/jira/browse/AMBARI-20353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20353: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Log error while importing the workflow from encrypted path > -- > > Key: AMBARI-20353 > URL: https://issues.apache.org/jira/browse/AMBARI-20353 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20353_trunk.patch > > > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/tmp/encrypt/workflow.xml=WORKFLOW > is failing with 500 status code. > Steps to reproduce : > Try to import workflow /tmp/encrypt/workflow.xml and its failing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
[ https://issues.apache.org/jira/browse/AMBARI-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20342: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > WFM:Performance improvement for adding node on a decision node in large > workflow. > - > > Key: AMBARI-20342 > URL: https://issues.apache.org/jira/browse/AMBARI-20342 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20342_trunk.patch > > > Performance improvement on adding node to large workflow on lower part of > decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20296) Workflow Manger support for pointing to kill node in decision editor.
[ https://issues.apache.org/jira/browse/AMBARI-20296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20296: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Workflow Manger support for pointing to kill node in decision editor. > -- > > Key: AMBARI-20296 > URL: https://issues.apache.org/jira/browse/AMBARI-20296 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20296_trunk.patch > > > Workflow Manger support for pointing to kill node in decision editor.. > In decision editor , the user should be able to point to a different node for > a condition than the pre configured ones. > Also in case of condition-node combination pointing to an structural error in > workflow, user should be warned . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20247) Show full error while importing the workflow from encrypted file
[ https://issues.apache.org/jira/browse/AMBARI-20247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20247: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Show full error while importing the workflow from encrypted file > > > Key: AMBARI-20247 > URL: https://issues.apache.org/jira/browse/AMBARI-20247 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20247_trunk.patch > > > Live cluster : > https://172.22.98.248:8443/#/main/views/WORKFLOW_MANAGER/1.0.0/WFM > Facing issue while importing workflow where api > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/user/hrt_qa/test_WfKillSubwf1/workflow.xml=WORKFLOW > is failing with 500 status code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20293) WFM FS editor needs to maintain order of FS operations.
[ https://issues.apache.org/jira/browse/AMBARI-20293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20293: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > WFM FS editor needs to maintain order of FS operations. > --- > > Key: AMBARI-20293 > URL: https://issues.apache.org/jira/browse/AMBARI-20293 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Belliraj HB > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20293_trunk.patch > > > WFM FS editor needs to maintain order of FS operations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20299) The Migrated Query Status "UNKNOWN" is to be replaced by original status as per hue query execution
[ https://issues.apache.org/jira/browse/AMBARI-20299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20299: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > The Migrated Query Status "UNKNOWN" is to be replaced by original status as > per hue query execution > --- > > Key: AMBARI-20299 > URL: https://issues.apache.org/jira/browse/AMBARI-20299 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20299.patch > > > The status of the migrated queries for hive history migration are "UNKNOWN". > They need to be set to their Hue corresponding status -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20121) Hue Migration Tool: param values getting cached
[ https://issues.apache.org/jira/browse/AMBARI-20121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20121: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Hue Migration Tool: param values getting cached > --- > > Key: AMBARI-20121 > URL: https://issues.apache.org/jira/browse/AMBARI-20121 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-20121.patch > > > When navigating away from a route the values are getting cached on returning > to the route which is causing unexpected migrations > hiveView15 is an instance of hive-view version1.5 > hiveView20 is an instance of hive-view version2.0 > 1. Migrate the Hive-history queries (user admin,instance hiveView15,startdate > :2017-02-21,enddate:2017-02-22) > 2. Migrate the Hive-saved queries (user admin,instance hiveView15,startdate > :2017-02-21,enddate:2017-02-22) > 3. Migrate the Hive-history queries (user admin,instance hiveView20,startdate > :2017-02-21,enddate:2017-02-22) **different instanceName > But The UI shows migration to "hiveView20" happened twice. It uses the > previously cached value in 'admin' for the variable 'username' for migrating > artifacts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20268) WFM generates duplicate kill nodes in XML if decision paths have multiple transition to kill node.
[ https://issues.apache.org/jira/browse/AMBARI-20268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar resolved AMBARI-20268. --- Resolution: Fixed Committed to branch-2.5 and trunk. > WFM generates duplicate kill nodes in XML if decision paths have multiple > transition to kill node. > -- > > Key: AMBARI-20268 > URL: https://issues.apache.org/jira/browse/AMBARI-20268 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20268_trunk.patch > > > The generate XML contains duplicate kill nodes if decision paths have > multiple transition to kill node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20266) Duplicate node error is shown if kill node transition exists from decision node in WFM
[ https://issues.apache.org/jira/browse/AMBARI-20266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20266: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Duplicate node error is shown if kill node transition exists from decision > node in WFM > -- > > Key: AMBARI-20266 > URL: https://issues.apache.org/jira/browse/AMBARI-20266 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20266_trunk.patch > > > If there's a transition to kill node from a decision node, node already > exists error is shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20206) Workflow manager is allowing to have empty action node
[ https://issues.apache.org/jira/browse/AMBARI-20206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20206: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Workflow manager is allowing to have empty action node > -- > > Key: AMBARI-20206 > URL: https://issues.apache.org/jira/browse/AMBARI-20206 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20206_trunk.patch > > > Workflow manager is allowing to have empty action node. > Steps to reproduce : > 1) Add a new node to the workflow > 2) Delete node name and keep it empty. > 3) Workflow manager is not complaining about empty node name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20131) Workflow details are lost upon refreshing the browser
[ https://issues.apache.org/jira/browse/AMBARI-20131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20131: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Workflow details are lost upon refreshing the browser > - > > Key: AMBARI-20131 > URL: https://issues.apache.org/jira/browse/AMBARI-20131 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20131_trunk.patch > > > Workflow details are lost upon refreshing the browser. > Steps to reproduce : > 1) Create a new workflow. > 2) Now refresh the browser. > 3) Upon refreshing, the previous workflow tab is not displayed and all the > unsaved works are lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20246) Not able to preview the xml for coordinator
[ https://issues.apache.org/jira/browse/AMBARI-20246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20246: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Not able to preview the xml for coordinator > --- > > Key: AMBARI-20246 > URL: https://issues.apache.org/jira/browse/AMBARI-20246 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Blocker > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20246_trunk.patch > > > Issue 1: > Not able to preview the xml for coordinator. I am not seeing any error in UI > console log. > Steps to reproduce : > 1) Import the coordinator. > 2) Import the coordinator. > 3) Try to preview the coordinator and UI is not showing preview. > Issue 2: > After issue 1 is encountered, if user tries to perform any other operations, > then UI is getting hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20236) HiveView 2.0: save as HDFS shows success message on error
[
https://issues.apache.org/jira/browse/AMBARI-20236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20236:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5 and trunk.
> HiveView 2.0: save as HDFS shows success message on error
> -
>
> Key: AMBARI-20236
> URL: https://issues.apache.org/jira/browse/AMBARI-20236
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20236_branch-2.5.patch
>
>
> {code:java}
> Caused by:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
> Permission denied: user=admin, access=WRITE,
> inode="/d1/d1.csv":hdfs:hdfs:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1955)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1939)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1922)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInternal(FSNamesystem.java:2736)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:2671)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:2555)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:735)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:408)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2351)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2347)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1833)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2345)
> at
> org.apache.hadoop.hdfs.web.JsonUtil.toRemoteException(JsonUtil.java:118)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.validateResponse(WebHdfsFileSystem.java:480)
> ... 8 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20236) HiveView 2.0: save as HDFS shows success message on error
[
https://issues.apache.org/jira/browse/AMBARI-20236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20236:
--
Status: Patch Available (was: Open)
> HiveView 2.0: save as HDFS shows success message on error
> -
>
> Key: AMBARI-20236
> URL: https://issues.apache.org/jira/browse/AMBARI-20236
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20236_branch-2.5.patch
>
>
> {code:java}
> Caused by:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
> Permission denied: user=admin, access=WRITE,
> inode="/d1/d1.csv":hdfs:hdfs:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1955)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1939)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1922)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInternal(FSNamesystem.java:2736)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:2671)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:2555)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:735)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:408)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2351)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2347)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1833)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2345)
> at
> org.apache.hadoop.hdfs.web.JsonUtil.toRemoteException(JsonUtil.java:118)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.validateResponse(WebHdfsFileSystem.java:480)
> ... 8 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20204) Huemigration View not working with Oracle Db(Single cluster)
[ https://issues.apache.org/jira/browse/AMBARI-20204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20204: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Huemigration View not working with Oracle Db(Single cluster) > > > Key: AMBARI-20204 > URL: https://issues.apache.org/jira/browse/AMBARI-20204 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-20204.patch, Screen Shot 2017-02-23 at 2.59.09 > PM.png > > > The Hue-Server and Ambari-server has been setup on oracle DB. > Instance Names are not visible In hue-migration view. > The Rest Api is also returning null. > After resolving this other issues persist like Class not overrided for oracle > correctly for pig and hive, timestamp insertion to ambari database incorrect, > no support for Hive later versions and date format wrong for fetching Hue > queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20204) Huemigration View not working with Oracle Db(Single cluster)
[ https://issues.apache.org/jira/browse/AMBARI-20204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20204: -- Fix Version/s: (was: trunk) 2.5.0 > Huemigration View not working with Oracle Db(Single cluster) > > > Key: AMBARI-20204 > URL: https://issues.apache.org/jira/browse/AMBARI-20204 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20204.patch, Screen Shot 2017-02-23 at 2.59.09 > PM.png > > > The Hue-Server and Ambari-server has been setup on oracle DB. > Instance Names are not visible In hue-migration view. > The Rest Api is also returning null. > After resolving this other issues persist like Class not overrided for oracle > correctly for pig and hive, timestamp insertion to ambari database incorrect, > no support for Hive later versions and date format wrong for fetching Hue > queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20236) HiveView 2.0: save as HDFS shows success message on error
[
https://issues.apache.org/jira/browse/AMBARI-20236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20236:
--
Attachment: AMBARI-20236_branch-2.5.patch
> HiveView 2.0: save as HDFS shows success message on error
> -
>
> Key: AMBARI-20236
> URL: https://issues.apache.org/jira/browse/AMBARI-20236
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anusha Bilgi
>Assignee: Gaurav Nagar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20236_branch-2.5.patch
>
>
> {code:java}
> Caused by:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
> Permission denied: user=admin, access=WRITE,
> inode="/d1/d1.csv":hdfs:hdfs:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1955)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1939)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1922)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInternal(FSNamesystem.java:2736)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:2671)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:2555)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:735)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:408)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2351)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2347)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1833)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2345)
> at
> org.apache.hadoop.hdfs.web.JsonUtil.toRemoteException(JsonUtil.java:118)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.validateResponse(WebHdfsFileSystem.java:480)
> ... 8 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20222) Hive View 2.0 LogAggregator prints lots of warning logs.
[
https://issues.apache.org/jira/browse/AMBARI-20222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20222:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5 and trunk.
> Hive View 2.0 LogAggregator prints lots of warning logs.
>
>
> Key: AMBARI-20222
> URL: https://issues.apache.org/jira/browse/AMBARI-20222
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.5.0
>
> Attachments: AMBARI-20222_branch-2.5.patch
>
>
> In Hive view log, there are lot of warning logs
> {code:java}
> 24 Feb 2017 11:39:20,180 WARN
> [HiveViewActorSystem-akka.actor.misc-dispatcher-26] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] LogAggregator:75 - SQL Error while getting logs. Tried
> writing to: /user/admin/hive/jobs/hive-job-315-2017-02-24_11-39/logs.
> Exception: Method getQueryLog() failed. The statement has been closed or
> cancelled.
> 24 Feb 2017 11:39:25,180 WARN
> [HiveViewActorSystem-akka.actor.misc-dispatcher-26] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] LogAggregator:75 - SQL Error while getting logs. Tried
> writing to: /user/admin/hive/jobs/hive-job-315-2017-02-24_11-39/logs.
> Exception: Method getQueryLog() failed. The statement has been closed or
> cancelled.
> {code}
> These logs need to supressed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20224) HiveView2.0: Logs tab is always empty
[ https://issues.apache.org/jira/browse/AMBARI-20224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20224: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > HiveView2.0: Logs tab is always empty > - > > Key: AMBARI-20224 > URL: https://issues.apache.org/jira/browse/AMBARI-20224 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20224_branch-2.5.patch > > > Logs tab is always empty. Get logs ajax call is failing with 404 because of > *//* in url > http://c6401.ambari.apache.org:8080/api/v1/views/HIVE/versions/2.0.0/instances/AUTO_HIVE20_INSTANCE/resources//files/user/admin/hive/jobs/hive-job-506-2017-02-28_06-15/logs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20223) Hive view 2.0 Fetch stats doesn't work when you point against LLAP
[ https://issues.apache.org/jira/browse/AMBARI-20223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20223: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Hive view 2.0 Fetch stats doesn't work when you point against LLAP > -- > > Key: AMBARI-20223 > URL: https://issues.apache.org/jira/browse/AMBARI-20223 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20223_branch-2.5.patch > > > In Hive View 2.0 Fetch column stats does not work when using LLAP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20224) HiveView2.0: Logs tab is always empty
[ https://issues.apache.org/jira/browse/AMBARI-20224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20224: -- Status: Patch Available (was: Open) > HiveView2.0: Logs tab is always empty > - > > Key: AMBARI-20224 > URL: https://issues.apache.org/jira/browse/AMBARI-20224 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20224_branch-2.5.patch > > > Logs tab is always empty. Get logs ajax call is failing with 404 because of > *//* in url > http://c6401.ambari.apache.org:8080/api/v1/views/HIVE/versions/2.0.0/instances/AUTO_HIVE20_INSTANCE/resources//files/user/admin/hive/jobs/hive-job-506-2017-02-28_06-15/logs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20224) HiveView2.0: Logs tab is always empty
[ https://issues.apache.org/jira/browse/AMBARI-20224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20224: -- Attachment: AMBARI-20224_branch-2.5.patch > HiveView2.0: Logs tab is always empty > - > > Key: AMBARI-20224 > URL: https://issues.apache.org/jira/browse/AMBARI-20224 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20224_branch-2.5.patch > > > Logs tab is always empty. Get logs ajax call is failing with 404 because of > *//* in url > http://c6401.ambari.apache.org:8080/api/v1/views/HIVE/versions/2.0.0/instances/AUTO_HIVE20_INSTANCE/resources//files/user/admin/hive/jobs/hive-job-506-2017-02-28_06-15/logs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20224) HiveView2.0: Logs tab is always empty
Gaurav Nagar created AMBARI-20224: - Summary: HiveView2.0: Logs tab is always empty Key: AMBARI-20224 URL: https://issues.apache.org/jira/browse/AMBARI-20224 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.0 Logs tab is always empty. Get logs ajax call is failing with 404 because of *//* in url http://c6401.ambari.apache.org:8080/api/v1/views/HIVE/versions/2.0.0/instances/AUTO_HIVE20_INSTANCE/resources//files/user/admin/hive/jobs/hive-job-506-2017-02-28_06-15/logs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20173) DB selected is not persisted while switching between tabs,SavedQuery tab does not show preview, if the query is not executed before saving
[ https://issues.apache.org/jira/browse/AMBARI-20173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20173: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > DB selected is not persisted while switching between tabs,SavedQuery tab does > not show preview, if the query is not executed before saving > -- > > Key: AMBARI-20173 > URL: https://issues.apache.org/jira/browse/AMBARI-20173 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20173.branch-2.5.patch > > > 1.Create an worksheet and select a database called "Default". > 2.Create another worksheet and select another database "Sample". > 3.Switch between the worksheets and the database selection will not be > persisted across the worksheets > SavedQuery tab does not show preview, if the query is not executed before > saving: > If the query is not executed before saving, preview is not being shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20223) Hive view 2.0 Fetch stats doesn't work when you point against LLAP
[ https://issues.apache.org/jira/browse/AMBARI-20223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20223: -- Attachment: AMBARI-20223_branch-2.5.patch > Hive view 2.0 Fetch stats doesn't work when you point against LLAP > -- > > Key: AMBARI-20223 > URL: https://issues.apache.org/jira/browse/AMBARI-20223 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20223_branch-2.5.patch > > > In Hive View 2.0 Fetch column stats does not work when using LLAP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20223) Hive view 2.0 Fetch stats doesn't work when you point against LLAP
[ https://issues.apache.org/jira/browse/AMBARI-20223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20223: -- Status: Patch Available (was: Open) > Hive view 2.0 Fetch stats doesn't work when you point against LLAP > -- > > Key: AMBARI-20223 > URL: https://issues.apache.org/jira/browse/AMBARI-20223 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > > In Hive View 2.0 Fetch column stats does not work when using LLAP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20223) Hive view 2.0 Fetch stats doesn't work when you point against LLAP
Gaurav Nagar created AMBARI-20223: - Summary: Hive view 2.0 Fetch stats doesn't work when you point against LLAP Key: AMBARI-20223 URL: https://issues.apache.org/jira/browse/AMBARI-20223 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.0 In Hive View 2.0 Fetch column stats does not work when using LLAP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20222) Hive View 2.0 LogAggregator prints lots of warning logs.
[
https://issues.apache.org/jira/browse/AMBARI-20222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20222:
--
Attachment: AMBARI-20222_branch-2.5.patch
> Hive View 2.0 LogAggregator prints lots of warning logs.
>
>
> Key: AMBARI-20222
> URL: https://issues.apache.org/jira/browse/AMBARI-20222
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.5.0
>
> Attachments: AMBARI-20222_branch-2.5.patch
>
>
> In Hive view log, there are lot of warning logs
> {code:java}
> 24 Feb 2017 11:39:20,180 WARN
> [HiveViewActorSystem-akka.actor.misc-dispatcher-26] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] LogAggregator:75 - SQL Error while getting logs. Tried
> writing to: /user/admin/hive/jobs/hive-job-315-2017-02-24_11-39/logs.
> Exception: Method getQueryLog() failed. The statement has been closed or
> cancelled.
> 24 Feb 2017 11:39:25,180 WARN
> [HiveViewActorSystem-akka.actor.misc-dispatcher-26] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] LogAggregator:75 - SQL Error while getting logs. Tried
> writing to: /user/admin/hive/jobs/hive-job-315-2017-02-24_11-39/logs.
> Exception: Method getQueryLog() failed. The statement has been closed or
> cancelled.
> {code}
> These logs need to supressed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20222) Hive View 2.0 LogAggregator prints lots of warning logs.
[
https://issues.apache.org/jira/browse/AMBARI-20222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20222:
--
Status: Patch Available (was: Open)
> Hive View 2.0 LogAggregator prints lots of warning logs.
>
>
> Key: AMBARI-20222
> URL: https://issues.apache.org/jira/browse/AMBARI-20222
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.5.0
>
> Attachments: AMBARI-20222_branch-2.5.patch
>
>
> In Hive view log, there are lot of warning logs
> {code:java}
> 24 Feb 2017 11:39:20,180 WARN
> [HiveViewActorSystem-akka.actor.misc-dispatcher-26] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] LogAggregator:75 - SQL Error while getting logs. Tried
> writing to: /user/admin/hive/jobs/hive-job-315-2017-02-24_11-39/logs.
> Exception: Method getQueryLog() failed. The statement has been closed or
> cancelled.
> 24 Feb 2017 11:39:25,180 WARN
> [HiveViewActorSystem-akka.actor.misc-dispatcher-26] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] LogAggregator:75 - SQL Error while getting logs. Tried
> writing to: /user/admin/hive/jobs/hive-job-315-2017-02-24_11-39/logs.
> Exception: Method getQueryLog() failed. The statement has been closed or
> cancelled.
> {code}
> These logs need to supressed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20222) Hive View 2.0 LogAggregator prints lots of warning logs.
Gaurav Nagar created AMBARI-20222:
-
Summary: Hive View 2.0 LogAggregator prints lots of warning logs.
Key: AMBARI-20222
URL: https://issues.apache.org/jira/browse/AMBARI-20222
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
Fix For: 2.5.0
In Hive view log, there are lot of warning logs
{code:java}
24 Feb 2017 11:39:20,180 WARN
[HiveViewActorSystem-akka.actor.misc-dispatcher-26] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] LogAggregator:75 - SQL Error while getting logs. Tried
writing to: /user/admin/hive/jobs/hive-job-315-2017-02-24_11-39/logs.
Exception: Method getQueryLog() failed. The statement has been closed or
cancelled.
24 Feb 2017 11:39:25,180 WARN
[HiveViewActorSystem-akka.actor.misc-dispatcher-26] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] LogAggregator:75 - SQL Error while getting logs. Tried
writing to: /user/admin/hive/jobs/hive-job-315-2017-02-24_11-39/logs.
Exception: Method getQueryLog() failed. The statement has been closed or
cancelled.
{code}
These logs need to supressed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20132) All the workflow details are getting logged in UI console log
[ https://issues.apache.org/jira/browse/AMBARI-20132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20132: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > All the workflow details are getting logged in UI console log > - > > Key: AMBARI-20132 > URL: https://issues.apache.org/jira/browse/AMBARI-20132 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Belliraj HB > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20132_trunk.patch > > > All the workflow details are getting logged in UI console log. > Is this logging necessary ? Whether it will have performance implications in > rendering the workflow ? > Steps to reproduce : > 1) Create a workflow. > 2) Refresh the browser. > 3) While loading the workflow, all the details are being logged in the UI > console log -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20142) Job Link URL not working
[ https://issues.apache.org/jira/browse/AMBARI-20142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20142: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Job Link URL not working > > > Key: AMBARI-20142 > URL: https://issues.apache.org/jira/browse/AMBARI-20142 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20142_trunk.patch > > > Please give details and possible attach screen shots to clearly show what > went wrong. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20167) importing from workflow from the coordinator setup hangs
[ https://issues.apache.org/jira/browse/AMBARI-20167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20167: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > importing from workflow from the coordinator setup hangs > > > Key: AMBARI-20167 > URL: https://issues.apache.org/jira/browse/AMBARI-20167 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20167_trunk.patch > > > Importing from workflow from the coordinator setup hangs > IMPACT: Users do not know what to do next. > STEPS TO REPRODUCE: > log into a WFM and create a workflow and then create coordinator > Add the path to the workflow for the coordinator, > give it bad path and click on the import workflow > It should validate the path before it tries to load it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20166) Workflow Manager. Nominal time should accept variables.
[ https://issues.apache.org/jira/browse/AMBARI-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20166: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Workflow Manager. Nominal time should accept variables. > --- > > Key: AMBARI-20166 > URL: https://issues.apache.org/jira/browse/AMBARI-20166 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20166_trunk.patch > > > Workflow Manager. Nominal time should accept variables. > currently nominal time accepts time only from date picker. it should allow > user to enter variables as wel. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20164) Kill a workflow jumps to another tab in WFM
[ https://issues.apache.org/jira/browse/AMBARI-20164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20164: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Kill a workflow jumps to another tab in WFM > --- > > Key: AMBARI-20164 > URL: https://issues.apache.org/jira/browse/AMBARI-20164 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20164_trunk.patch > > > Steps: > 1. log into ambari ui > 2. go to wfm > 3. select an existing workflow. e.g.Workflow10 > 4. choose edit workflow > 5. choose the "dashboard" tab to go back to the workflow list > 6. select the existing workflow and choose "action->kill" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20141) Command text lost when toggling from Command to Args on sqoop in Workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20141: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Command text lost when toggling from Command to Args on sqoop in Workflow > manager. > -- > > Key: AMBARI-20141 > URL: https://issues.apache.org/jira/browse/AMBARI-20141 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20141_trunk.patch > > > Command text lost when toggling from Command to Args on sqoop action. > Pressing cancel and opening the configure dialog again restores the settings > but this is inconvenient if you had several changes or you haven’t saved the > settings yet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20161) Workflow Manager-mapred action contains duplicates in editor if user saves and reopens editor
[ https://issues.apache.org/jira/browse/AMBARI-20161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20161: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Workflow Manager-mapred action contains duplicates in editor if user saves > and reopens editor > - > > Key: AMBARI-20161 > URL: https://issues.apache.org/jira/browse/AMBARI-20161 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20161_trunk.patch > > > Open a Map-Red editor. > Fill in details and Save. > Reopen the editor. you will see the configuration in both general and > advanced section. > Preview xml looks fine though. > Expected: > the configuration should be not duplicated. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20050) Issue while importing workflow with insufficient permissions
[ https://issues.apache.org/jira/browse/AMBARI-20050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20050: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Issue while importing workflow with insufficient permissions > > > Key: AMBARI-20050 > URL: https://issues.apache.org/jira/browse/AMBARI-20050 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: M Madhan Mohan Reddy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20050_trunk.patch > > > Facing Issue while importing workflow with insufficient permissions. Though > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflowDetail?workflowXmlPath=/user/admin/new/email.xml > is failed with 500 code, its not been handled on the UI. > UI is stuck in import phase. > Steps to reproduce : > 1) Login as user1 and submit workflow and save to hdfs location /user/user1 > 2) Now login as user2 who doesn't have access to /user/user1 . > Now user2 can view the workflow status in the dashboard. > 3) Click on edit workflow and try to navigate to designer page. > 4) Due to lack of permission, user is not allowed to import the workflow and > UI is not handling this error. > This should be properly handled on the UI and appropriate error message need > to be displayed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20137) File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20137: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE > 11 > > > Key: AMBARI-20137 > URL: https://issues.apache.org/jira/browse/AMBARI-20137 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20137_branch-2.5.patch > > > ROBLEM: > The Ambari File View -> Upload, does not work anymore in Chrome 56.0.2924.87 > and IE 11 > The error message is: Currently supports single file upload > STEPS TO REPRODUCE: > root@node1 ~# ambari-server --hash > 503aa9809d4890e6c54b219fda1aa3444dbb5597 > root@node1 ~# ambari-server --version > 2.4.2.0-136 > My cluster is the default HDP 2.5.3 installation. > 1) Upgrade to Chrome 56.0.2924.87 (or use IE 11). > 2) Open Ambari Views -> File View. > 3) Create a file called "x.sh" and select to upload it > 4) The operation fails with: "Currently supports single file upload" > Opening the Chrome Developer, shows the error: > "Cannot add a directory." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135.1_branch-2.5.patch, > AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20137) File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20137: -- Attachment: AMBARI-20137_branch-2.5.patch > File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE > 11 > > > Key: AMBARI-20137 > URL: https://issues.apache.org/jira/browse/AMBARI-20137 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20137_branch-2.5.patch > > > ROBLEM: > The Ambari File View -> Upload, does not work anymore in Chrome 56.0.2924.87 > and IE 11 > The error message is: Currently supports single file upload > STEPS TO REPRODUCE: > root@node1 ~# ambari-server --hash > 503aa9809d4890e6c54b219fda1aa3444dbb5597 > root@node1 ~# ambari-server --version > 2.4.2.0-136 > My cluster is the default HDP 2.5.3 installation. > 1) Upgrade to Chrome 56.0.2924.87 (or use IE 11). > 2) Open Ambari Views -> File View. > 3) Create a file called "x.sh" and select to upload it > 4) The operation fails with: "Currently supports single file upload" > Opening the Chrome Developer, shows the error: > "Cannot add a directory." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20137) File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20137: -- Status: Patch Available (was: Open) > File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE > 11 > > > Key: AMBARI-20137 > URL: https://issues.apache.org/jira/browse/AMBARI-20137 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20137_branch-2.5.patch > > > ROBLEM: > The Ambari File View -> Upload, does not work anymore in Chrome 56.0.2924.87 > and IE 11 > The error message is: Currently supports single file upload > STEPS TO REPRODUCE: > root@node1 ~# ambari-server --hash > 503aa9809d4890e6c54b219fda1aa3444dbb5597 > root@node1 ~# ambari-server --version > 2.4.2.0-136 > My cluster is the default HDP 2.5.3 installation. > 1) Upgrade to Chrome 56.0.2924.87 (or use IE 11). > 2) Open Ambari Views -> File View. > 3) Create a file called "x.sh" and select to upload it > 4) The operation fails with: "Currently supports single file upload" > Opening the Chrome Developer, shows the error: > "Cannot add a directory." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20137) File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20137: -- Component/s: ambari-views > File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE > 11 > > > Key: AMBARI-20137 > URL: https://issues.apache.org/jira/browse/AMBARI-20137 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > > ROBLEM: > The Ambari File View -> Upload, does not work anymore in Chrome 56.0.2924.87 > and IE 11 > The error message is: Currently supports single file upload > STEPS TO REPRODUCE: > root@node1 ~# ambari-server --hash > 503aa9809d4890e6c54b219fda1aa3444dbb5597 > root@node1 ~# ambari-server --version > 2.4.2.0-136 > My cluster is the default HDP 2.5.3 installation. > 1) Upgrade to Chrome 56.0.2924.87 (or use IE 11). > 2) Open Ambari Views -> File View. > 3) Create a file called "x.sh" and select to upload it > 4) The operation fails with: "Currently supports single file upload" > Opening the Chrome Developer, shows the error: > "Cannot add a directory." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20137) File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE 11
[ https://issues.apache.org/jira/browse/AMBARI-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20137: -- Description: ROBLEM: The Ambari File View -> Upload, does not work anymore in Chrome 56.0.2924.87 and IE 11 The error message is: Currently supports single file upload STEPS TO REPRODUCE: root@node1 ~# ambari-server --hash 503aa9809d4890e6c54b219fda1aa3444dbb5597 root@node1 ~# ambari-server --version 2.4.2.0-136 My cluster is the default HDP 2.5.3 installation. 1) Upgrade to Chrome 56.0.2924.87 (or use IE 11). 2) Open Ambari Views -> File View. 3) Create a file called "x.sh" and select to upload it 4) The operation fails with: "Currently supports single file upload" Opening the Chrome Developer, shows the error: "Cannot add a directory." > File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE > 11 > > > Key: AMBARI-20137 > URL: https://issues.apache.org/jira/browse/AMBARI-20137 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > > ROBLEM: > The Ambari File View -> Upload, does not work anymore in Chrome 56.0.2924.87 > and IE 11 > The error message is: Currently supports single file upload > STEPS TO REPRODUCE: > root@node1 ~# ambari-server --hash > 503aa9809d4890e6c54b219fda1aa3444dbb5597 > root@node1 ~# ambari-server --version > 2.4.2.0-136 > My cluster is the default HDP 2.5.3 installation. > 1) Upgrade to Chrome 56.0.2924.87 (or use IE 11). > 2) Open Ambari Views -> File View. > 3) Create a file called "x.sh" and select to upload it > 4) The operation fails with: "Currently supports single file upload" > Opening the Chrome Developer, shows the error: > "Cannot add a directory." -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20137) File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE 11
Gaurav Nagar created AMBARI-20137: - Summary: File upload from Ambari File View does not work in Chrome 56.0.2924.87 and IE 11 Key: AMBARI-20137 URL: https://issues.apache.org/jira/browse/AMBARI-20137 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Attachment: AMBARI-20135.1_branch-2.5.patch > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135.1_branch-2.5.patch, > AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Status: Patch Available (was: Open) > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Component/s: ambari-views > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Attachment: AMBARI-20135_branch-2.5.patch > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
Gaurav Nagar created AMBARI-20135: - Summary: Hive view 2.0 : Hanging query - no cancel available Key: AMBARI-20135 URL: https://issues.apache.org/jira/browse/AMBARI-20135 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.0 In Hive View 2.0 there is no way to cancel the current running job. Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20093) Cannot edit join node name in Workflow Manager
[ https://issues.apache.org/jira/browse/AMBARI-20093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20093: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Cannot edit join node name in Workflow Manager > -- > > Key: AMBARI-20093 > URL: https://issues.apache.org/jira/browse/AMBARI-20093 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Belliraj HB >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20093_trunk.patch > > > After create a fork node, the join node will generated automatically. But, I > cannot edit the name of the join node. Only action I can take to that join > node is delete. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20107: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Action node shows unsupported properties even though there are none in > workflow manager. > > > Key: AMBARI-20107 > URL: https://issues.apache.org/jira/browse/AMBARI-20107 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20107_trunk.patch > > > Action node during edit shows unsupported properties. But in unsupported > properties you see empty text. > Expected. > Unsupported properties should not be shown if there are no unsupported > properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20090) On submit of bundle, if any coordinator path contains variables, user should be notified about custom variables.
[ https://issues.apache.org/jira/browse/AMBARI-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20090: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > On submit of bundle, if any coordinator path contains variables, user should > be notified about custom variables. > > > Key: AMBARI-20090 > URL: https://issues.apache.org/jira/browse/AMBARI-20090 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20090_trunk.patch > > > If there is a variable in file path, it becomes difficult to deduce variables > as we don't know the actual workflow that the bundle or coordinator uses. The > fix is to just prompt the user the variables cannot be auto detected as path > is not known. > In bundle submit, we parse though all coordinator paths and their respective > workflows to find the variables to be entered. But in case any of these paths > contain "variable" section,WFD wont be able to auto prompt these variables . > In this scenario, WFD has to notify the user to fill the variables manually > using custom variables. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20084) Cut Node feature is broken in workflow manager
[
https://issues.apache.org/jira/browse/AMBARI-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20084:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5 and trunk.
> Cut Node feature is broken in workflow manager
> --
>
> Key: AMBARI-20084
> URL: https://issues.apache.org/jira/browse/AMBARI-20084
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20084_trunk.patch
>
>
> Cut Node feature is broken in workflow manager. While cutting the node I am
> seeing below error in UI console.
> {code}
> TypeError: t is undefined
> d<.deleteNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:9
> e.default<.deleteWorkflowNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> e.default<.cutNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> a<._addEvents/<()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:8
> J.event.dispatch()
> vendor-415a6fd6db11ecd27aa07f5115312174.js:4
> J.event.add/g.handle()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20079: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20079_trunk.patch, Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20080) WFM does not issue confirmation message when workflow is suspended or killed
[ https://issues.apache.org/jira/browse/AMBARI-20080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20080: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > WFM does not issue confirmation message when workflow is suspended or killed > > > Key: AMBARI-20080 > URL: https://issues.apache.org/jira/browse/AMBARI-20080 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20080_trunk.patch > > > Steps: > 1. log into ambari ui > 2. go to wfm > 3. upload workflow from file system: > 4. submit the workflow > 5. kill or suspend the workflow from WFM ui > Issue: > workflow ui is not giving any confirmation message when wf is killed or > suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20078) When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed
[ https://issues.apache.org/jira/browse/AMBARI-20078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20078: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > When uploading a file using the WFM, need a message to say that either the > file upload succeeded or failed > -- > > Key: AMBARI-20078 > URL: https://issues.apache.org/jira/browse/AMBARI-20078 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20078_trunk.patch > > > Steps to repo: > 1. Create a WF > 2. Add a java action > 3. Go to Advanced Properties, and under File - click on Browse and use the > File Browser to upload a file from local machine. > 4. Need to receive a message whether the file upload is successful or failed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20041) Custom job.properties are not retained in the workflow designer
[ https://issues.apache.org/jira/browse/AMBARI-20041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20041: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Custom job.properties are not retained in the workflow designer > --- > > Key: AMBARI-20041 > URL: https://issues.apache.org/jira/browse/AMBARI-20041 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Labels: wfd > Fix For: 2.5.0 > > Attachments: AMBARI-20041.branch-2.5.patch > > > Custom job.properties are not retained in the workflow designer. > Steps to reproduce : > 1) Submit a workflow with custom job properties say > oozie.action.sharelib.for.sqoop=sqoop,hive. > 2) From the dashboard, select this workflow. > 3) When user tries to submit it again, previously included properties are not > visible to the user. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20040) Workflow Manager workflow rendering is broken in designer page
[ https://issues.apache.org/jira/browse/AMBARI-20040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20040: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Workflow Manager workflow rendering is broken in designer page > -- > > Key: AMBARI-20040 > URL: https://issues.apache.org/jira/browse/AMBARI-20040 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Belliraj HB > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20040_trunk.patch, workflow (3).xml > > > Workflow rendering is broken in designer page. > Steps to reproduce : > 1) Import the attached workflow and check that rendering of the workflow is > broken. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19979) Issue while resetting the coordinator
[ https://issues.apache.org/jira/browse/AMBARI-19979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19979: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Issue while resetting the coordinator > - > > Key: AMBARI-19979 > URL: https://issues.apache.org/jira/browse/AMBARI-19979 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-19979.branch-2.5.patch > > > User is not able to reset the coordinator. > Steps to reproduce : > 1) Import the attached coordinator. > 2) Import the same coordinator in different window > 3) Try to preview the xml or reset the coordinator. The UI is getting hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19823: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19823: -- Fix Version/s: (was: trunk) 2.5.0 > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.5.0 > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19978) Coordinator tag sequence is not maintained
[ https://issues.apache.org/jira/browse/AMBARI-19978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19978: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Coordinator tag sequence is not maintained > --- > > Key: AMBARI-19978 > URL: https://issues.apache.org/jira/browse/AMBARI-19978 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-19978_trunk.patch > > > Coordinator tag sequence is not maintained while creating coordinator. > Steps to reproduce : > 1) Import the attached coordinator. > 2) In the preview xml, check the position of controls tag. Its coming in the > end. > According to coordinator xsd, this tag should be in the beginning of the > coordinator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20003) Not able to preview the workflow xml
[
https://issues.apache.org/jira/browse/AMBARI-20003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar updated AMBARI-20003:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5 and trunk.
> Not able to preview the workflow xml
>
>
> Key: AMBARI-20003
> URL: https://issues.apache.org/jira/browse/AMBARI-20003
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20003_trunk.patch
>
>
> Preview xml is failing and I am seeing below error in console.log :
> {code}
> Uncaught TypeError: Cannot read property 'length' of undefined
> at n.validate
> (http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-ef66fa01464545ddc3f5b0f360f1ea3c.js:7:13121)
> at n.visitNode
> (http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-ef66fa01464545ddc3f5b0f360f1ea3c.js:9:21574)
> at
> http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-ef66fa01464545ddc3f5b0f360f1ea3c.js:9:22050
> at Array.forEach (native)
> at n.visitNode
> (http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-ef66fa01464545ddc3f5b0f360f1ea3c.js:9:22028)
> at n.process
> (http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-ef66fa01464545ddc3f5b0f360f1ea3c.js:9:19594)
> at n.previewWorkflow
> (http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-ef66fa01464545ddc3f5b0f360f1ea3c.js:3:27474)
> at n.send
> (http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-c52dd73472b01fcbec62872ba470c597.js:15:25559)
> at n [as send]
> (http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-c52dd73472b01fcbec62872ba470c597.js:11:18800)
> at
> http://172.27.44.87:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-c52dd73472b01fcbec62872ba470c597.js:13:10172
> {code}
> Steps to reproduce :
> 1) Import the attached workflow.
> 2) Try to preview the workflow.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
