You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2013/12/06 18:55:35 UTC

[jira] [Updated] (AMBARI-4008) Config group names should be unique in a service, not global

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

Aleksandr Kovalenko updated AMBARI-4008:
----------------------------------------

    Attachment: AMBARI-4008.patch

> Config group names should be unique in a service, not global
> ------------------------------------------------------------
>
>                 Key: AMBARI-4008
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4008
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.3
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 1.4.3
>
>         Attachments: AMBARI-4008.patch
>
>
> - config group names are unique across all services
> - if you create a config group named "test1" in HDFS, you cannot create one called "test1" in MapReduce
> - The names should be unique in a service, not global. So that you can have a test1 in HDFS and test1 in MapReduce



--
This message was sent by Atlassian JIRA
(v6.1#6144)