[
https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861823#comment-15861823
]
Hadoop QA commented on SENTRY-1614:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12852116/SENTRY-1614.002-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2334/console
This message is automatically generated.
> 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)
