ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13489) MySQL Ambari Repository gives Key Too Long error messages for hostcomponentdesiredstate table.
Date Tue, 20 Oct 2015 14:00:33 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-13489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Lysnichenko updated AMBARI-13489:
----------------------------------------
    Component/s: ambari-server

> MySQL Ambari Repository gives Key Too Long error messages for hostcomponentdesiredstate
table.
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13489
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13489
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>         Attachments: AMBARI-13489.patch
>
>
> Problem:
> MySQL Ambari Repository gives Key Too Long error messages for hostcomponentdesiredstate
table.
> Steps To Reproduce:
> The comment in the Ambari-DDL-MySQL-CREATE.sql file indicates that the script was generated
on a MySQL DB with UTF8 as the character set.
> The default collation name for the DB is utf8_general_ci
> I suspect that this is preventing me from creating the Ambari database schema and giving
the message that the maximum key size is 1000 bytes.
> If the VARCHAR fields use more than one byte per character then two VARCHAR(255) fields
in the key is going to exceed 1000 bytes.
> CREATE TABLE hostcomponentdesiredstate (
> cluster_id BIGINT NOT NULL,
> component_name VARCHAR(255) NOT NULL,
> desired_stack_id BIGINT NOT NULL,
> desired_state VARCHAR(255) NOT NULL,
> host_id BIGINT NOT NULL,
> service_name VARCHAR(255) NOT NULL,
> admin_state VARCHAR(32),
> maintenance_state VARCHAR(32) NOT NULL DEFAULT 'ACTIVE',
> security_state VARCHAR(32) NOT NULL DEFAULT 'UNSECURED',
> restart_required TINYINT(1) NOT NULL DEFAULT 0,
> PRIMARY KEY (cluster_id, component_name, host_id, service_name)
> );
> Their is a work around of using MySQL 5.6 which is not the default for Cent OS 6.  You
also need to make a manual configuration change of innodb_large_prefix property.  This is
very ugly for installation process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message