[
https://issues.apache.org/jira/browse/SENTRY-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458698#comment-16458698
]
Sergio Peña commented on SENTRY-2210:
-------------------------------------
If it does not cause conflict, then I think we should create the index
explicitly so we don't have a future discussion about indexes? Or we can leave
a comment on the sql script for mysql just that indexes are created
automatically? I think creating the index explicitly would be good it is
harmless
> AUTHZ_PATH should have index on the foreign key AUTHZ_OBJ_ID
> ------------------------------------------------------------
>
> Key: SENTRY-2210
> URL: https://issues.apache.org/jira/browse/SENTRY-2210
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
> Affects Versions: 2.1.0
> Reporter: Na Li
> Assignee: Na Li
> Priority: Major
> Attachments: SENTRY-2210.001.patch, SENTRY-2210.002.patch,
> SENTRY-2210.003.patch, SENTRY-2210.004.patch
>
>
> AUTHZ_PATH does not have index on the foreign key AUTHZ_OBJ_ID. When the
> number of entries become really large, a command like "select * from
> AUTHZ_PATH where AUTHZ_OBJ_ID = 8311512" becomes very slow because it results
> in table scan.
> To improve performance, we should add index for its foreign key in table
> AUTHZ_PATH.
> The sql script to do this in Oracle is "CREATE INDEX AUTHZ_PATH_FK_IDX on
> AUTHZ_PATH(AUTHZ_OBJ_ID);"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
