continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent N Atkinson (JIRA)" <j...@codehaus.org>
Subject [jira] (CONTINUUM-2739) Specified key was too long during mysql data import
Date Tue, 24 Feb 2015 14:20:17 GMT

    [ https://jira.codehaus.org/browse/CONTINUUM-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=364066#comment-364066
] 

Brent N Atkinson commented on CONTINUUM-2739:
---------------------------------------------

It appears that this issue is simply a limitation on the key length support by the MySQL storage
engine:

>From http://dev.mysql.com/doc/refman/5.5/en/innodb-restrictions.html:
{quote}
By default, an index key for a single-column index can be up to 767 bytes. The same length
limit applies to any index key prefix. See Section 13.1.13, ?CREATE INDEX Syntax?. For example,
you might hit this limit with a column prefix index of more than 255 characters on a TEXT
or VARCHAR column, assuming a UTF-8 character set and the maximum of 3 bytes for each character.
When the innodb_large_prefix configuration option is enabled, this length limit is raised
to 3072 bytes, for InnoDB tables that use the DYNAMIC and COMPRESSED row formats.

If you specify an index prefix length that is greater than the allowed maximum value, the
length is silently reduced to the maximum length. In MySQL 5.6 and later, specifying an index
prefix length greater than the maximum length produces an error.

When innodb_large_prefix is enabled, attempting to create an index prefix with a key length
greater than 3072 for a REDUNDANT or COMPACT table causes an ER_INDEX_COLUMN_TOO_LONG error.
{quote}

> Specified key was too long during mysql data import
> ---------------------------------------------------
>
>                 Key: CONTINUUM-2739
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2739
>             Project: Continuum
>          Issue Type: Bug
>            Reporter: Brent N Atkinson
>
> From CONTINUUM-2558:
> When a user attempts to import data into mysql using the following command:
> {noformat}
> java -Xmx512m
>    -jar ~/.m2/repository/org/apache/continuum/data-management-cli/1.5-SNAPSHOT/data-management-cli-1.5-SNAPSHOT-app.jar
\
>    -buildsJdbcUrl jdbc:mysql://localhost:3306/continuum_continuum \
>    -usersJdbcUrl jdbc:mysql://localhost:3306/continuum_users \
>    -mode IMPORT \
>    -directory backups \
>    -databaseType OTHER \
>    -username root -groupId mysql -artifactId mysql-connector-java -artifactVersion 5.1.34
-driverClass  com.mysql.jdbc.Driver -password ""
> {noformat}
> they recieve the following error message:
> {noformat}
> Specified key was too long; max key length is 767 bytes
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message