You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2025/04/14 23:27:01 UTC

[jira] [Updated] (AMBARI-21189) Service Advisor - UI to pass in instance name of Service modified to recommendation/validation APIs

     [ https://issues.apache.org/jira/browse/AMBARI-21189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei-Chiu Chuang updated AMBARI-21189:
-------------------------------------
    Fix Version/s: 3.1.0
                       (was: 3.0.0)

> Service Advisor - UI to pass in instance name of Service modified to recommendation/validation APIs
> ---------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21189
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21189
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 3.0.0
>            Reporter: Alejandro Fernandez
>            Priority: Major
>             Fix For: 3.1.0
>
>
> In order for AMBARI-20853 to have granularity at the service-level of which type of service advisor (Java or Python) to invoke, we need the UI to call the recommendation & validation APIs with the instance name of the service being modified.
> Today, we pass a list of all services in the stack, which is redundant since the backend already knows it. Instead, we need a new field called "modified_service" with the instance name.
> Today, it is calculated for all services, which adds extra overhead for services that are unrelated to configs being modified.
> The backend has all of the knowledge about service and config dependencies, so if a ZK config is being changed, it should be smart enough to also invoke Service Advisor for say Storm, Kafka, and HDFS. Similarly, if an Atlas or Ranger config is being changed, it may have to invoke service advisor for all of the services that have hooks/plugins.
> Either way, the UI shouldn't be the one to calculate this since it places additional burden and opens Ambari to miscalculations, especially since the API should require the minimal amount of input.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ambari.apache.org
For additional commands, e-mail: issues-help@ambari.apache.org