[
https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955521#comment-15955521
]
Na Li commented on SENTRY-1614:
-------------------------------
In order to run the script to initiate schema, I drop the database sentry, and
then create it.
The steps I took are
1. get code from sentry-ha-redesign branch, create database sentry, found
failure in initiating schema, add updates from me and Kalyan to fix it.
2. get code from master branch, drop and create database sentry, no problem in
initiating schema.
3. get code from sentry-ha-redesign branch, drop and create database sentry,
found failure in initiating schema, add updates from Kalyan to fix it.
> 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)
