[
https://issues.apache.org/jira/browse/SENTRY-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349654#comment-15349654
]
Sravya Tirukkovalur edited comment on SENTRY-1356 at 6/25/16 2:08 PM:
----------------------------------------------------------------------
So following two things need evaluation to understand if there any problems
currently:
1. Is each event triggering a new PathsUpdate?
2. What are the events which have more than one pathChanges? Is this behavior
acceptable?
was (Author: sravya):
So following three things need evaluation to understand if there any problems
currently:
1. Is each event triggering a new PathsUpdate?
2. What are the events which have more than one pathChanges? Is this behavior
acceptable?
> Evaluate the current approach of updates from HMS
> -------------------------------------------------
>
> Key: SENTRY-1356
> URL: https://issues.apache.org/jira/browse/SENTRY-1356
> Project: Sentry
> Issue Type: Sub-task
> Reporter: Sravya Tirukkovalur
>
> Would be good to reevaluate the current approach of HMS updates. Currently,
> update contains a list of addPaths and delPaths. Some concerns we need to
> evaluate:
> 1. Hard to capture order in this model.
> 2. In UpdateatableAuthzPaths.applyPartialUpdate we seem to be adding the
> newPaths first and removing the delPaths. One caveat here is: if the newPath
> and oldPath are same, we end up deleting the path. See SENTRY-1346 for one
> such example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
