[jira] [Created] (AMBARI-15438) Capacity Scheduler view is not working when using custom configuration

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-15438:
-

 Summary: Capacity Scheduler view is not working when using custom 
configuration
 Key: AMBARI-15438
 URL: https://issues.apache.org/jira/browse/AMBARI-15438
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.2.1
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.2.2


Capacity scheduler not working when using remote cluster.

It fails to get ranger-yarn-plugin configuration when ranger service is not 
installed.

http://c6408.ambari.apache.org:8080/api/v1/views/CAPACITY-SCHEDULER/versions/1.0.0/instances/AUTO_CS_INSTANCE/resources/scheduler/configuration/getConfig?siteName=ranger-yarn-plugin-properties&configName=ranger-yarn-plugin-enabled

{code:java}

{"trace":"java.lang.NullPointerException\n\tat 
org.apache.ambari.view.utils.ambari.RemoteCluster.getConfigurationValue(RemoteCluster.java:80)\n\tat
 
org.apache.ambari.view.capacityscheduler.ConfigurationService.getConfigurationValue(ConfigurationService.java:494)\n\tat
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
 java.lang.reflect.Method.invoke(Method.java:497)\n\tat 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15438) Capacity Scheduler view is not working when using custom configuration

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15438:
--
Status: Patch Available  (was: Open)

> Capacity Scheduler view is not working when using custom configuration
> --
>
> Key: AMBARI-15438
> URL: https://issues.apache.org/jira/browse/AMBARI-15438
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.1
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.2.2
>
> Attachments: AMBARI-15438_branch-2.2.patch
>
>
> Capacity scheduler not working when using remote cluster.
> It fails to get ranger-yarn-plugin configuration when ranger service is not 
> installed.
> http://c6408.ambari.apache.org:8080/api/v1/views/CAPACITY-SCHEDULER/versions/1.0.0/instances/AUTO_CS_INSTANCE/resources/scheduler/configuration/getConfig?siteName=ranger-yarn-plugin-properties&configName=ranger-yarn-plugin-enabled
> {code:java}
> {"trace":"java.lang.NullPointerException\n\tat 
> org.apache.ambari.view.utils.ambari.RemoteCluster.getConfigurationValue(RemoteCluster.java:80)\n\tat
>  
> org.apache.ambari.view.capacityscheduler.ConfigurationService.getConfigurationValue(ConfigurationService.java:494)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:497)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15438) Capacity Scheduler view is not working when using custom configuration

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15438:
--
Attachment: AMBARI-15438_branch-2.2.patch

> Capacity Scheduler view is not working when using custom configuration
> --
>
> Key: AMBARI-15438
> URL: https://issues.apache.org/jira/browse/AMBARI-15438
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.1
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.2.2
>
> Attachments: AMBARI-15438_branch-2.2.patch
>
>
> Capacity scheduler not working when using remote cluster.
> It fails to get ranger-yarn-plugin configuration when ranger service is not 
> installed.
> http://c6408.ambari.apache.org:8080/api/v1/views/CAPACITY-SCHEDULER/versions/1.0.0/instances/AUTO_CS_INSTANCE/resources/scheduler/configuration/getConfig?siteName=ranger-yarn-plugin-properties&configName=ranger-yarn-plugin-enabled
> {code:java}
> {"trace":"java.lang.NullPointerException\n\tat 
> org.apache.ambari.view.utils.ambari.RemoteCluster.getConfigurationValue(RemoteCluster.java:80)\n\tat
>  
> org.apache.ambari.view.capacityscheduler.ConfigurationService.getConfigurationValue(ConfigurationService.java:494)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:497)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-15727) https://hortonworks.jira.com/browse/BUG-55491

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-15727:
-

 Summary: https://hortonworks.jira.com/browse/BUG-55491
 Key: AMBARI-15727
 URL: https://issues.apache.org/jira/browse/AMBARI-15727
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar


ISSUE: Queries fail when execution engine is Tez from Hive view. 

Error :

{code}

java.lang.NullPointerException 
java.lang.NullPointerException 
at 
org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
 
at 
org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
 
at 
org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
 
at 
org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
 
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: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)
 

{code}

The same query works in the hive view if the execution engine is MR. 

Restarting Ambari did not work. Here is the tail of the ambari-server log:

{code}
25 Feb 2016 13:15:21,451 INFO [qtp-ambari-client-31] Connection:497 - Hive 
session opened 
25 Feb 2016 13:15:43,598 ERROR [qtp-ambari-client-31] 
ServiceFormattedException:96 - java.lang.NullPointerException 

java.lang.NullPointerException 
at 
org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
 
at 
org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
 
at 
org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
 
at 
org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
 
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: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:20
{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15727) "E090 NullPointerException" when executing Hive queries with tez

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15727:
--
Summary: "E090 NullPointerException" when executing Hive queries with tez  
(was: https://hortonworks.jira.com/browse/BUG-55491)

> "E090 NullPointerException" when executing Hive queries with tez
> 
>
> Key: AMBARI-15727
> URL: https://issues.apache.org/jira/browse/AMBARI-15727
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
>
> ISSUE: Queries fail when execution engine is Tez from Hive view. 
> Error :
> {code}
> java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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)
>  
> {code}
> The same query works in the hive view if the execution engine is MR. 
> Restarting Ambari did not work. Here is the tail of the ambari-server log:
> {code}
> 25 Feb 2016 13:15:21,451 INFO [qtp-ambari-client-31] Connection:497 - Hive 
> session opened 
> 25 Feb 2016 13:15:43,598 ERROR [qtp-ambari-client-31] 
> ServiceFormattedException:96 - java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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:20
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15727) https://hortonworks.jira.com/browse/BUG-55491

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15727:
--
Affects Version/s: 2.2.0

> https://hortonworks.jira.com/browse/BUG-55491
> -
>
> Key: AMBARI-15727
> URL: https://issues.apache.org/jira/browse/AMBARI-15727
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
>
> ISSUE: Queries fail when execution engine is Tez from Hive view. 
> Error :
> {code}
> java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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)
>  
> {code}
> The same query works in the hive view if the execution engine is MR. 
> Restarting Ambari did not work. Here is the tail of the ambari-server log:
> {code}
> 25 Feb 2016 13:15:21,451 INFO [qtp-ambari-client-31] Connection:497 - Hive 
> session opened 
> 25 Feb 2016 13:15:43,598 ERROR [qtp-ambari-client-31] 
> ServiceFormattedException:96 - java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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:20
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15727) "E090 NullPointerException" when executing Hive queries with tez

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15727:
--
Status: Patch Available  (was: Open)

> "E090 NullPointerException" when executing Hive queries with tez
> 
>
> Key: AMBARI-15727
> URL: https://issues.apache.org/jira/browse/AMBARI-15727
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
>
> ISSUE: Queries fail when execution engine is Tez from Hive view. 
> Error :
> {code}
> java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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)
>  
> {code}
> The same query works in the hive view if the execution engine is MR. 
> Restarting Ambari did not work. Here is the tail of the ambari-server log:
> {code}
> 25 Feb 2016 13:15:21,451 INFO [qtp-ambari-client-31] Connection:497 - Hive 
> session opened 
> 25 Feb 2016 13:15:43,598 ERROR [qtp-ambari-client-31] 
> ServiceFormattedException:96 - java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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:20
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15727) "E090 NullPointerException" when executing Hive queries with tez

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15727:
--
Attachment: AMBARI-15727_branch-2.2.patch

> "E090 NullPointerException" when executing Hive queries with tez
> 
>
> Key: AMBARI-15727
> URL: https://issues.apache.org/jira/browse/AMBARI-15727
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Attachments: AMBARI-15727_branch-2.2.patch
>
>
> ISSUE: Queries fail when execution engine is Tez from Hive view. 
> Error :
> {code}
> java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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)
>  
> {code}
> The same query works in the hive view if the execution engine is MR. 
> Restarting Ambari did not work. Here is the tail of the ambari-server log:
> {code}
> 25 Feb 2016 13:15:21,451 INFO [qtp-ambari-client-31] Connection:497 - Hive 
> session opened 
> 25 Feb 2016 13:15:43,598 ERROR [qtp-ambari-client-31] 
> ServiceFormattedException:96 - java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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:20
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15727) "E090 NullPointerException" when executing Hive queries with tez

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15727:
--
Fix Version/s: 2.2.2

> "E090 NullPointerException" when executing Hive queries with tez
> 
>
> Key: AMBARI-15727
> URL: https://issues.apache.org/jira/browse/AMBARI-15727
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.2.2
>
> Attachments: AMBARI-15727_branch-2.2.patch
>
>
> ISSUE: Queries fail when execution engine is Tez from Hive view. 
> Error :
> {code}
> java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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)
>  
> {code}
> The same query works in the hive view if the execution engine is MR. 
> Restarting Ambari did not work. Here is the tail of the ambari-server log:
> {code}
> 25 Feb 2016 13:15:21,451 INFO [qtp-ambari-client-31] Connection:497 - Hive 
> session opened 
> 25 Feb 2016 13:15:43,598 ERROR [qtp-ambari-client-31] 
> ServiceFormattedException:96 - java.lang.NullPointerException 
> java.lang.NullPointerException 
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.saveJobInfoIfNeeded(Aggregator.java:180)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.Aggregator.readATSJob(Aggregator.java:133)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.jsonObjectFromJob(JobService.java:123)
>  
> at 
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:106)
>  
> 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: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:20
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-15919:
-

 Summary: Migrate instance specific data from one version to 
another.
 Key: AMBARI-15919
 URL: https://issues.apache.org/jira/browse/AMBARI-15919
 Project: Ambari
  Issue Type: Bug
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar


Users will update Hive/Pig View jars multiple times during upgarde, they cannot 
lose any data. The view will need to implement specific data migration call 
back handler that the ambari view framework will invoke.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15919:
--
Fix Version/s: 2.4.0

> Migrate instance specific data from one version to another.
> ---
>
> Key: AMBARI-15919
> URL: https://issues.apache.org/jira/browse/AMBARI-15919
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Users will update Hive/Pig View jars multiple times during upgarde, they 
> cannot lose any data. The view will need to implement specific data migration 
> call back handler that the ambari view framework will invoke.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15919:
--
Affects Version/s: 2.4.0

