[
https://issues.apache.org/jira/browse/SENTRY-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsee Yarlagadda updated SENTRY-1515:
--------------------------------------
Resolution: Fixed
Fix Version/s: sentry-ha-redesign
1.8.0
Status: Resolved (was: Patch Available)
1.8.0: 854934cb218cf113bd089f51ca4fdfe72ecef0ee
sentry-ha-redesign: 56b0f19a5a53d75b6d9bc28ff663a37f7cd182af
Thanks Sasha for the work.
Thanks Vadim, Hao, Mat, Kalyan for the reviews.
> Cleanup exception handling in SentryStore
> -----------------------------------------
>
> Key: SENTRY-1515
> URL: https://issues.apache.org/jira/browse/SENTRY-1515
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Alexander Kolbasov
> Assignee: Alexander Kolbasov
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1515.001.patch
>
>
> The changes to SENTRY-1422 and SENTRY-1512 changed the semantics of several
> API calls:
> - hasAnyServerPrivileges
> - getMSentryPrivileges
> - getMSentryPrivilegesByAuth
> - getRoleNamesForGroups
> - retrieveFullPrivilegeImage
> - retrieveFullRoleImage
> - retrieveFullPathsImage
> - getAllRoleNames
> Previously they were not marked as throwing Exception, but they still could
> do it. With the change they now ignore exceptions and just log them which may
> not be the right thing to do.
> Instead they should be marked as throwing exceptions which has consequence
> for broader APIs which should be marked as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
