[
https://issues.apache.org/jira/browse/SENTRY-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Mishra updated SENTRY-2476:
---------------------------------
Description:
Right now when we process a drop partition event, we fetch each path object for
paths_mapping object then find the one we want to delete and then delete it. We
should avoid fetching all objects and directly delete the path that needs to be
deleted
This affects, deleteAuthzPathsMapping, renameAuthzPathsMapping,
updateAuthzPathsMapping, and addAuthzPathsMappingCore methods that are known at
the moment
was:Right now when we process a drop partition event, we fetch each path
object for paths_mapping object then find the one we want to delete and then
delete it. We should avoid fetching all objects and directly delete the path
that needs to be deleted
> Optimize deleting specific paths for objects
> --------------------------------------------
>
> Key: SENTRY-2476
> URL: https://issues.apache.org/jira/browse/SENTRY-2476
> Project: Sentry
> Issue Type: Bug
> Reporter: Arjun Mishra
> Assignee: Arjun Mishra
> Priority: Major
> Attachments: SENTRY-2476.01.patch, SENTRY-2476.02.patch,
> SENTRY-2476.03.patch, SENTRY-2476.04.patch
>
>
> Right now when we process a drop partition event, we fetch each path object
> for paths_mapping object then find the one we want to delete and then delete
> it. We should avoid fetching all objects and directly delete the path that
> needs to be deleted
> This affects, deleteAuthzPathsMapping, renameAuthzPathsMapping,
> updateAuthzPathsMapping, and addAuthzPathsMappingCore methods that are known
> at the moment
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
