[
https://issues.apache.org/jira/browse/SENTRY-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034785#comment-14034785
]
Jarek Jarcec Cecho commented on SENTRY-260:
-------------------------------------------
I've tried to run the changes against "DB 2 Express-C" version "10.5" and got
following error message:
{code}
Error: DB2 SQL Error: SQLCODE=-614, SQLSTATE=54008,
SQLERRMC=SENTRYPRIVILEGENAME, DRIVER=4.16.53 (state=54008,code=-614)
{code}
For query:
{code}
-- Constraints for table SENTRY_DB_PRIVILEGE for class(es)
[org.apache.sentry.provider.db.service.model.MSentryPrivilege]
CREATE UNIQUE INDEX SENTRYPRIVILEGENAME ON SENTRY_DB_PRIVILEGE (PRIVILEGE_NAME);
{code}
Based on [some
googling|http://dba.stackexchange.com/questions/19894/create-index-for-long-columns]
it seems that we're trying to create bigger index that is feasible. I'm not
sure whether it's just a limitation of my express edition or DB2 issue in
general. We've seen similar issue in MySQL that is traced by SENTRY-304 and
hence might be resolved using similar means (creating index only on prefix of
the string column)?
> Add support to use DB2 as database for sentry metastore
> --------------------------------------------------------
>
> Key: SENTRY-260
> URL: https://issues.apache.org/jira/browse/SENTRY-260
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Ruiming Zhou
> Assignee: Ruiming Zhou
> Labels: newbie
> Fix For: 1.4.0
>
> Attachments: SENTRY-260-1.patch, SENTRY-260.patch
>
>
> Currently Sentry supports derby, mysql, oracle, postgres to back its
> Metastore. We like to have DB2 database to be supported.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