> Migrate instance specific data from one version to another.
> ---
>
> Key: AMBARI-15919
> URL: https://issues.apache.org/jira/browse/AMBARI-15919
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Users will update Hive/Pig View jars multiple times during upgarde, they 
> cannot lose any data. The view will need to implement specific data migration 
> call back handler that the ambari view framework will invoke.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15919:
--
Description: 
It is critical that we provide a way to migrate instance data and view data 
information between versions of views. We need to support the following use 
case:

- New version of view is instantiated. Since instance specific data will not be 
available to the new instance of the view (if the version has changed), there 
needs to be a way of migrating existing information over to the new view 
instance.
- The Ambari view framework needs to provide a facility to invoke call back 
handlers (of sorts) to allow the view itself to handle the migration from and 
older version to the current version.

An example...

After a view instance (X1) is created (say from XView 1.0.0), a view might use 
instance data and/or datastore data. When a new view is released (say from 
XView 2.0.0), an ambari admin will want to create a new instance (X2) and 
migrate the data from the existing instance (X1). Ambari should provide a 
mechanism to perform this migration.

1) The ambari admin creates new instance X2 in the admin interface.
2) The ambari admin can select to migrate data from an existing instance.
3) The ambari admin initiates the migration of instance and datastore. The 
ambari views framework starts the processing of instance + datastore data 
movement (copying) to the new X2 instance scope.
4) The framework should call into a hook in the view in case any changes are 
needed to the X1 info before they saved in the new X2 instance.

  was:Users will update Hive/Pig View jars multiple times during upgarde, they 
cannot lose any data. The view will need to implement specific data migration 
call back handler that the ambari view framework will invoke.


> Migrate instance specific data from one version to another.
> ---
>
> Key: AMBARI-15919
> URL: https://issues.apache.org/jira/browse/AMBARI-15919
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> It is critical that we provide a way to migrate instance data and view data 
> information between versions of views. We need to support the following use 
> case:
> - New version of view is instantiated. Since instance specific data will not 
> be available to the new instance of the view (if the version has changed), 
> there needs to be a way of migrating existing information over to the new 
> view instance.
> - The Ambari view framework needs to provide a facility to invoke call back 
> handlers (of sorts) to allow the view itself to handle the migration from and 
> older version to the current version.
> An example...
> After a view instance (X1) is created (say from XView 1.0.0), a view might 
> use instance data and/or datastore data. When a new view is released (say 
> from XView 2.0.0), an ambari admin will want to create a new instance (X2) 
> and migrate the data from the existing instance (X1). Ambari should provide a 
> mechanism to perform this migration.
> 1) The ambari admin creates new instance X2 in the admin interface.
> 2) The ambari admin can select to migrate data from an existing instance.
> 3) The ambari admin initiates the migration of instance and datastore. The 
> ambari views framework starts the processing of instance + datastore data 
> movement (copying) to the new X2 instance scope.
> 4) The framework should call into a hook in the view in case any changes are 
> needed to the X1 info before they saved in the new X2 instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15919:
--
Attachment: AMBARI-15919_trunk.patch

> Migrate instance specific data from one version to another.
> ---
>
> Key: AMBARI-15919
> URL: https://issues.apache.org/jira/browse/AMBARI-15919
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-15919_trunk.patch
>
>
> It is critical that we provide a way to migrate instance data and view data 
> information between versions of views. We need to support the following use 
> case:
> - New version of view is instantiated. Since instance specific data will not 
> be available to the new instance of the view (if the version has changed), 
> there needs to be a way of migrating existing information over to the new 
> view instance.
> - The Ambari view framework needs to provide a facility to invoke call back 
> handlers (of sorts) to allow the view itself to handle the migration from and 
> older version to the current version.
> An example...
> After a view instance (X1) is created (say from XView 1.0.0), a view might 
> use instance data and/or datastore data. When a new view is released (say 
> from XView 2.0.0), an ambari admin will want to create a new instance (X2) 
> and migrate the data from the existing instance (X1). Ambari should provide a 
> mechanism to perform this migration.
> 1) The ambari admin creates new instance X2 in the admin interface.
> 2) The ambari admin can select to migrate data from an existing instance.
> 3) The ambari admin initiates the migration of instance and datastore. The 
> ambari views framework starts the processing of instance + datastore data 
> movement (copying) to the new X2 instance scope.
> 4) The framework should call into a hook in the view in case any changes are 
> needed to the X1 info before they saved in the new X2 instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15919:
--
Attachment: (was: AMBARI-15919_trunk.patch)

> Migrate instance specific data from one version to another.
> ---
>
> Key: AMBARI-15919
> URL: https://issues.apache.org/jira/browse/AMBARI-15919
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-15919_trunk.patch
>
>
> It is critical that we provide a way to migrate instance data and view data 
> information between versions of views. We need to support the following use 
> case:
> - New version of view is instantiated. Since instance specific data will not 
> be available to the new instance of the view (if the version has changed), 
> there needs to be a way of migrating existing information over to the new 
> view instance.
> - The Ambari view framework needs to provide a facility to invoke call back 
> handlers (of sorts) to allow the view itself to handle the migration from and 
> older version to the current version.
> An example...
> After a view instance (X1) is created (say from XView 1.0.0), a view might 
> use instance data and/or datastore data. When a new view is released (say 
> from XView 2.0.0), an ambari admin will want to create a new instance (X2) 
> and migrate the data from the existing instance (X1). Ambari should provide a 
> mechanism to perform this migration.
> 1) The ambari admin creates new instance X2 in the admin interface.
> 2) The ambari admin can select to migrate data from an existing instance.
> 3) The ambari admin initiates the migration of instance and datastore. The 
> ambari views framework starts the processing of instance + datastore data 
> movement (copying) to the new X2 instance scope.
> 4) The framework should call into a hook in the view in case any changes are 
> needed to the X1 info before they saved in the new X2 instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15919:
--
Attachment: AMBARI-15919_trunk.patch

> Migrate instance specific data from one version to another.
> ---
>
> Key: AMBARI-15919
> URL: https://issues.apache.org/jira/browse/AMBARI-15919
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-15919_trunk.patch
>
>
> It is critical that we provide a way to migrate instance data and view data 
> information between versions of views. We need to support the following use 
> case:
> - New version of view is instantiated. Since instance specific data will not 
> be available to the new instance of the view (if the version has changed), 
> there needs to be a way of migrating existing information over to the new 
> view instance.
> - The Ambari view framework needs to provide a facility to invoke call back 
> handlers (of sorts) to allow the view itself to handle the migration from and 
> older version to the current version.
> An example...
> After a view instance (X1) is created (say from XView 1.0.0), a view might 
> use instance data and/or datastore data. When a new view is released (say 
> from XView 2.0.0), an ambari admin will want to create a new instance (X2) 
> and migrate the data from the existing instance (X1). Ambari should provide a 
> mechanism to perform this migration.
> 1) The ambari admin creates new instance X2 in the admin interface.
> 2) The ambari admin can select to migrate data from an existing instance.
> 3) The ambari admin initiates the migration of instance and datastore. The 
> ambari views framework starts the processing of instance + datastore data 
> movement (copying) to the new X2 instance scope.
> 4) The framework should call into a hook in the view in case any changes are 
> needed to the X1 info before they saved in the new X2 instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15919:
--
Status: Patch Available  (was: Open)

> Migrate instance specific data from one version to another.
> ---
>
> Key: AMBARI-15919
> URL: https://issues.apache.org/jira/browse/AMBARI-15919
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-15919_trunk.patch
>
>
> It is critical that we provide a way to migrate instance data and view data 
> information between versions of views. We need to support the following use 
> case:
> - New version of view is instantiated. Since instance specific data will not 
> be available to the new instance of the view (if the version has changed), 
> there needs to be a way of migrating existing information over to the new 
> view instance.
> - The Ambari view framework needs to provide a facility to invoke call back 
> handlers (of sorts) to allow the view itself to handle the migration from and 
> older version to the current version.
> An example...
> After a view instance (X1) is created (say from XView 1.0.0), a view might 
> use instance data and/or datastore data. When a new view is released (say 
> from XView 2.0.0), an ambari admin will want to create a new instance (X2) 
> and migrate the data from the existing instance (X1). Ambari should provide a 
> mechanism to perform this migration.
> 1) The ambari admin creates new instance X2 in the admin interface.
> 2) The ambari admin can select to migrate data from an existing instance.
> 3) The ambari admin initiates the migration of instance and datastore. The 
> ambari views framework starts the processing of instance + datastore data 
> movement (copying) to the new X2 instance scope.
> 4) The framework should call into a hook in the view in case any changes are 
> needed to the X1 info before they saved in the new X2 instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15919) Migrate instance specific data from one version to another.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-15919:
--
Component/s: ambari-views

> Migrate instance specific data from one version to another.
> ---
>
> Key: AMBARI-15919
> URL: https://issues.apache.org/jira/browse/AMBARI-15919
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-15919_trunk.patch
>
>
> It is critical that we provide a way to migrate instance data and view data 
> information between versions of views. We need to support the following use 
> case:
> - New version of view is instantiated. Since instance specific data will not 
> be available to the new instance of the view (if the version has changed), 
> there needs to be a way of migrating existing information over to the new 
> view instance.
> - The Ambari view framework needs to provide a facility to invoke call back 
> handlers (of sorts) to allow the view itself to handle the migration from and 
> older version to the current version.
> An example...
> After a view instance (X1) is created (say from XView 1.0.0), a view might 
> use instance data and/or datastore data. When a new view is released (say 
> from XView 2.0.0), an ambari admin will want to create a new instance (X2) 
> and migrate the data from the existing instance (X1). Ambari should provide a 
> mechanism to perform this migration.
> 1) The ambari admin creates new instance X2 in the admin interface.
> 2) The ambari admin can select to migrate data from an existing instance.
> 3) The ambari admin initiates the migration of instance and datastore. The 
> ambari views framework starts the processing of instance + datastore data 
> movement (copying) to the new X2 instance scope.
> 4) The framework should call into a hook in the view in case any changes are 
> needed to the X1 info before they saved in the new X2 instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16037) View Configuration Simplification

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16037:
-

 Summary: View Configuration Simplification
 Key: AMBARI-16037
 URL: https://issues.apache.org/jira/browse/AMBARI-16037
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.2.2
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16037) View Configuration Simplification

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16037:
--
Component/s: ambari-views

