You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2014/03/25 21:13:15 UTC
[jira] [Updated] (AMBARI-5213) HCat client configs can be refreshed
only on host/component level, but not on service level
[ https://issues.apache.org/jira/browse/AMBARI-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srimanth Gunturi updated AMBARI-5213:
-------------------------------------
Attachment: AMBARI-5213.patch
Review at https://reviews.apache.org/r/19628/
> HCat client configs can be refreshed only on host/component level, but not on service level
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-5213
> URL: https://issues.apache.org/jira/browse/AMBARI-5213
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.5.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 1.5.0
>
> Attachments: AMBARI-5213.patch
>
>
> Changing Hive service configs affects "stale_configs" field of client HCAT (from service level).
> But the HCat client configs can be refreshed only on host/component level after applying change. Triggering "Restart" action from Hive service page will not affect HCat. This can be potentially inconvenient for user on large clusters.
--
This message was sent by Atlassian JIRA
(v6.2#6252)