ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Di Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12614) Ambari should provide defining optional client dependencies in metainfo.xml. Now all client dependencies defined in metainfo.xml are required.
Date Thu, 14 Jan 2016 17:48:40 GMT

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

Di Li commented on AMBARI-12614:
--------------------------------

[~mkurapati], why not simply remove dependency of hbase client and have your service behavior
differently according to whether the host has hbase client or not...

> Ambari should provide defining optional client dependencies in metainfo.xml. Now all
client dependencies defined in metainfo.xml are required.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-12614
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12614
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Mahesh Kurapati
>              Labels: feature_custom_service
>
> In Amabri 2.1.0 release, Ambari team added new client dependency check before adding/installing
components based on JIRA https://issues.apache.org/jira/browse/AMBARI-10131. Based on this
whenever we add new component to any hosts Ambari UI checks client dependencies defined in
metainfo.xml file. If dependency clients not installed on same host then Ambari UI gives error
and not allow install that component. Because of this even service for that client not installed,
new Component not allowed to be installed.
>     For example if HBase service not installed to the cluster and try to add custom component
using Host Add action gives error that HBase client need to be installed prior to component
install. This makes HBase client become a required client even though HBase service doesn't
exist. Our custom component works without HBase we want to define HBase client as optional
dependency. i.e if HBase service exist it should check for HBase client, other wise it should
ignore HBase client exist check.



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

Mime
View raw message