[
https://issues.apache.org/jira/browse/SENTRY-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sravya Tirukkovalur updated SENTRY-1481:
----------------------------------------
Description:
In SentryStore#retrieveFullPathsImage, I see that we essentially loop over all
rows of MAuthzPathsMapping just to create a slightly different representation
of it. This might be pretty expensive as this table can be huge? I think we
should consider returning MAuthzPathsMapping instead.
And in equals() of MAuthzPathsMapping, seems like we do not compare paths. Just
want to make sure it is by design.
I see that we are essentially treating this object as a map on authzObjName in
application logic.
was:
In SentryStore#retrieveFullPathsImage, I see that we essentially loop over all
rows of MAuthzPathsMapping just to create a slightly different representation
of it. This might be pretty expensive as this table can be huge? I think we
should consider returning MAuthzPathsMapping instead.
And in equals() of MAuthzPathsMapping, seems like we do not compare paths.
Should we fix it?
> Sentry-1325 follow up
> ---------------------
>
> Key: SENTRY-1481
> URL: https://issues.apache.org/jira/browse/SENTRY-1481
> Project: Sentry
> Issue Type: Improvement
> Affects Versions: sentry-ha-redesign
> Reporter: Sravya Tirukkovalur
>
> In SentryStore#retrieveFullPathsImage, I see that we essentially loop over
> all rows of MAuthzPathsMapping just to create a slightly different
> representation of it. This might be pretty expensive as this table can be
> huge? I think we should consider returning MAuthzPathsMapping instead.
> And in equals() of MAuthzPathsMapping, seems like we do not compare paths.
> Just want to make sure it is by design.
> I see that we are essentially treating this object as a map on authzObjName
> in application logic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
