[
https://issues.apache.org/jira/browse/AMBARI-15226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273785#comment-15273785
]
Jayush Luniya commented on AMBARI-15226:
----------------------------------------
Sorry for the delay, I was noticing some unit test failures on my Mac which
turned out to be my environment issue and had to step out this evening.
Verified unit tests pass with the patch and committed to trunk.
commit 4ce716f8e2b49e35c782b58a5889bfbf563712ae
Author: Jayush Luniya <[email protected]>
Date: Fri May 6 01:10:15 2016 -0700
AMBARI-15226 - The stack advisor should be pushed down to the services (Tim
Thorpe via jluniya)
> 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)
