ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Babiichuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-6677) Addable and deletable components should be derived from cardinality field
Date Wed, 30 Jul 2014 16:12:40 GMT

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

Andrii Babiichuk updated AMBARI-6677:
-------------------------------------

    Attachment: AMBARI-6677.patch

> Addable and deletable components should be derived from cardinality field 
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-6677
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6677
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.7.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-6677.patch
>
>
> Currently, StackServiceComponent model hard-codes the list of service components that
can be added or deleted to a host.
> Instead of maintaining a list, we should derive the logic for allowing addition or deletion
of a host component via cardinality field.
> For deletable master components, Let zookeeper server be the only component that can
be deleted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message