You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Gaurav Nagar (JIRA)" <ji...@apache.org> on 2015/12/29 09:55:49 UTC

[jira] [Updated] (AMBARI-14514) Hive View: Config changes(Local <--> Custom) are not reflected unless ambari-server is restarted

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

Gaurav Nagar updated AMBARI-14514:
----------------------------------
    Summary: Hive View: Config changes(Local <--> Custom) are not reflected unless ambari-server is restarted  (was: Hive View: Config changes(Local <--> Custom) are not reflected unless ambari-server is restrated)

> Hive View: Config changes(Local <--> Custom) are not reflected unless ambari-server is restarted
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14514
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14514
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.2, 2.2.0
>            Reporter: Gaurav Nagar
>            Assignee: Gaurav Nagar
>
> Hive View: Config changes(Local <--> Custom) are not reflected unless ambari-server is restrated.
> Step -1: Create Hive view
> It is expected for Secure-AD runs Local cluster selection will not work(as per design as it unable to get WebHdfs Url address), but even after changing to Custom cluster populating all config entries(Save the configs) still Hive view throws error(unable to authenticate kerberro Token to <NameNodeaaddress>:8020).
> It means that still it is getting Local cluster configs as its unable read WebHdfs- and HIve view fails to come up.
> When ambari-server is restarted changes are reflected and works fine.



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