[
https://issues.apache.org/jira/browse/SENTRY-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arjun Mishra updated SENTRY-2146:
---------------------------------
Description:
Targeted changes are:
# Separate input and output privileges hierarchy list from authorization
checks
# Log all relevant outputs for pre and post analyze at DEBUG level
# KeyValue constructor threw exceptions earlier without any information. Add
more information about attributes to it
# Finally in ResourceAuthorizationProvider which deals with doing the
authorization comparison, we never gracefully handled exceptions and the hive
command would end abruptly. Handling this exception and throwing it back to the
client will prompt a better log message on the client side
was:
There are a bunch of improvements that should be made to
ResourceAuthorizationProvider. For example, exceptions thrown by
privilegeFactory.createPrivilege are not gracefully handled. Makes debugging
hard.
We also need to add a lot more logging to related classes
> Add better error handling to ResourceAuthorizationProvider and improve
> logging in related classes
> -------------------------------------------------------------------------------------------------
>
> Key: SENTRY-2146
> URL: https://issues.apache.org/jira/browse/SENTRY-2146
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Arjun Mishra
> Assignee: Arjun Mishra
> Priority: Major
> Attachments: SENTRY-2146.002.patch, SENTRY-2146.005.patch,
> SENTRY-2146.01.patch, SENTRY-2146.02.patch, SENTRY-2146.03.patch,
> SENTRY-2146.04.patch, SENTRY-2146.05.patch
>
>
> Targeted changes are:
> # Separate input and output privileges hierarchy list from authorization
> checks
> # Log all relevant outputs for pre and post analyze at DEBUG level
> # KeyValue constructor threw exceptions earlier without any information. Add
> more information about attributes to it
> # Finally in ResourceAuthorizationProvider which deals with doing the
> authorization comparison, we never gracefully handled exceptions and the hive
> command would end abruptly. Handling this exception and throwing it back to
> the client will prompt a better log message on the client side
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
