[
https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966688#comment-15966688
]
Na Li commented on SENTRY-1614:
-------------------------------
this link is useful for Limits on InnoDB Tables
https://dev.mysql.com/doc/refman/5.7/en/innodb-restrictions.html
"If innodb_large_prefix is enabled (the default), the index key prefix limit is
3072 bytes for InnoDB tables that use DYNAMIC or COMPRESSED row format. If
innodb_large_prefix is disabled, the index key prefix limit is 767 bytes for
tables of any row format."
> DB schema key is too long for MySQL
> -----------------------------------
>
> Key: SENTRY-1614
> URL: https://issues.apache.org/jira/browse/SENTRY-1614
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Attachments: SENTRY-1614.001-sentry-ha-redesign.patch,
> SENTRY-1614.002-sentry-ha-redesign.patch
>
>
> When a schema tool is used to initialize sentry database schema we observing
> issue and the initialization of schema fails. Here are the details of the
> failure.
> *Error: Specified key was too long; max key length is 767 bytes*
> {noformat}
> Error: Specified key was too long; max key length is 767 bytes
> (state=42000,code=1071)
> Closing: 0: jdbc:mysql://192.168.56.103/sentry_db1
> org.apache.sentry.core.common.exception.SentryUserException: Schema
> initialization FAILED! Metastore state would be inconsistent !!
> *** Sentry schemaTool failed ***
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
