You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2018/07/18 02:48:00 UTC
[jira] [Commented] (SENTRY-2307) Avoid HMS event synchronization
while sentry is fetching full snapshot.
[ https://issues.apache.org/jira/browse/SENTRY-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547314#comment-16547314 ]
Hadoop QA commented on SENTRY-2307:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12932003/SENTRY-2307.001.patch against master.
{color:red}Overall:{color} -1 due to 2 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.dbprovider.TestOwnerPrivilegesWithGrantOption
Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/3973/console
This message is automatically generated.
> Avoid HMS event synchronization while sentry is fetching full snapshot.
> ------------------------------------------------------------------------
>
> Key: SENTRY-2307
> URL: https://issues.apache.org/jira/browse/SENTRY-2307
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: 2.1.0
> Reporter: kalyan kumar kalvagadda
> Assignee: kalyan kumar kalvagadda
> Priority: Major
> Fix For: 2.1.0
>
> Attachments: SENTRY-2307.001.patch
>
>
> Sentry tries to synchronize the HMS operations to make sure that sentry server process the notifications for create/drop/alter table and databases before it receives permission grants/revokes on them. Blocking HMS threads to make sentry processes appropriate notifications makes sense but doing the same when full snapshot is taken doesn’t serve any purpose as sentry server doesn’t update sentry permissions based on HMS full snapshot. We can document that there sentry could have some stale permissions when there are any DDL operations performed at the time of snapshot creation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)