[
https://issues.apache.org/jira/browse/SENTRY-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215395#comment-15215395
]
Hao Hao commented on SENTRY-1101:
---------------------------------
[~sravya] When you ran the test case, did you encounter any failure? The test
case will fail in my local environment after the update log is full (which the
max size is 100). Based on my debugging and current understanding, it is
because when the update log is full, it compacts the existing updateable as you
said, but it will not contain the newest updates (which is the 101th updates).
And the missing updates is the problem that I am referring here.
> 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
>
> Attachments: SENTRY-1101.0.patch
>
>
> 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)
