[
https://issues.apache.org/jira/browse/AMBARI-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-4843:
--------------------------------------
Attachment: AMBARI-4843.patch
> Ambari DDL for MySQL should not create ambarirca database
> ---------------------------------------------------------
>
> Key: AMBARI-4843
> URL: https://issues.apache.org/jira/browse/AMBARI-4843
> Project: Ambari
> Issue Type: Bug
> Components: agent
> Affects Versions: 1.5.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 1.5.0
>
> Attachments: AMBARI-4843.patch
>
>
> Ambari-DDL-MySQL-CREATE.sql includes "create ambarirca" database.
> {code}
> CREATE DATABASE ambarirca;
> USE ambarirca;
> {code}
> 1) At minimum, this DDL should not be creating an ambarirca database and
> instead mix in the RCA tables with core Ambari tables (that's how Oracle DDL
> does it -- I think). Not ideal but better than creating an ambarirca database
> in this script (a user would be surprised to see this).
> 2) Alternatively, we need to split out RCA DDL from the core Ambari. We can
> doc that if you plan to use HDP 1.3.x stack that you need to to setup an RCA
> database (since RCA is only applicable to those with HDP 1.3.x stack). If we
> go this route, for consistency, we would need to do the same for the oracle
> DDL.
> Note: Right now, looks like the oracle DDL just puts the RCA tables in the
> same database as ambari core tables (basically #1 above).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
