[
https://issues.apache.org/jira/browse/SENTRY-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851167#comment-15851167
]
Hao Hao commented on SENTRY-1536:
---------------------------------
Transfer +1 from CR.
> Refactor SentryStore transaction management to allow for extra transactions
> for a single permission update
> ----------------------------------------------------------------------------------------------------------
>
> Key: SENTRY-1536
> URL: https://issues.apache.org/jira/browse/SENTRY-1536
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Alexander Kolbasov
> Assignee: Hao Hao
> Labels: hdfs-sync
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1536.001-sentry-ha-redesign.patch,
> SENTRY-1536.002-sentry-ha-redesign.patch,
> SENTRY-1536.003-sentry-ha-redesign.patch,
> SENTRY-1536.004-sentry-ha-redesign.patch,
> SENTRY-1536.005-sentry-ha-redesign.patch
>
>
> To persist single permission change, it needs to combine multiple things in a
> single transaction:
> * Doing the actual operation (priv change)
> * Updating notification ID.
> It is important to do this in a single transaction to guarantee that
> notificationID handling is atomic. Current code structure doesn't allow for
> that.
> So we need to pass extra transaction code to SentryStore functions or figure
> out a generic way to do this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
