[jira] [Updated] (SENTRY-1894) Update field size in package.jdo for dataNucleus to match size in sql

["Na Li (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SENTRY-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Na Li updated SENTRY-1894:
--------------------------
    Resolution: Won't Fix
        Status: Resolved  (was: Patch Available)

SENTRY-2028 does not add dataNucleus schema into DB by default. So with default DN behavior, we don't need to fix this issue. 



> Update field size in package.jdo for dataNucleus to match size in sql
> ---------------------------------------------------------------------
>
>                 Key: SENTRY-1894
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1894
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 2.0.0
>            Reporter: Na Li
>            Assignee: Na Li
>         Attachments: SENTRY-1894.001.patch, SENTRY-1894.002.patch
>
>
> The unique index (`SERVER_NAME`,`DB_NAME`,`TABLE_NAME`,`COLUMN_NAME`,`URI`,`ACTION`,`WITH_GRANT_OPTION`)" in `SENTRY_DB_PRIVILEGE` at package.jdo file is too large. When running datanucleus schema tool, it complains "com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 767 bytes"
> The size of the fields `SERVER_NAME`,`DB_NAME`,`TABLE_NAME`,`COLUMN_NAME` are 4000, but the corresponding size in sql is only 128.
> We should match the size defined in package.jdo to what's in sql script, and remove `URI` from being part of the unique id. After those change, the datanucleus schema tool finishes successfully with command "mvn datanucleus:schema-create -X -e"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)