> View Configuration Simplification
> -
>
> Key: AMBARI-16037
> URL: https://issues.apache.org/jira/browse/AMBARI-16037
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16037) View Configuration Simplification

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16037:
--
Description: 
Scope
The current implementation scope is limited to improving the ease of creation 
of View Instances, and reduce creation time issues. Also, this design leaves 
enough extension points to be extended further on the availability of 
subsequent centrally shared services in the case of non-Ambari managed custom 
Clusters.
 
Custom Configuration for non-Ambari managed Cluster
Cluster level configurations will be setup once to define underlying data 
services and end-points for subsequent usage at the time of View Instance 
creation. 
These cluster level configurations will be maintained as references in the 
respective View instances. 


> View Configuration Simplification
> -
>
> Key: AMBARI-16037
> URL: https://issues.apache.org/jira/browse/AMBARI-16037
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Scope
> The current implementation scope is limited to improving the ease of creation 
> of View Instances, and reduce creation time issues. Also, this design leaves 
> enough extension points to be extended further on the availability of 
> subsequent centrally shared services in the case of non-Ambari managed custom 
> Clusters.
>  
> Custom Configuration for non-Ambari managed Cluster
> Cluster level configurations will be setup once to define underlying data 
> services and end-points for subsequent usage at the time of View Instance 
> creation. 
> These cluster level configurations will be maintained as references in the 
> respective View instances. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16037) View Configuration Simplification

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16037:
--
Status: Patch Available  (was: Open)

> View Configuration Simplification
> -
>
> Key: AMBARI-16037
> URL: https://issues.apache.org/jira/browse/AMBARI-16037
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16037_trunk.patch
>
>
> Scope
> The current implementation scope is limited to improving the ease of creation 
> of View Instances, and reduce creation time issues. Also, this design leaves 
> enough extension points to be extended further on the availability of 
> subsequent centrally shared services in the case of non-Ambari managed custom 
> Clusters.
>  
> Custom Configuration for non-Ambari managed Cluster
> Cluster level configurations will be setup once to define underlying data 
> services and end-points for subsequent usage at the time of View Instance 
> creation. 
> These cluster level configurations will be maintained as references in the 
> respective View instances. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16037) View Configuration Simplification

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16037:
--
Attachment: AMBARI-16037_trunk.patch

> View Configuration Simplification
> -
>
> Key: AMBARI-16037
> URL: https://issues.apache.org/jira/browse/AMBARI-16037
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16037_trunk.patch
>
>
> Scope
> The current implementation scope is limited to improving the ease of creation 
> of View Instances, and reduce creation time issues. Also, this design leaves 
> enough extension points to be extended further on the availability of 
> subsequent centrally shared services in the case of non-Ambari managed custom 
> Clusters.
>  
> Custom Configuration for non-Ambari managed Cluster
> Cluster level configurations will be setup once to define underlying data 
> services and end-points for subsequent usage at the time of View Instance 
> creation. 
> These cluster level configurations will be maintained as references in the 
> respective View instances. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16037) View Configuration Simplification

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16037:
--
Attachment: AMBARI-16037.2_trunk.patch

> View Configuration Simplification
> -
>
> Key: AMBARI-16037
> URL: https://issues.apache.org/jira/browse/AMBARI-16037
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16037.2_trunk.patch, AMBARI-16037_trunk.patch
>
>
> Scope
> The current implementation scope is limited to improving the ease of creation 
> of View Instances, and reduce creation time issues. Also, this design leaves 
> enough extension points to be extended further on the availability of 
> subsequent centrally shared services in the case of non-Ambari managed custom 
> Clusters.
>  
> Custom Configuration for non-Ambari managed Cluster
> Cluster level configurations will be setup once to define underlying data 
> services and end-points for subsequent usage at the time of View Instance 
> creation. 
> These cluster level configurations will be maintained as references in the 
> respective View instances. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16116) Not able to edit Pig script tab

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16116:
-

 Summary: Not able to edit Pig script tab
 Key: AMBARI-16116
 URL: https://issues.apache.org/jira/browse/AMBARI-16116
 Project: Ambari
  Issue Type: Bug
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar


Not able to edit Pig script tab on Pig views on humboldt.
The 'path of this script file on HDFS' keeps loading and script tab is disabled.

The below API call throws error. The slash before 'user/admin' is missing
https://ambviews-am22.cloudapp.net/api/v1/views/PIG/versions/1.0.0/instances/PIG/resources/file/%2F%2Fuser%2Fadmin%2Fpig%2Fscripts%2Fbcd1234-2016-04-22_10-17.pig
API Response
{"message":"user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig","status":404,"trace":"java.io.FileNotFoundException:
 
user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\njava.io.FileNotFoundException:
 user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\tat 
org.apache.hadoop.fs.azure.NativeAzureFileSystem.open(NativeAzureFileSystem.java:2034)\n\tat
 org.apache.hadoop.fs.FileSystem.open(FileSystem.java:767)\n\tat 
org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:324)\n\tat 
org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:322)\n\tat 
java.security.AccessController.doPrivileged(Native Method)\n\tat 
javax.security.auth.Subject.doAs(Subject.java:415)\n\tat 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)\n\tat
 org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)\n\tat 
org.apache.ambari.view.utils.hdfs.HdfsApi.open(HdfsApi.java:322)\n\tat 
org.apache.ambari.view.pig.utils.FilePaginator.readPage(FilePaginator.java:76)\n\tat
 
org.apache.ambari.view.pig.resources.files.FileService.getFile(FileService.java:90)\n\tat
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
 java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)\n\tat
 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)\n\tat
 javax.servlet.http.HttpServlet.service(HttpServlet.java:770)\n\tat 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)\n\tat 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)\n\tat
 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(Fi

[jira] [Updated] (AMBARI-16116) Not able to edit Pig script tab

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16116:
--
Fix Version/s: 2.4.0

> Not able to edit Pig script tab
> ---
>
> Key: AMBARI-16116
> URL: https://issues.apache.org/jira/browse/AMBARI-16116
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Not able to edit Pig script tab on Pig views on humboldt.
> The 'path of this script file on HDFS' keeps loading and script tab is 
> disabled.
> The below API call throws error. The slash before 'user/admin' is missing
> https://ambviews-am22.cloudapp.net/api/v1/views/PIG/versions/1.0.0/instances/PIG/resources/file/%2F%2Fuser%2Fadmin%2Fpig%2Fscripts%2Fbcd1234-2016-04-22_10-17.pig
> API Response
> {"message":"user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig","status":404,"trace":"java.io.FileNotFoundException:
>  
> user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\njava.io.FileNotFoundException:
>  user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\tat 
> org.apache.hadoop.fs.azure.NativeAzureFileSystem.open(NativeAzureFileSystem.java:2034)\n\tat
>  org.apache.hadoop.fs.FileSystem.open(FileSystem.java:767)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:324)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:322)\n\tat 
> java.security.AccessController.doPrivileged(Native Method)\n\tat 
> javax.security.auth.Subject.doAs(Subject.java:415)\n\tat 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)\n\tat
>  org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi.open(HdfsApi.java:322)\n\tat 
> org.apache.ambari.view.pig.utils.FilePaginator.readPage(FilePaginator.java:76)\n\tat
>  
> org.apache.ambari.view.pig.resources.files.FileService.getFile(FileService.java:90)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:770)

[jira] [Updated] (AMBARI-16116) Not able to edit Pig script tab

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16116:
--
Affects Version/s: 2.2.0

> Not able to edit Pig script tab
> ---
>
> Key: AMBARI-16116
> URL: https://issues.apache.org/jira/browse/AMBARI-16116
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Not able to edit Pig script tab on Pig views on humboldt.
> The 'path of this script file on HDFS' keeps loading and script tab is 
> disabled.
> The below API call throws error. The slash before 'user/admin' is missing
> https://ambviews-am22.cloudapp.net/api/v1/views/PIG/versions/1.0.0/instances/PIG/resources/file/%2F%2Fuser%2Fadmin%2Fpig%2Fscripts%2Fbcd1234-2016-04-22_10-17.pig
> API Response
> {"message":"user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig","status":404,"trace":"java.io.FileNotFoundException:
>  
> user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\njava.io.FileNotFoundException:
>  user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\tat 
> org.apache.hadoop.fs.azure.NativeAzureFileSystem.open(NativeAzureFileSystem.java:2034)\n\tat
>  org.apache.hadoop.fs.FileSystem.open(FileSystem.java:767)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:324)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:322)\n\tat 
> java.security.AccessController.doPrivileged(Native Method)\n\tat 
> javax.security.auth.Subject.doAs(Subject.java:415)\n\tat 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)\n\tat
>  org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi.open(HdfsApi.java:322)\n\tat 
> org.apache.ambari.view.pig.utils.FilePaginator.readPage(FilePaginator.java:76)\n\tat
>  
> org.apache.ambari.view.pig.resources.files.FileService.getFile(FileService.java:90)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:

[jira] [Updated] (AMBARI-16116) Not able to edit Pig script tab

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16116:
--
Attachment: AMBARI-16116_trunk.patch

> Not able to edit Pig script tab
> ---
>
> Key: AMBARI-16116
> URL: https://issues.apache.org/jira/browse/AMBARI-16116
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16116_trunk.patch
>
>
> Not able to edit Pig script tab on Pig views on humboldt.
> The 'path of this script file on HDFS' keeps loading and script tab is 
> disabled.
> The below API call throws error. The slash before 'user/admin' is missing
> https://ambviews-am22.cloudapp.net/api/v1/views/PIG/versions/1.0.0/instances/PIG/resources/file/%2F%2Fuser%2Fadmin%2Fpig%2Fscripts%2Fbcd1234-2016-04-22_10-17.pig
> API Response
> {"message":"user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig","status":404,"trace":"java.io.FileNotFoundException:
>  
> user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\njava.io.FileNotFoundException:
>  user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\tat 
> org.apache.hadoop.fs.azure.NativeAzureFileSystem.open(NativeAzureFileSystem.java:2034)\n\tat
>  org.apache.hadoop.fs.FileSystem.open(FileSystem.java:767)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:324)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:322)\n\tat 
> java.security.AccessController.doPrivileged(Native Method)\n\tat 
> javax.security.auth.Subject.doAs(Subject.java:415)\n\tat 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)\n\tat
>  org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi.open(HdfsApi.java:322)\n\tat 
> org.apache.ambari.view.pig.utils.FilePaginator.readPage(FilePaginator.java:76)\n\tat
>  
> org.apache.ambari.view.pig.resources.files.FileService.getFile(FileService.java:90)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)\n\t

