[
https://issues.apache.org/jira/browse/SENTRY-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Ma updated SENTRY-355:
----------------------------
Attachment: SENTRY-355.v4.patch
hi, [~prasadm] and [~lskuff], I found these problems were caused by the
SENTRY-355.v3.patch. The new patch is updated and is also available on review
board.
[~lskuff], you're right, I need fix these problems in the current JIRA, thanks
for your review.
> Support metadata read privilege enforcement for Metastore pluging
> -----------------------------------------------------------------
>
> Key: SENTRY-355
> URL: https://issues.apache.org/jira/browse/SENTRY-355
> Project: Sentry
> Issue Type: Improvement
> Reporter: Prasad Mujumdar
> Assignee: Colin Ma
> Attachments: SENTRY-355.WIP.patch, SENTRY-355.v1.patch,
> SENTRY-355.v2.patch, SENTRY-355.v3.patch, SENTRY-355.v4.patch
>
>
> The Metastore plugin currently enforces Sentry policies for metadata
> modifications. This makes it inconsistent with Hive plugin that support
> privileges for both metadata read and write.
> We should support the policy enforcement for metadata read as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
