[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

["kalyan kumar kalvagadda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854310#comment-15854310 ] 

kalyan kumar kalvagadda commented on SENTRY-1614:
-------------------------------------------------

Adding AUTHZ_PATHS_MAPPING to primary is causing issues while adding FOREIGN KEY in oracle.

> 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
>
> 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)