[
https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963425#comment-15963425
]
kalyan kumar kalvagadda commented on SENTRY-1643:
-------------------------------------------------
[~hahao] I agree, functionally this approach will solve this issue. but this
approach will create performance issues under traffic.
My statement makes more sense for PERM updates.
I have not looked at the logic in namenode plug-in. If we can change that logic
to handle monotonically increasing change ID's, that is best way to go.
> 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)