[jira] [Updated] (AMBARI-16116) Not able to edit Pig script tab

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16116:
--
Status: Patch Available  (was: Open)

> Not able to edit Pig script tab
> ---
>
> Key: AMBARI-16116
> URL: https://issues.apache.org/jira/browse/AMBARI-16116
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16116_trunk.patch
>
>
> Not able to edit Pig script tab on Pig views on humboldt.
> The 'path of this script file on HDFS' keeps loading and script tab is 
> disabled.
> The below API call throws error. The slash before 'user/admin' is missing
> https://ambviews-am22.cloudapp.net/api/v1/views/PIG/versions/1.0.0/instances/PIG/resources/file/%2F%2Fuser%2Fadmin%2Fpig%2Fscripts%2Fbcd1234-2016-04-22_10-17.pig
> API Response
> {"message":"user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig","status":404,"trace":"java.io.FileNotFoundException:
>  
> user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\njava.io.FileNotFoundException:
>  user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\tat 
> org.apache.hadoop.fs.azure.NativeAzureFileSystem.open(NativeAzureFileSystem.java:2034)\n\tat
>  org.apache.hadoop.fs.FileSystem.open(FileSystem.java:767)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:324)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:322)\n\tat 
> java.security.AccessController.doPrivileged(Native Method)\n\tat 
> javax.security.auth.Subject.doAs(Subject.java:415)\n\tat 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)\n\tat
>  org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi.open(HdfsApi.java:322)\n\tat 
> org.apache.ambari.view.pig.utils.FilePaginator.readPage(FilePaginator.java:76)\n\tat
>  
> org.apache.ambari.view.pig.resources.files.FileService.getFile(FileService.java:90)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)\n\t

[jira] [Updated] (AMBARI-16116) Not able to edit Pig script tab

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16116:
--
Component/s: ambari-views

> Not able to edit Pig script tab
> ---
>
> Key: AMBARI-16116
> URL: https://issues.apache.org/jira/browse/AMBARI-16116
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16116_trunk.patch
>
>
> Not able to edit Pig script tab on Pig views on humboldt.
> The 'path of this script file on HDFS' keeps loading and script tab is 
> disabled.
> The below API call throws error. The slash before 'user/admin' is missing
> https://ambviews-am22.cloudapp.net/api/v1/views/PIG/versions/1.0.0/instances/PIG/resources/file/%2F%2Fuser%2Fadmin%2Fpig%2Fscripts%2Fbcd1234-2016-04-22_10-17.pig
> API Response
> {"message":"user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig","status":404,"trace":"java.io.FileNotFoundException:
>  
> user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\njava.io.FileNotFoundException:
>  user/admin/pig/scripts/bcd1234-2016-04-22_10-17.pig\n\tat 
> org.apache.hadoop.fs.azure.NativeAzureFileSystem.open(NativeAzureFileSystem.java:2034)\n\tat
>  org.apache.hadoop.fs.FileSystem.open(FileSystem.java:767)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:324)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi$14.run(HdfsApi.java:322)\n\tat 
> java.security.AccessController.doPrivileged(Native Method)\n\tat 
> javax.security.auth.Subject.doAs(Subject.java:415)\n\tat 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)\n\tat
>  org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)\n\tat 
> org.apache.ambari.view.utils.hdfs.HdfsApi.open(HdfsApi.java:322)\n\tat 
> org.apache.ambari.view.pig.utils.FilePaginator.readPage(FilePaginator.java:76)\n\tat
>  
> org.apache.ambari.view.pig.resources.files.FileService.getFile(FileService.java:90)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(Servl

[jira] [Created] (AMBARI-16138) Converting cluster to Kerberos the views should automatically adjust and work prior to the kerberization.

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16138:
-

 Summary: Converting cluster to Kerberos the views should 
automatically adjust and work prior to the kerberization.
 Key: AMBARI-16138
 URL: https://issues.apache.org/jira/browse/AMBARI-16138
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.2.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


PROBLEM: 
Converting cluster to Kerberos the views should automatically adjust and work 
prior to the kerberization. 

STEPS TO REPRODUCE: 
-create a cluster
-enable ha
-verify views are working as expected using the local ambari manage setting. 
-kerberize cluster
-verify the views are working as expected.  You should get some errors. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16138) Converting cluster to Kerberos the views should automatically adjust and work prior to the kerberization.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16138:
--
Status: Patch Available  (was: Open)

> Converting cluster to Kerberos the views should automatically adjust and work 
> prior to the kerberization.
> -
>
> Key: AMBARI-16138
> URL: https://issues.apache.org/jira/browse/AMBARI-16138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> PROBLEM: 
> Converting cluster to Kerberos the views should automatically adjust and work 
> prior to the kerberization. 
> STEPS TO REPRODUCE: 
> -create a cluster
> -enable ha
> -verify views are working as expected using the local ambari manage setting. 
> -kerberize cluster
> -verify the views are working as expected.  You should get some errors. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16138) Converting cluster to Kerberos the views should automatically adjust and work prior to the kerberization.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16138:
--
Attachment: AMBARI-16138_trunk.patch

> Converting cluster to Kerberos the views should automatically adjust and work 
> prior to the kerberization.
> -
>
> Key: AMBARI-16138
> URL: https://issues.apache.org/jira/browse/AMBARI-16138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16138_trunk.patch
>
>
> PROBLEM: 
> Converting cluster to Kerberos the views should automatically adjust and work 
> prior to the kerberization. 
> STEPS TO REPRODUCE: 
> -create a cluster
> -enable ha
> -verify views are working as expected using the local ambari manage setting. 
> -kerberize cluster
> -verify the views are working as expected.  You should get some errors. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16138) Converting cluster to Kerberos the views should automatically adjust and work prior to the kerberization.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16138:
--
Attachment: AMBARI-16138.2_trunk.patch

> Converting cluster to Kerberos the views should automatically adjust and work 
> prior to the kerberization.
> -
>
> Key: AMBARI-16138
> URL: https://issues.apache.org/jira/browse/AMBARI-16138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16138.2_trunk.patch, AMBARI-16138_trunk.patch
>
>
> PROBLEM: 
> Converting cluster to Kerberos the views should automatically adjust and work 
> prior to the kerberization. 
> STEPS TO REPRODUCE: 
> -create a cluster
> -enable ha
> -verify views are working as expected using the local ambari manage setting. 
> -kerberize cluster
> -verify the views are working as expected.  You should get some errors. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16274:
-

 Summary: Views: Simplify View Configuration for Remote Ambari 
Managed Cluster
 Key: AMBARI-16274
 URL: https://issues.apache.org/jira/browse/AMBARI-16274
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16274:
--
Status: Patch Available  (was: Open)

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16274:
--
Attachment: AMBARI-16274.2_trunk.patch
AMBARI-16274.1_trunk.patch
AMBARI-16274.3_trunk.patch
AMBARI-16274.4_trunk.patch

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16274.1_trunk.patch, AMBARI-16274.2_trunk.patch, 
> AMBARI-16274.3_trunk.patch, AMBARI-16274.4_trunk.patch
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16274:
--
Description: Simplify View configuration for Remote Ambari Managed Cluster. 
This current approach solves the Local and Remote Ambari managed clusters. The 
idea is the make remote ambari clusters available for view configurations and 
also to be available as part of Ambari APIs. The Remote Ambari clusters will 
require clsuter URL, username and password for the remote instance. 

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar commented on AMBARI-16274:
---

There are 4 different patches to this bug to cover the following areas, divided 
for ease of review:

- Ambari server
- Ambari Front-end
- Database changes 
- View changes

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16289) Upgrade existing capacity scheduler view instance after the Remote Ambari Cluster changes

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16289:
-

 Summary: Upgrade existing capacity scheduler view instance after 
the Remote Ambari Cluster changes
 Key: AMBARI-16289
 URL: https://issues.apache.org/jira/browse/AMBARI-16289
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler 
instances which is configured as Custom won't work.
We need to provide proper upgrade for those instances, so instances will work 
without any extra configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16289) Upgrade existing capacity scheduler view instance after the Remote Ambari Cluster changes

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16289:
--
Description: 
With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler 
instances which is configured as Custom won't work.
We need to provide proper upgrade for those instances, so instances will work 
without any extra configuration after upgrade

  was:
With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler 
instances which is configured as Custom won't work.
We need to provide proper upgrade for those instances, so instances will work 
without any extra configuration.


> Upgrade existing capacity scheduler view instance after the Remote Ambari 
> Cluster changes
> -
>
> Key: AMBARI-16289
> URL: https://issues.apache.org/jira/browse/AMBARI-16289
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler 
> instances which is configured as Custom won't work.
> We need to provide proper upgrade for those instances, so instances will work 
> without any extra configuration after upgrade



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16274:
--
Attachment: (was: AMBARI-16274.1_trunk.patch)

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16274.3_trunk.patch, AMBARI-16274.4_trunk.patch
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16274:
--
Attachment: (was: AMBARI-16274.2_trunk.patch)

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16274.3_trunk.patch, AMBARI-16274.4_trunk.patch
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16274:
--
Attachment: (was: AMBARI-16274.3_trunk.patch)

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16274.1_trunk.patch, AMBARI-16274.2_trunk.patch, 
> AMBARI-16274.3_trunk.patch, AMBARI-16274.4_trunk.patch
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16274:
--
Attachment: AMBARI-16274.4_trunk.patch
AMBARI-16274.1_trunk.patch
AMBARI-16274.2_trunk.patch
AMBARI-16274.3_trunk.patch

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16274.1_trunk.patch, AMBARI-16274.2_trunk.patch, 
> AMBARI-16274.3_trunk.patch, AMBARI-16274.4_trunk.patch
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16274) Views: Simplify View Configuration for Remote Ambari Managed Cluster

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16274:
--
Attachment: (was: AMBARI-16274.4_trunk.patch)

