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/01/18 18:01:00 UTC

[jira] [Commented] (SENTRY-2106) Remove sentry dependency on HMS table NOTIFICATION_SEQUENCE when checking if Sentry is out-of-sync with HMS

    [ https://issues.apache.org/jira/browse/SENTRY-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330875#comment-16330875 ] 

Hadoop QA commented on SENTRY-2106:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12906242/SENTRY-2106.06.patch against master.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/3625/console

This message is automatically generated.

> Remove sentry dependency on HMS table NOTIFICATION_SEQUENCE when checking if Sentry is out-of-sync with HMS
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SENTRY-2106
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2106
>             Project: Sentry
>          Issue Type: New Feature
>          Components: Sentry
>    Affects Versions: 2.1.0
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>            Priority: Major
>              Labels: features
>             Fix For: 2.1.0
>
>         Attachments: SENTRY-2106.01.patch, SENTRY-2106.02.patch, SENTRY-2106.03.patch, SENTRY-2106.04.patch, SENTRY-2106.05.patch, SENTRY-2106.06.patch
>
>
> After steady state, a full snapshot is triggered by mainly 2 cases
> # Sentry is "ahead"
> # Sentry is behind
> Case 1 has a dependency on NOTIFICATION_SEQUENCE table. This is not reliable as it was observed that sometimes NOTIFICATION_SEQUENCE and NOTIFICATION_LOG are not in sync. As a result of this unnecessary full snapshots can be triggered. 
> The fix is to remove this dependency



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)