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

Hudson commented on AMBARI-22274:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8305 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8305/])
AMBARI-22274. use different names for superset and druid metadata (nishant: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9ac8e534d2a4bbac672ecfed447b6213aa9954ca])
* (edit) 
ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/themes/theme.json
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.10.1/themes/theme.json


> "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize 
> service page>Druid when superset is also selected to install
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-22274
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22274
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.6.0
>            Reporter: Kishor Ramakrishnan
>            Assignee: Nishant Bangarwa
>            Priority: Blocker
>              Labels: deployment
>             Fix For: trunk, 2.6.0
>
>         Attachments: AMBARI-22274.patch
>
>
> "META DATA STORAGE CONFIG" tab is disabled in the install wizard>Customize 
> service page>Druid when superset is also selected to install.
> STR:
> 1. Navigate to Ambari admin page and start install wizard
> 2. Select Druid and Superset to be installed from Choose Services page along 
> with other required services
> 3. Navigate to Customize services page step in the wizard
> 4. "META DATA STORAGE CONFIG" tab in Druid config tab should be enabled but 
> is disabled now.
> Note: This behavior is only when Superset is chosen, and works fine without 
> Superset.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to