[ 
https://issues.apache.org/jira/browse/AMBARI-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235012#comment-14235012
 ] 

Jayush Luniya commented on AMBARI-7201:
---------------------------------------

[~nalex]
Regarding your proposal for second set of versioning in common services, it 
would lead to more complications and versioning confusion as if 
common-services/HDFS/2.6 needs to inherit from common-services/HDFS/2.4.1, if 
2.4.1 has 2 versions which version will the new 2.6 version inherit from or 
will we create new versions in the child service for each version of the parent 
service. Also this kinda defeats the purpose of common services if different 
stacks inherit from different versions of the same service version. 

Further, for the example you mentioned in which PHD stack needs a bug fix, we 
can always fix that bug in the PHD stack by overriding for example the default 
config property in the PHD stack. 

To keep things simple we will go without support for the second set of 
versioning. Let us know if you have any concerns.


> Common Services
> ---------------
>
>                 Key: AMBARI-7201
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7201
>             Project: Ambari
>          Issue Type: Epic
>          Components: stacks
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>              Labels: common-services, service, stack
>             Fix For: 2.0.0
>
>         Attachments: CommonStackServicesTechnicalDocument.pdf
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> *Problem*
> The current implementation of the Ambari stack does not allow for a common 
> set of services to be defined and reused in vendor-specific stack 
> definitions. Therefore in order for the same service to be made available to 
> different stacks, it’s definition must be copied or inherited from stack to 
> stack.  
> *Solution*
> There needs to be a repository of services that exist outside the scope of 
> any vendor-specific stack, but are accessible to vendor-specific stacks via 
> service inheritance. This set of services should be known as common services 
> and are to be maintained by the community to ensure that changes do not break 
> vendor-specific services that inherit from them. 
> See [^CommonStackServicesTechnicalDocument.pdf] for more information.



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

Reply via email to