[
https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963455#comment-15963455
]
Na Li commented on SENTRY-1643:
-------------------------------
If the path change and perm change do not happen often, the change from Lei
would not cause serious performance issue.
If performance is an issue, we can use a stored proc at SQL server to do the
ChangeID update. there is no 2 round trip time between getting the last
changeID and increase it by one with updates. The time to lock is much shorter.
> AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be
> error-prone
> --------------------------------------------------------------------------------
>
> Key: SENTRY-1643
> URL: https://issues.apache.org/jira/browse/SENTRY-1643
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
> Affects Versions: sentry-ha-redesign
> Reporter: Hao Hao
> Assignee: Lei (Eddy) Xu
> Priority: Critical
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1643.00-sentry-ha-redesign.patch,
> SENTRY-1643.01-sentry-ha-redesign.patch
>
>
> In MSentryPermChange/MSentryPathChange table, the changeID field is
> auto-increment.
> {noformat}
> <field name="changeID" primary-key="true" value-strategy="increment">
> <column name="CHANGE_ID" jdbc-type="BIGINT" allows-null="false"/>
> </field>{noformat}
> However, found through the integration unit test TestHDFSIntegration, the
> value does not seem to be correctly auto increased. e.g Instead of increasing
> by one for each new entry, it increased by some unexpected number.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
