[
https://issues.apache.org/jira/browse/AMBARI-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-8105:
---------------------------------
Attachment: (was: AMBARI-8105.patch)
> Hide "New MySQL Database" option for Hive in Install Wizard / Add Service
> Wizard if OS family is redhat5 or sles11
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-8105
> URL: https://issues.apache.org/jira/browse/AMBARI-8105
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8105.patch
>
>
> Check /api/v1/services/AMBARI/components/AMBARI_SERVER.
> If os_type is "redhat5" or "sles11", do not show "New MySQL Database" option
> in Customize Services page for the Install Wizard / Add Service Wizard.
> In this scenario, the default selection should be "Existing MySQL database".
> Note that in the Dashboard, if Hive is already configured with "New MySQL
> Database", we still need to render it properly in Services > Hive. Configs,
> even if the OS is redhat5 or sles11. This can happen if the user installed
> the cluster prior to Ambari 1.7.0 and used "New MySQL Database". It's ok to
> always show "New MySQL Database" on this page regardless of the OS.
> Add "App.supports.alwaysEnableManagedMySQLForHive", which should be set to
> false. This is to allow the use case in which the user is using SLES 11 or
> RedHat 5 and wants to install Ambari-Managed, "New" MySQL Server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
