[
https://issues.apache.org/jira/browse/AMBARI-20853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-20853:
-----------------------------------------
Description:
See Epic AMBARI-20852
First step is to allow a Service's metainfo.xml file to define what type of
Service Advisor it uses, Python or Java.
For now, continue to call Python for all services since all services are not
specifying which type to use (so defaults to Python)
If set to Java, will eventually call a class to invoke the existing Service
Advisor in Python as a way to ensure compatibility.
If set to Python, continue to call the current script.
In both cases, we will continue to generate the services.json file.
Today, we call Stack Advisor on all services even if only one service is
modified, so it's ok to hardcode a service name until the UI is able to provide
that granularity.
was:
See Epic AMBARI-20852
First step is to allow a Service's metainfo.xml file to define what type of
Service Advisor it uses, Python or Java.
For now, continue to call Python for all services.
If set to Java, call a jar that ends up calling the existing Service Advisor in
Python as a way to ensure compatibility.
If set to Python, continue to call the current script.
In both cases, we will continue to generate the services.json file
> Service Advisor - Allow Service to define its Advisor Type as Python or Java
> ----------------------------------------------------------------------------
>
> Key: AMBARI-20853
> URL: https://issues.apache.org/jira/browse/AMBARI-20853
> Project: Ambari
> Issue Type: Story
> Components: service-advisor
> Affects Versions: 3.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: trunk
>
> Attachments: AMBARI-20853.patch, AMBARI-20853.trunk.patch
>
>
> See Epic AMBARI-20852
> First step is to allow a Service's metainfo.xml file to define what type of
> Service Advisor it uses, Python or Java.
> For now, continue to call Python for all services since all services are not
> specifying which type to use (so defaults to Python)
> If set to Java, will eventually call a class to invoke the existing Service
> Advisor in Python as a way to ensure compatibility.
> If set to Python, continue to call the current script.
> In both cases, we will continue to generate the services.json file.
> Today, we call Stack Advisor on all services even if only one service is
> modified, so it's ok to hardcode a service name until the UI is able to
> provide that granularity.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
