You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Tim Thorpe (JIRA)" <ji...@apache.org> on 2016/05/02 19:07:12 UTC

[jira] [Commented] (AMBARI-15226) Custom services need a way to integrate in the stack advisor process

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

Tim Thorpe commented on AMBARI-15226:
-------------------------------------

The error encountered is not related to my change.  Once the Pivotal folks finish verifying whether there are any issues with respect to HAWQ and PXF, I will verify the patch again over trunk before getting it pushed up.

> 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)