> Views: Simplify View Configuration for Remote Ambari Managed Cluster
> 
>
> Key: AMBARI-16274
> URL: https://issues.apache.org/jira/browse/AMBARI-16274
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16274.1_trunk.patch, AMBARI-16274.2_trunk.patch, 
> AMBARI-16274.3_trunk.patch, AMBARI-16274.4_trunk.patch
>
>
> Simplify View configuration for Remote Ambari Managed Cluster. This current 
> approach solves the Local and Remote Ambari managed clusters. The idea is the 
> make remote ambari clusters available for view configurations and also to be 
> available as part of Ambari APIs. The Remote Ambari clusters will require 
> clsuter URL, username and password for the remote instance. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16627) Upgrading ambari server fails

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16627:
-

 Summary: Upgrading ambari server fails
 Key: AMBARI-16627
 URL: https://issues.apache.org/jira/browse/AMBARI-16627
 Project: Ambari
  Issue Type: Bug
Reporter: Gaurav Nagar


Upgrading ambari server fails with error 


Exception in thread "main" org.apache.ambari.server.AmbariException: ERROR: 
column "local_ambari" does not exist
  Position: 40
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
Caused by: org.postgresql.util.PSQLException: ERROR: column "local_ambari" does 
not exist
  Position: 40
at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
at 
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16627) Upgrading ambari server fails when trying to create cluster_type column

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16627:
--
Affects Version/s: 2.4.0

> Upgrading ambari server fails when trying to create cluster_type column
> ---
>
> Key: AMBARI-16627
> URL: https://issues.apache.org/jira/browse/AMBARI-16627
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>
> Upgrading ambari server fails with error 
> Exception in thread "main" org.apache.ambari.server.AmbariException: ERROR: 
> column "local_ambari" does not exist
>   Position: 40
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
> Caused by: org.postgresql.util.PSQLException: ERROR: column "local_ambari" 
> does not exist
>   Position: 40
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
>   at 
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16627) Upgrading ambari server fails when trying to create cluster_type column

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16627:
--
Summary: Upgrading ambari server fails when trying to create cluster_type 
column  (was: Upgrading ambari server fails)

> Upgrading ambari server fails when trying to create cluster_type column
> ---
>
> Key: AMBARI-16627
> URL: https://issues.apache.org/jira/browse/AMBARI-16627
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>
> Upgrading ambari server fails with error 
> Exception in thread "main" org.apache.ambari.server.AmbariException: ERROR: 
> column "local_ambari" does not exist
>   Position: 40
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
> Caused by: org.postgresql.util.PSQLException: ERROR: column "local_ambari" 
> does not exist
>   Position: 40
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
>   at 
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-16627) Upgrading ambari server fails when trying to create cluster_type column

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar reassigned AMBARI-16627:
-

Assignee: Gaurav Nagar

> Upgrading ambari server fails when trying to create cluster_type column
> ---
>
> Key: AMBARI-16627
> URL: https://issues.apache.org/jira/browse/AMBARI-16627
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Upgrading ambari server fails with error 
> Exception in thread "main" org.apache.ambari.server.AmbariException: ERROR: 
> column "local_ambari" does not exist
>   Position: 40
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
> Caused by: org.postgresql.util.PSQLException: ERROR: column "local_ambari" 
> does not exist
>   Position: 40
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
>   at 
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16627) Upgrading ambari server fails when trying to create cluster_type column

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16627:
--
Fix Version/s: 2.4.0

> Upgrading ambari server fails when trying to create cluster_type column
> ---
>
> Key: AMBARI-16627
> URL: https://issues.apache.org/jira/browse/AMBARI-16627
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Upgrading ambari server fails with error 
> Exception in thread "main" org.apache.ambari.server.AmbariException: ERROR: 
> column "local_ambari" does not exist
>   Position: 40
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
> Caused by: org.postgresql.util.PSQLException: ERROR: column "local_ambari" 
> does not exist
>   Position: 40
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
>   at 
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16627) Upgrading ambari server fails when trying to create cluster_type column

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16627:
--
Status: Patch Available  (was: Open)

> Upgrading ambari server fails when trying to create cluster_type column
> ---
>
> Key: AMBARI-16627
> URL: https://issues.apache.org/jira/browse/AMBARI-16627
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Upgrading ambari server fails with error 
> Exception in thread "main" org.apache.ambari.server.AmbariException: ERROR: 
> column "local_ambari" does not exist
>   Position: 40
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
> Caused by: org.postgresql.util.PSQLException: ERROR: column "local_ambari" 
> does not exist
>   Position: 40
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
>   at 
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16627) Upgrading ambari server fails when trying to create cluster_type column

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16627:
--
Attachment: AMBARI-16627_trunk.patch

> Upgrading ambari server fails when trying to create cluster_type column
> ---
>
> Key: AMBARI-16627
> URL: https://issues.apache.org/jira/browse/AMBARI-16627
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16627_trunk.patch
>
>
> Upgrading ambari server fails with error 
> Exception in thread "main" org.apache.ambari.server.AmbariException: ERROR: 
> column "local_ambari" does not exist
>   Position: 40
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
> Caused by: org.postgresql.util.PSQLException: ERROR: column "local_ambari" 
> does not exist
>   Position: 40
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
>   at 
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16037) View Configuration Simplification

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16037:
--
Resolution: Invalid
Status: Resolved  (was: Patch Available)

> View Configuration Simplification
> -
>
> Key: AMBARI-16037
> URL: https://issues.apache.org/jira/browse/AMBARI-16037
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.2
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16037.2_trunk.patch, AMBARI-16037_trunk.patch
>
>
> Scope
> The current implementation scope is limited to improving the ease of creation 
> of View Instances, and reduce creation time issues. Also, this design leaves 
> enough extension points to be extended further on the availability of 
> subsequent centrally shared services in the case of non-Ambari managed custom 
> Clusters.
>  
> Custom Configuration for non-Ambari managed Cluster
> Cluster level configurations will be setup once to define underlying data 
> services and end-points for subsequent usage at the time of View Instance 
> creation. 
> These cluster level configurations will be maintained as references in the 
> respective View instances. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16634) Ambari Admin Privilege required for Pig and Hive View. 403 error received when opening Pig View by a non-admin user

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16634:
-

 Summary: Ambari Admin Privilege required for Pig and Hive View. 
403 error received when opening Pig View by a non-admin user
 Key: AMBARI-16634
 URL: https://issues.apache.org/jira/browse/AMBARI-16634
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.2.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


Opening Pig view with a user created in Ambari without Admin privilege an NPE 
error is initially issued. The NPE error can be cleared by granting Admin 
privilege to the user. 
If, subsequently, you remove Admin privilege from that user and log in again, 
the WebHCat service check fails with 403 error: ervice 'webhcat' check failed:
org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
requesting Ambari
org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
requesting Ambari
at 
org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
at 
org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
at 
org.apache.ambari.view.utils.ambari.AmbariApi.getHostsWithComponent(AmbariApi.java:99)
at org.apache.ambari.view.utils.ambari.Services.getWebHCatURL(Services.java:218)
at 
org.apache.ambari.view.pig.templeton.client.TempletonApiFactory.connectToTempletonApi(TempletonApiFactory.java:40)
at 
org.apache.ambari.view.pig.resources.jobs.JobResourceManager.webhcatSmokeTest(JobResourceManager.java:303)
at 
org.apache.ambari.view.pig.services.HelpService.webhcatStatus(HelpService.java:103)
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: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.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:540)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
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.w

[jira] [Updated] (AMBARI-16634) Ambari Admin Privilege required for Pig and Hive View. 403 error received when opening Pig View by a non-admin user

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16634:
--
Status: Patch Available  (was: Open)

> Ambari Admin Privilege required for Pig and Hive View. 403 error received 
> when opening Pig View by a non-admin user
> ---
>
> Key: AMBARI-16634
> URL: https://issues.apache.org/jira/browse/AMBARI-16634
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16634_trunk.patch
>
>
> Opening Pig view with a user created in Ambari without Admin privilege an NPE 
> error is initially issued. The NPE error can be cleared by granting Admin 
> privilege to the user. 
> If, subsequently, you remove Admin privilege from that user and log in again, 
> the WebHCat service check fails with 403 error: ervice 'webhcat' check failed:
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.getHostsWithComponent(AmbariApi.java:99)
> at 
> org.apache.ambari.view.utils.ambari.Services.getWebHCatURL(Services.java:218)
> at 
> org.apache.ambari.view.pig.templeton.client.TempletonApiFactory.connectToTempletonApi(TempletonApiFactory.java:40)
> at 
> org.apache.ambari.view.pig.resources.jobs.JobResourceManager.webhcatSmokeTest(JobResourceManager.java:303)
> at 
> org.apache.ambari.view.pig.services.HelpService.webhcatStatus(HelpService.java:103)
> 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: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.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:540)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at 

[jira] [Updated] (AMBARI-16634) Ambari Admin Privilege required for Pig and Hive View. 403 error received when opening Pig View by a non-admin user

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16634:
--
Attachment: AMBARI-16634_trunk.patch

> Ambari Admin Privilege required for Pig and Hive View. 403 error received 
> when opening Pig View by a non-admin user
> ---
>
> Key: AMBARI-16634
> URL: https://issues.apache.org/jira/browse/AMBARI-16634
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16634_trunk.patch
>
>
> Opening Pig view with a user created in Ambari without Admin privilege an NPE 
> error is initially issued. The NPE error can be cleared by granting Admin 
> privilege to the user. 
> If, subsequently, you remove Admin privilege from that user and log in again, 
> the WebHCat service check fails with 403 error: ervice 'webhcat' check failed:
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> org.apache.ambari.view.utils.ambari.AmbariApiException: RA040 I/O error while 
> requesting Ambari
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:176)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.requestClusterAPI(AmbariApi.java:142)
> at 
> org.apache.ambari.view.utils.ambari.AmbariApi.getHostsWithComponent(AmbariApi.java:99)
> at 
> org.apache.ambari.view.utils.ambari.Services.getWebHCatURL(Services.java:218)
> at 
> org.apache.ambari.view.pig.templeton.client.TempletonApiFactory.connectToTempletonApi(TempletonApiFactory.java:40)
> at 
> org.apache.ambari.view.pig.resources.jobs.JobResourceManager.webhcatSmokeTest(JobResourceManager.java:303)
> at 
> org.apache.ambari.view.pig.services.HelpService.webhcatStatus(HelpService.java:103)
> 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: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.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:540)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at 

[jira] [Updated] (AMBARI-16627) Upgrading ambari server fails when trying to create cluster_type column

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16627:
--
Resolution: Duplicate
Status: Resolved  (was: Patch Available)

