You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2016/07/01 17:18:10 UTC

[jira] [Commented] (AMBARI-17536) The FE should always send the cluster-env config when invoking the Recommendations REST API

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

Antonenko Alexander commented on AMBARI-17536:
----------------------------------------------

+1 for the patch

> The FE should always send the cluster-env config when invoking the Recommendations REST API
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17536
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17536
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17536.patch
>
>
> The FE should always send the *{{cluster-env}}* config when invoking the Recommendations REST API. Currently this appears to not be the case, at least when querying for 'configuration-dependencies' from the service config pages. 
> Information in {{cluster-env}} may be needed to help determine recommendations... In particular, {{cluster-env/security_enabled}} will tell the stack advisor whether Kerberos is (to be) enabled or not. 
> For example when toggling Ranger plug-in states. 



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