You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Sravya Tirukkovalur (JIRA)" <ji...@apache.org> on 2014/09/20 00:19:34 UTC
[jira] [Commented] (SENTRY-454) Hive metadata changes syncup with
Sentry store should not run in error cases
[ https://issues.apache.org/jira/browse/SENTRY-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141420#comment-14141420 ]
Sravya Tirukkovalur commented on SENTRY-454:
--------------------------------------------
[~prasadm], should "if (tableEvent.getStatus())" be "if (!tableEvent.getStatus()) " instead?
> Hive metadata changes syncup with Sentry store should not run in error cases
> ----------------------------------------------------------------------------
>
> Key: SENTRY-454
> URL: https://issues.apache.org/jira/browse/SENTRY-454
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Fix For: 1.5.0
>
> Attachments: SENTRY-454.1.patch
>
>
> The Sentry plugin for metastore handles syncing up metadata changes with Sentry store. If a Db or Table is modified (eg drop, alter), then the corresponding privilege adjustments are handled by the plugin.
> This is implemented as a metastore post event listener which is fired even when the operation failed.
> We need to ensure that the syncup only happens when the listener is fired upon successful completion of the operation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)