> Upgrading ambari server fails when trying to create cluster_type column
> ---
>
> Key: AMBARI-16627
> URL: https://issues.apache.org/jira/browse/AMBARI-16627
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16627_trunk.patch
>
>
> Upgrading ambari server fails with error 
> Exception in thread "main" org.apache.ambari.server.AmbariException: ERROR: 
> column "local_ambari" does not exist
>   Position: 40
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
> Caused by: org.postgresql.util.PSQLException: ERROR: column "local_ambari" 
> does not exist
>   Position: 40
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
>   at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
>   at 
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16138) Converting cluster to Kerberos the views should automatically adjust and work prior to the kerberization.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16138:
--
Attachment: AMBARI-16138.3_trunk.patch

> Converting cluster to Kerberos the views should automatically adjust and work 
> prior to the kerberization.
> -
>
> Key: AMBARI-16138
> URL: https://issues.apache.org/jira/browse/AMBARI-16138
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16138.2_trunk.patch, AMBARI-16138.3_trunk.patch, 
> AMBARI-16138_trunk.patch
>
>
> PROBLEM: 
> Converting cluster to Kerberos the views should automatically adjust and work 
> prior to the kerberization. 
> STEPS TO REPRODUCE: 
> -create a cluster
> -enable ha
> -verify views are working as expected using the local ambari manage setting. 
> -kerberize cluster
> -verify the views are working as expected.  You should get some errors. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16652) Ambari admin test fails with Error : Unexpected request: GET /api/v1/remoteclusters

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16652:
-

 Summary: Ambari admin test fails with Error : Unexpected request: 
GET /api/v1/remoteclusters
 Key: AMBARI-16652
 URL: https://issues.apache.org/jira/browse/AMBARI-16652
 Project: Ambari
  Issue Type: Bug
  Components: ambari-admin
Affects Versions: 2.4.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


output for 'npm test'

INFO [karma]: Karma v0.12.16 server started at http://localhost:9876/
INFO [launcher]: Starting browser PhantomJS
INFO [PhantomJS 1.9.7 (Mac OS X)]: Connected on socket 77KA9I4yuxXu9jkAxdY2 
with id 16162778
LOG: null
PhantomJS 1.9.7 (Mac OS X) #CreateViewInstanceCtrl should set default property 
value before creating view instance FAILED
Error: Unexpected request: GET 
/api/v1/remoteclusters?fields=ClusterInfo/services&_=1463120420124
No more request expected
at $httpBackend 
(/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular-mocks/angular-mocks.js:1181)
at sendReq 
(/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8356)
at 
/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8088
at 
/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:11573
at 
/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:11659
at 
/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12702
at 
/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12514
at 
/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12806
at done 
(/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8379)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16652) Ambari admin test fails with Error : Unexpected request: GET /api/v1/remoteclusters

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16652:
--
Attachment: AMBARI-16652_trunk.patch

> Ambari admin test fails with Error : Unexpected request: GET 
> /api/v1/remoteclusters
> ---
>
> Key: AMBARI-16652
> URL: https://issues.apache.org/jira/browse/AMBARI-16652
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16652_trunk.patch
>
>
> output for 'npm test'
> INFO [karma]: Karma v0.12.16 server started at http://localhost:9876/
> INFO [launcher]: Starting browser PhantomJS
> INFO [PhantomJS 1.9.7 (Mac OS X)]: Connected on socket 77KA9I4yuxXu9jkAxdY2 
> with id 16162778
> LOG: null
> PhantomJS 1.9.7 (Mac OS X) #CreateViewInstanceCtrl should set default 
> property value before creating view instance FAILED
>   Error: Unexpected request: GET 
> /api/v1/remoteclusters?fields=ClusterInfo/services&_=1463120420124
>   No more request expected
>   at $httpBackend 
> (/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular-mocks/angular-mocks.js:1181)
>   at sendReq 
> (/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8356)
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8088
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:11573
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:11659
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12702
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12514
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12806
>   at done 
> (/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8379)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16656) Error while loading slider view: Unable to initialize Slider view

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16656:
-

 Summary: Error while loading slider view: Unable to initialize 
Slider view
 Key: AMBARI-16656
 URL: https://issues.apache.org/jira/browse/AMBARI-16656
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Gaurav Nagar
 Fix For: 2.4.0


ERROR:

Unable to initialize Slider view: org.apache.commons.httpclient.HttpException: 
RA060 View is not associated with any cluster. No way to request Ambari.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-16656) Error while loading slider view: Unable to initialize Slider view

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar reassigned AMBARI-16656:
-

Assignee: Gaurav Nagar

> Error while loading slider view: Unable to initialize Slider view
> -
>
> Key: AMBARI-16656
> URL: https://issues.apache.org/jira/browse/AMBARI-16656
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> ERROR:
> Unable to initialize Slider view: 
> org.apache.commons.httpclient.HttpException: RA060 View is not associated 
> with any cluster. No way to request Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16656) Error while loading slider view: Unable to initialize Slider view

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16656:
--
Attachment: AMBARI-16656_trunk.patch

> Error while loading slider view: Unable to initialize Slider view
> -
>
> Key: AMBARI-16656
> URL: https://issues.apache.org/jira/browse/AMBARI-16656
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16656_trunk.patch
>
>
> ERROR:
> Unable to initialize Slider view: 
> org.apache.commons.httpclient.HttpException: RA060 View is not associated 
> with any cluster. No way to request Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16656) Error while loading slider view: Unable to initialize Slider view

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16656:
--
Status: Patch Available  (was: Open)

> Error while loading slider view: Unable to initialize Slider view
> -
>
> Key: AMBARI-16656
> URL: https://issues.apache.org/jira/browse/AMBARI-16656
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16656_trunk.patch
>
>
> ERROR:
> Unable to initialize Slider view: 
> org.apache.commons.httpclient.HttpException: RA060 View is not associated 
> with any cluster. No way to request Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16652) Ambari admin test fails with Error : Unexpected request: GET /api/v1/remoteclusters

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16652:
--
Status: Patch Available  (was: Open)

> Ambari admin test fails with Error : Unexpected request: GET 
> /api/v1/remoteclusters
> ---
>
> Key: AMBARI-16652
> URL: https://issues.apache.org/jira/browse/AMBARI-16652
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16652_trunk.patch
>
>
> output for 'npm test'
> INFO [karma]: Karma v0.12.16 server started at http://localhost:9876/
> INFO [launcher]: Starting browser PhantomJS
> INFO [PhantomJS 1.9.7 (Mac OS X)]: Connected on socket 77KA9I4yuxXu9jkAxdY2 
> with id 16162778
> LOG: null
> PhantomJS 1.9.7 (Mac OS X) #CreateViewInstanceCtrl should set default 
> property value before creating view instance FAILED
>   Error: Unexpected request: GET 
> /api/v1/remoteclusters?fields=ClusterInfo/services&_=1463120420124
>   No more request expected
>   at $httpBackend 
> (/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular-mocks/angular-mocks.js:1181)
>   at sendReq 
> (/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8356)
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8088
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:11573
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:11659
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12702
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12514
>   at 
> /Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:12806
>   at done 
> (/Users/gnagar/code/ambari/ambari-admin/src/main/resources/ui/admin-web/app/bower_components/angular/angular.js:8379)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16659) Zeppelin View has issues in opening iFrame, when zeppelin view is installed on non-gateway node

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16659:
-

 Summary: Zeppelin View has issues in opening iFrame, when zeppelin 
view is installed on non-gateway node
 Key: AMBARI-16659
 URL: https://issues.apache.org/jira/browse/AMBARI-16659
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.4.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


Zeppelin View does not load inside Firefox in the case that zeppelin is not 
installed in gateway node.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16659) Zeppelin View has issues in opening iFrame, when zeppelin view is installed on non-gateway node

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16659:
--
Attachment: AMBARI-16659_branch-2.4.patch

> Zeppelin View has issues in opening iFrame, when zeppelin view is installed 
> on non-gateway node
> ---
>
> Key: AMBARI-16659
> URL: https://issues.apache.org/jira/browse/AMBARI-16659
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16659_branch-2.4.patch
>
>
> Zeppelin View does not load inside Firefox in the case that zeppelin is not 
> installed in gateway node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16659) Zeppelin View has issues in opening iFrame, when zeppelin view is installed on non-gateway node

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16659:
--
Status: Patch Available  (was: Open)

> Zeppelin View has issues in opening iFrame, when zeppelin view is installed 
> on non-gateway node
> ---
>
> Key: AMBARI-16659
> URL: https://issues.apache.org/jira/browse/AMBARI-16659
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16659_branch-2.4.patch
>
>
> Zeppelin View does not load inside Firefox in the case that zeppelin is not 
> installed in gateway node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16706) ADLS as default FS is not supported for any views

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16706:
-

 Summary: ADLS as default FS is not supported for any views
 Key: AMBARI-16706
 URL: https://issues.apache.org/jira/browse/AMBARI-16706
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


ADL filesystem is not supported for any views. Need to add adl related 
properties while creating filesystem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16707) Explain script on pig views encountered an IOExecption

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16707:
-

 Summary: Explain script on pig views encountered an IOExecption
 Key: AMBARI-16707
 URL: https://issues.apache.org/jira/browse/AMBARI-16707
 Project: Ambari
  Issue Type: Bug
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


Explain pig script throws IOException for wasb filesystem.
The job runs for more than 4 minutes and gets marked as "COMPLETED", but throws 
error:
2016-04-28 08:27:44,002 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 
2997: Encountered IOException. Call From wn0-ambvie to 
humbtestings2jw.blob.core.windows.net:8020 failed on socket timeout exception: 
org.apache.hadoop.net.ConnectTimeoutException: 2 millis timeout while 
waiting for channel to be ready for connect. ch : 
java.nio.channels.SocketChannel[connection-pending 
remote=humbtestings2jw.blob.core.windows.net]; 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16707) Explain script on pig views encountered an IOExecption

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16707:
--
Component/s: ambari-views

> Explain script on pig views encountered an IOExecption
> --
>
> Key: AMBARI-16707
> URL: https://issues.apache.org/jira/browse/AMBARI-16707
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> Explain pig script throws IOException for wasb filesystem.
> The job runs for more than 4 minutes and gets marked as "COMPLETED", but 
> throws error:
> 2016-04-28 08:27:44,002 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 
> 2997: Encountered IOException. Call From wn0-ambvie to 
> humbtestings2jw.blob.core.windows.net:8020 failed on socket timeout 
> exception: org.apache.hadoop.net.ConnectTimeoutException: 2 millis 
> timeout while waiting for channel to be ready for connect. ch : 
> java.nio.channels.SocketChannel[connection-pending 
> remote=humbtestings2jw.blob.core.windows.net]; 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16707) Explain script on pig views encountered an IOExecption

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16707:
--
Attachment: AMBARI-16707_branch-2.4.patch

