[
https://issues.apache.org/jira/browse/AMBARI-18532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548898#comment-15548898
]
Hadoop QA commented on AMBARI-18532:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831633/AMBARI-18532.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8814//console
This message is automatically generated.
> blueprint_setting table incorrectly defines blueprint_name column in DDL for
> MySQL
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-18532
> URL: https://issues.apache.org/jira/browse/AMBARI-18532
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-upgrade
> Affects Versions: 2.4.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18532.patch
>
>
> blueprint_setting table incorrectly defines blueprint_name column in DDL for
> MySQL:
> {code:title=Current Definition}
> CREATE TABLE blueprint_setting (
> id BIGINT NOT NULL,
> blueprint_name VARCHAR(100) NOT NULL,
> setting_name VARCHAR(100) NOT NULL,
> setting_data MEDIUMTEXT NOT NULL,
> CONSTRAINT PK_blueprint_setting PRIMARY KEY (id),
> CONSTRAINT UQ_blueprint_setting_name UNIQUE(blueprint_name,setting_name),
> CONSTRAINT FK_blueprint_setting_name FOREIGN KEY (blueprint_name)
> REFERENCES blueprint(blueprint_name));
> {code}
> {code:title=Correct Definition}
> CREATE TABLE blueprint_setting (
> id BIGINT NOT NULL,
> blueprint_name VARCHAR(255) NOT NULL,
> setting_name VARCHAR(100) NOT NULL,
> setting_data MEDIUMTEXT NOT NULL,
> CONSTRAINT PK_blueprint_setting PRIMARY KEY (id),
> CONSTRAINT UQ_blueprint_setting_name UNIQUE(blueprint_name,setting_name),
> CONSTRAINT FK_blueprint_setting_name FOREIGN KEY (blueprint_name)
> REFERENCES blueprint(blueprint_name));
> {code}
> This will cause errors when creating the table while MySQL sets up the
> foreign key constraint due to the column mismatch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
