[
https://issues.apache.org/jira/browse/AMBARI-21076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147515#comment-16147515
]
slim bouguerra commented on AMBARI-21076:
-----------------------------------------
i still see that some superset config files living within druid repo
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-superset-env.xml
not sure how this actually work ?
> Move superset as a top-level module in HDP
> ------------------------------------------
>
> Key: AMBARI-21076
> URL: https://issues.apache.org/jira/browse/AMBARI-21076
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: trunk, 2.5.1
> Reporter: Nishant Bangarwa
> Assignee: Nishant Bangarwa
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-21076.1.patch, AMBARI-21076.2.patch,
> AMBARI-21076.3.patch, AMBARI-21076.5.patch, AMBARI-21076.patch
>
>
> Superset is a generic UI which can work with multiple data stores e.g HIVE,
> DRUID and any other dataStore that supports SQLALCHEMY dialects.
> Currently superset is installed as a master component under Druid.
> This task is to move superset out of Druid so that it can be installed and
> managed independent of Druid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