> Explain script on pig views encountered an IOExecption
> --
>
> Key: AMBARI-16707
> URL: https://issues.apache.org/jira/browse/AMBARI-16707
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16707_branch-2.4.patch
>
>
> Explain pig script throws IOException for wasb filesystem.
> The job runs for more than 4 minutes and gets marked as "COMPLETED", but 
> throws error:
> 2016-04-28 08:27:44,002 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 
> 2997: Encountered IOException. Call From wn0-ambvie to 
> humbtestings2jw.blob.core.windows.net:8020 failed on socket timeout 
> exception: org.apache.hadoop.net.ConnectTimeoutException: 2 millis 
> timeout while waiting for channel to be ready for connect. ch : 
> java.nio.channels.SocketChannel[connection-pending 
> remote=humbtestings2jw.blob.core.windows.net]; 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16706) ADLS as default FS is not supported for any views

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16706:
--
Attachment: AMBARI-16706_branch-2.4.patch

> ADLS as default FS is not supported for any views
> -
>
> Key: AMBARI-16706
> URL: https://issues.apache.org/jira/browse/AMBARI-16706
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16706_branch-2.4.patch
>
>
> ADL filesystem is not supported for any views. Need to add adl related 
> properties while creating filesystem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16707) Explain script on pig views encountered an IOExecption

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16707:
--
Status: Patch Available  (was: Open)

> Explain script on pig views encountered an IOExecption
> --
>
> Key: AMBARI-16707
> URL: https://issues.apache.org/jira/browse/AMBARI-16707
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16707_branch-2.4.patch
>
>
> Explain pig script throws IOException for wasb filesystem.
> The job runs for more than 4 minutes and gets marked as "COMPLETED", but 
> throws error:
> 2016-04-28 08:27:44,002 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 
> 2997: Encountered IOException. Call From wn0-ambvie to 
> humbtestings2jw.blob.core.windows.net:8020 failed on socket timeout 
> exception: org.apache.hadoop.net.ConnectTimeoutException: 2 millis 
> timeout while waiting for channel to be ready for connect. ch : 
> java.nio.channels.SocketChannel[connection-pending 
> remote=humbtestings2jw.blob.core.windows.net]; 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16706) ADLS as default FS is not supported for any views

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16706:
--
Status: Patch Available  (was: Open)

> ADLS as default FS is not supported for any views
> -
>
> Key: AMBARI-16706
> URL: https://issues.apache.org/jira/browse/AMBARI-16706
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16706_branch-2.4.patch
>
>
> ADL filesystem is not supported for any views. Need to add adl related 
> properties while creating filesystem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16713) Hive View does not work with multi-bytes characters

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16713:
-

 Summary: Hive View does not work with multi-bytes characters
 Key: AMBARI-16713
 URL: https://issues.apache.org/jira/browse/AMBARI-16713
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


Hive View replaces the multi-byte characters such as Japanese to single byte if 
you use it in WHERE clause
For example:
select * from test_csv where note='あああ';
becomes
select * from test_csv where note='BBB';



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16713) Hive View does not work with multi-bytes characters

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16713:
--
Attachment: AMBARI-16713_branch-2.4.patch

> Hive View does not work with multi-bytes characters
> ---
>
> Key: AMBARI-16713
> URL: https://issues.apache.org/jira/browse/AMBARI-16713
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16713_branch-2.4.patch
>
>
> Hive View replaces the multi-byte characters such as Japanese to single byte 
> if you use it in WHERE clause
> For example:
> select * from test_csv where note='あああ';
> becomes
> select * from test_csv where note='BBB';



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16713) Hive View does not work with multi-bytes characters

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16713:
--
Status: Patch Available  (was: Open)

> Hive View does not work with multi-bytes characters
> ---
>
> Key: AMBARI-16713
> URL: https://issues.apache.org/jira/browse/AMBARI-16713
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16713_branch-2.4.patch
>
>
> Hive View replaces the multi-byte characters such as Japanese to single byte 
> if you use it in WHERE clause
> For example:
> select * from test_csv where note='あああ';
> becomes
> select * from test_csv where note='BBB';



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-16791) All created views disappear after upgrade to 2.4.0.0

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar reassigned AMBARI-16791:
-

Assignee: Gaurav Nagar

> All created views disappear after upgrade to 2.4.0.0
> 
>
> Key: AMBARI-16791
> URL: https://issues.apache.org/jira/browse/AMBARI-16791
> Project: Ambari
>  Issue Type: Bug
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
>
> STR:
> 1) Install old version (2.1.2 in our case, but it is reproducible for some 
> another configurations too)
> 2) Create all possible views (through API or by using UI)
> 3)Make ambari only upgrade
> Actual result:
> All created views disappear after upgrade to 2.4.0.0
> Issue was absent after upgrade to ambari2.2.2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16791) All created views disappear after upgrade to 2.4.0.0

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16791:
-

 Summary: All created views disappear after upgrade to 2.4.0.0
 Key: AMBARI-16791
 URL: https://issues.apache.org/jira/browse/AMBARI-16791
 Project: Ambari
  Issue Type: Bug
Reporter: Gaurav Nagar


STR:
1) Install old version (2.1.2 in our case, but it is reproducible for some 
another configurations too)
2) Create all possible views (through API or by using UI)
3)Make ambari only upgrade
Actual result:
All created views disappear after upgrade to 2.4.0.0

Issue was absent after upgrade to ambari2.2.2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16791) All created views disappear after upgrade to 2.4.0.0

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16791:
--
Affects Version/s: 2.4.0

> All created views disappear after upgrade to 2.4.0.0
> 
>
> Key: AMBARI-16791
> URL: https://issues.apache.org/jira/browse/AMBARI-16791
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade, ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> STR:
> 1) Install old version (2.1.2 in our case, but it is reproducible for some 
> another configurations too)
> 2) Create all possible views (through API or by using UI)
> 3)Make ambari only upgrade
> Actual result:
> All created views disappear after upgrade to 2.4.0.0
> Issue was absent after upgrade to ambari2.2.2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16791) All created views disappear after upgrade to 2.4.0.0

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16791:
--
Fix Version/s: 2.4.0

> All created views disappear after upgrade to 2.4.0.0
> 
>
> Key: AMBARI-16791
> URL: https://issues.apache.org/jira/browse/AMBARI-16791
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade, ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> STR:
> 1) Install old version (2.1.2 in our case, but it is reproducible for some 
> another configurations too)
> 2) Create all possible views (through API or by using UI)
> 3)Make ambari only upgrade
> Actual result:
> All created views disappear after upgrade to 2.4.0.0
> Issue was absent after upgrade to ambari2.2.2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16791) All created views disappear after upgrade to 2.4.0.0

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16791:
--
Component/s: ambari-views
 ambari-upgrade

> All created views disappear after upgrade to 2.4.0.0
> 
>
> Key: AMBARI-16791
> URL: https://issues.apache.org/jira/browse/AMBARI-16791
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade, ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> STR:
> 1) Install old version (2.1.2 in our case, but it is reproducible for some 
> another configurations too)
> 2) Create all possible views (through API or by using UI)
> 3)Make ambari only upgrade
> Actual result:
> All created views disappear after upgrade to 2.4.0.0
> Issue was absent after upgrade to ambari2.2.2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16791) All created views disappear after upgrade to 2.4.0.0

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16791:
--
Attachment: AMBARI-16791_branch-2.4.patch

> All created views disappear after upgrade to 2.4.0.0
> 
>
> Key: AMBARI-16791
> URL: https://issues.apache.org/jira/browse/AMBARI-16791
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade, ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16791_branch-2.4.patch
>
>
> STR:
> 1) Install old version (2.1.2 in our case, but it is reproducible for some 
> another configurations too)
> 2) Create all possible views (through API or by using UI)
> 3)Make ambari only upgrade
> Actual result:
> All created views disappear after upgrade to 2.4.0.0
> Issue was absent after upgrade to ambari2.2.2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16791) All created views disappear after upgrade to 2.4.0.0

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16791:
--
Status: Patch Available  (was: Open)

> All created views disappear after upgrade to 2.4.0.0
> 
>
> Key: AMBARI-16791
> URL: https://issues.apache.org/jira/browse/AMBARI-16791
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade, ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16791_branch-2.4.patch
>
>
> STR:
> 1) Install old version (2.1.2 in our case, but it is reproducible for some 
> another configurations too)
> 2) Create all possible views (through API or by using UI)
> 3)Make ambari only upgrade
> Actual result:
> All created views disappear after upgrade to 2.4.0.0
> Issue was absent after upgrade to ambari2.2.2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16812) Editing local cluster name breaks all view instances

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16812:
-

 Summary: Editing local cluster name breaks all view instances
 Key: AMBARI-16812
 URL: https://issues.apache.org/jira/browse/AMBARI-16812
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


If we edit the local cluster name from admin view, all the view instances with 
that cluster association stop working.
View Instance is attached to cluster using cluster name field not Id. If we 
chance the cluster name from admin ui the association breaks. 
It should be associated with Id field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16812) Editing local cluster name breaks all view instances

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16812:
--
Attachment: AMBARI-16812_branch-2.4.patch

> Editing local cluster name breaks all view instances
> 
>
> Key: AMBARI-16812
> URL: https://issues.apache.org/jira/browse/AMBARI-16812
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16812_branch-2.4.patch
>
>
> If we edit the local cluster name from admin view, all the view instances 
> with that cluster association stop working.
> View Instance is attached to cluster using cluster name field not Id. If we 
> chance the cluster name from admin ui the association breaks. 
> It should be associated with Id field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16812) Editing local cluster name breaks all view instances

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16812:
--
Status: Patch Available  (was: Open)

> Editing local cluster name breaks all view instances
> 
>
> Key: AMBARI-16812
> URL: https://issues.apache.org/jira/browse/AMBARI-16812
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16812_branch-2.4.patch
>
>
> If we edit the local cluster name from admin view, all the view instances 
> with that cluster association stop working.
> View Instance is attached to cluster using cluster name field not Id. If we 
> chance the cluster name from admin ui the association breaks. 
> It should be associated with Id field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16289) Upgrade existing capacity scheduler view instance after the Remote Ambari Cluster changes

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16289:
--
Attachment: AMBARI-16289_branch-2.4.patch

