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 2016/03/21 22:45:25 UTC

[jira] [Commented] (SENTRY-1101) When edit log for HDFS sync in Sentry Server is full, the next Path update is not correctly setup

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

Sravya Tirukkovalur commented on SENTRY-1101:
---------------------------------------------

This seems like a bug we need to fix sooner than later, changing the version to 1.7.0 for now. [~hahao], feel free to change it back if you think this should not be targeted for 1.7.0. Also, I can pick this up too if needed. Thanks!

> When edit log for HDFS sync in Sentry Server is full, the next Path update is not correctly setup
> -------------------------------------------------------------------------------------------------
>
>                 Key: SENTRY-1101
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1101
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>            Reporter: Hao Hao
>            Assignee: Hao Hao
>             Fix For: 1.7.0
>
>
> The edit log for caching the path updates is not updated properly once the cache is full in Sentry Server side. In that case, even though the path updates will be send to NN plugin, the path updates itself is not containing the correct paths. It can cause unexpected ACL behavior issues during table creation. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)