You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2016/09/19 11:08:21 UTC
[jira] [Created] (AMBARI-18415) Stack definition: service component
'cardinality' inheritance not working properly
Andrew Onischuk created AMBARI-18415:
----------------------------------------
Summary: Stack definition: service component 'cardinality' inheritance not working properly
Key: AMBARI-18415
URL: https://issues.apache.org/jira/browse/AMBARI-18415
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.5.0
Attachments: AMBARI-18415.patch
In the stack definition if a property of service component is not defined in
one specific version than it will be inherited from the parent version.
The `ComponentInfo.cardinality` always has a default value of "0+" from the
moment the object is instantiated thus the inheritance logic is never applied.
This leads to if a specific version of a service component doesn't have a
property set in stack definition it won't inherit it from its parent but
rather will take the "0+" default value.
This is not the correct behaviour. First the inheritance should be applied and
only set `cardinality` to "0+" only if it can't be inherited from the parents
(as it's not defined in any of the parents up in the inheritance chain)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)