[
https://issues.apache.org/jira/browse/AMBARI-15226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273401#comment-15273401
]
Matt commented on AMBARI-15226:
-------------------------------
[~Tim Thorpe] The latest patch could not be applied on trunk
{code}
bash-3.2$ git branch
branch-2.2
branch-2.2.2
* trunk
bash-3.2$ pwd
/Users/Matt/Documents/ApacheAmbari
bash-3.2$ git apply ~/Desktop/AMBARI-15226.patch
error: patch failed:
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java:154
error:
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java:
patch does not apply
{code}
> Custom services need a way to integrate in the stack advisor process
> --------------------------------------------------------------------
>
> Key: AMBARI-15226
> URL: https://issues.apache.org/jira/browse/AMBARI-15226
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Tim Thorpe
> Assignee: Tim Thorpe
> Fix For: trunk
>
> Attachments: AMBARI-15226.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the stack advisor is defined under each stack version such as
> HDP/2.3. The problem with this is that it restricts the services that can be
> added to the stack. If a custom service is to be added, they would need to
> modify the stack advisor. If configuration recommendations and validations
> could be done at the service level then a custom service could just include
> their own recommendations and validations separately.
> The idea here is that the stack advisor will continue to give the
> recommendations and validations for the core stack services but custom
> services would be able to provide their own service advisor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