> Upgrade existing capacity scheduler view instance after the Remote Ambari 
> Cluster changes
> -
>
> Key: AMBARI-16289
> URL: https://issues.apache.org/jira/browse/AMBARI-16289
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16289_branch-2.4.patch
>
>
> With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler 
> instances which is configured as Custom won't work.
> We need to provide proper upgrade for those instances, so instances will work 
> without any extra configuration after upgrade



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16289) Upgrade existing capacity scheduler view instance after the Remote Ambari Cluster changes

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16289:
--
Status: Patch Available  (was: Open)

> Upgrade existing capacity scheduler view instance after the Remote Ambari 
> Cluster changes
> -
>
> Key: AMBARI-16289
> URL: https://issues.apache.org/jira/browse/AMBARI-16289
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16289_branch-2.4.patch
>
>
> With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler 
> instances which is configured as Custom won't work.
> We need to provide proper upgrade for those instances, so instances will work 
> without any extra configuration after upgrade



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16866) View Config-Non remote user able to edit queue settings in remote capacity schedular view

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16866:
-

 Summary: View Config-Non remote user able to edit queue settings 
in remote capacity schedular view
 Key: AMBARI-16866
 URL: https://issues.apache.org/jira/browse/AMBARI-16866
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: ambari-2.4.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: ambari-2.4.0


Remote Cluster -A1
Views Cluster-A2
Capacity scheduler view for A1 is configured in A2
Created user1 in A2 with view user permission. user1 is not present in A1.
user1 is able to edit queue configs from the remote view



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16866) View Config-Non remote user able to edit queue settings in remote capacity schedular view

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16866:
--
Status: Patch Available  (was: Open)

> View Config-Non remote user able to edit queue settings in remote capacity 
> schedular view
> -
>
> Key: AMBARI-16866
> URL: https://issues.apache.org/jira/browse/AMBARI-16866
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: ambari-2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-16866_branch-2.4.patch
>
>
> Remote Cluster -A1
> Views Cluster-A2
> Capacity scheduler view for A1 is configured in A2
> Created user1 in A2 with view user permission. user1 is not present in A1.
> user1 is able to edit queue configs from the remote view



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16866) View Config-Non remote user able to edit queue settings in remote capacity schedular view

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16866:
--
Attachment: AMBARI-16866_branch-2.4.patch

> View Config-Non remote user able to edit queue settings in remote capacity 
> schedular view
> -
>
> Key: AMBARI-16866
> URL: https://issues.apache.org/jira/browse/AMBARI-16866
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: ambari-2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-16866_branch-2.4.patch
>
>
> Remote Cluster -A1
> Views Cluster-A2
> Capacity scheduler view for A1 is configured in A2
> Created user1 in A2 with view user permission. user1 is not present in A1.
> user1 is able to edit queue configs from the remote view



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16868) Insert Statement in Hive View is giving error in Kerberised cluster.

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16868:
-

 Summary: Insert Statement in Hive View is giving error in 
Kerberised cluster.
 Key: AMBARI-16868
 URL: https://issues.apache.org/jira/browse/AMBARI-16868
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: ambari-2.4.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: ambari-2.4.0


 Statement : INSERT INTO TABLE testtable61 values('name','name0','secondname0');
{code}
Error Generated :
INFO : Tez session hasn't been created yet. Opening session
ERROR : Failed to execute tez graph.
org.apache.hadoop.security.AccessControlException: Permission denied: 
user=${username}, access=WRITE, inode="/user/${username}":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:1827)
at 
org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1811)
at 
org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1794)
at 
org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:71)
at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:4004)
at 
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:1102)
at 
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:630)
at 
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16868) Insert Statement in Hive View is giving error in Kerberised cluster.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16868:
--
Status: Patch Available  (was: Open)

> Insert Statement in Hive View is giving error in Kerberised cluster.
> 
>
> Key: AMBARI-16868
> URL: https://issues.apache.org/jira/browse/AMBARI-16868
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: ambari-2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-16868_branch-2.4.patch
>
>
>  Statement : INSERT INTO TABLE testtable61 
> values('name','name0','secondname0');
> {code}
> Error Generated :
> INFO : Tez session hasn't been created yet. Opening session
> ERROR : Failed to execute tez graph.
> org.apache.hadoop.security.AccessControlException: Permission denied: 
> user=${username}, access=WRITE, inode="/user/${username}":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:1827)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1811)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1794)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:71)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:4004)
> at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:1102)
> at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:630)
> at 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16868) Insert Statement in Hive View is giving error in Kerberised cluster.

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16868:
--
Attachment: AMBARI-16868_branch-2.4.patch

> Insert Statement in Hive View is giving error in Kerberised cluster.
> 
>
> Key: AMBARI-16868
> URL: https://issues.apache.org/jira/browse/AMBARI-16868
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: ambari-2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-16868_branch-2.4.patch
>
>
>  Statement : INSERT INTO TABLE testtable61 
> values('name','name0','secondname0');
> {code}
> Error Generated :
> INFO : Tez session hasn't been created yet. Opening session
> ERROR : Failed to execute tez graph.
> org.apache.hadoop.security.AccessControlException: Permission denied: 
> user=${username}, access=WRITE, inode="/user/${username}":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:1827)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1811)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1794)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:71)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:4004)
> at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:1102)
> at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:630)
> at 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16924) Invalid syntax of Oracle DDL for cluster_handle in viewinstance

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16924:
-

 Summary: Invalid syntax of Oracle DDL for cluster_handle in 
viewinstance
 Key: AMBARI-16924
 URL: https://issues.apache.org/jira/browse/AMBARI-16924
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


exceptions in ambari-server.log:
{code}
27 May 2016 08:01:01,326 ERROR [qtp-ambari-client-27] ReadHandler:94 - Caught a 
runtime exception executing a query
javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse 
Persistence Services - 2.6.2.v20151217-774c696): 
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or view 
does not exist

Error Code: 942
Call: SELECT view_instance_id, alter_names, cluster_handle, cluster_type, 
DESCRIPTION, ICON, ICON64, LABEL, name, view_name, VISIBLE, xml_driven, 
resource_id, short_url FROM viewinstance
Query: ReadAllQuery(name="allViewInstances" referenceClass=ViewInstanceEntity 
sql="SELECT view_instance_id, alter_names, cluster_handle, cluster_type, 
DESCRIPTION, ICON, ICON64, LABEL, name, view_name, VISIBLE, xml_driven, 
resource_id, short_url FROM viewinstance")
at 
org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
at 
org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
at 
org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:473)
at 
org.apache.ambari.server.orm.dao.ViewInstanceDAO.findAll(ViewInstanceDAO.java:92)
at 
org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:53)
at 
org.apache.ambari.server.security.authorization.ClusterInheritedPermissionHelper.getViewPrivilegesWithClusterPermission(ClusterInheritedPermissionHelper.java:187)
at 
org.apache.ambari.server.controller.internal.UserPrivilegeResourceProvider.getResources(UserPrivilegeResourceProvider.java:208)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
at 
org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:512)
at 
org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:464)
at 
org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:437)
at 
org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:217)
at 
org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:69)
at 
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
at 
org.apache.ambari.server.api.services.UserService.getUser(UserService.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
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.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.WebApplicat

[jira] [Updated] (AMBARI-16924) Invalid syntax of Oracle DDL for cluster_handle in viewinstance

[Gaurav Nagar (JIRA)]

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

Gaurav Nagar updated AMBARI-16924:
--
Attachment: AMBARI-16924_branch-2.4.patch

> Invalid syntax of Oracle DDL for cluster_handle in viewinstance
> ---
>
> Key: AMBARI-16924
> URL: https://issues.apache.org/jira/browse/AMBARI-16924
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16924_branch-2.4.patch
>
>
> exceptions in ambari-server.log:
> {code}
> 27 May 2016 08:01:01,326 ERROR [qtp-ambari-client-27] ReadHandler:94 - Caught 
> a runtime exception executing a query
> javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse 
> Persistence Services - 2.6.2.v20151217-774c696): 
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or 
> view does not exist
> Error Code: 942
> Call: SELECT view_instance_id, alter_names, cluster_handle, cluster_type, 
> DESCRIPTION, ICON, ICON64, LABEL, name, view_name, VISIBLE, xml_driven, 
> resource_id, short_url FROM viewinstance
> Query: ReadAllQuery(name="allViewInstances" referenceClass=ViewInstanceEntity 
> sql="SELECT view_instance_id, alter_names, cluster_handle, cluster_type, 
> DESCRIPTION, ICON, ICON64, LABEL, name, view_name, VISIBLE, xml_driven, 
> resource_id, short_url FROM viewinstance")
>   at 
> org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
>   at 
> org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
>   at 
> org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:473)
>   at 
> org.apache.ambari.server.orm.dao.ViewInstanceDAO.findAll(ViewInstanceDAO.java:92)
>   at 
> org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:53)
>   at 
> org.apache.ambari.server.security.authorization.ClusterInheritedPermissionHelper.getViewPrivilegesWithClusterPermission(ClusterInheritedPermissionHelper.java:187)
>   at 
> org.apache.ambari.server.controller.internal.UserPrivilegeResourceProvider.getResources(UserPrivilegeResourceProvider.java:208)
>   at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
>   at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
>   at 
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:512)
>   at 
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:464)
>   at 
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:437)
>   at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:217)
>   at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:69)
>   at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
>   at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
>   at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
>   at 
> org.apache.ambari.server.api.services.UserService.getUser(UserService.java:69)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> 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.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.se

[jira] [Created] (AMBARI-16948) Not able to save custom config in view config

[Gaurav Nagar (JIRA)]

Gaurav Nagar created AMBARI-16948:
-

 Summary: Not able to save custom config in view config
 Key: AMBARI-16948
 URL: https://issues.apache.org/jira/browse/AMBARI-16948
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.4.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
 Fix For: 2.4.0


While creating/updating the existing view instance, custom section is not able 
the value.
Steps:
1. Open existing File view instance.
2. Change cluster from Local to Custom.
3. Set value in WebHDFS FileSystem URI.
There is error thrown in saving the config.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)