sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Mujumdar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-264) SentryOnFailureHookContext missing database and table
Date Fri, 06 Jun 2014 18:42:01 GMT

    [ https://issues.apache.org/jira/browse/SENTRY-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020200#comment-14020200
] 

Prasad Mujumdar commented on SENTRY-264:
----------------------------------------

Thanks [~sravya] and [~eheyming] for confirming that.
Regarding the auth DDL statements, as I mentioned the db and table are not very relevant.
The policies are at global level. In a single statement you could be dealing with multiple
db or tables etc. Can consider including relevant details like group and role in for auth
statements in future.

If we are missing the object names in non-auth DDLs, then we should fix that.

> SentryOnFailureHookContext missing database and table
> -----------------------------------------------------
>
>                 Key: SENTRY-264
>                 URL: https://issues.apache.org/jira/browse/SENTRY-264
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: Erin Heyming
>
> The SentryOnFailureHookContext has the database and table set to null. It is important
for these values to be set in order to determine which database/table the user was trying
to access/modify when they were denied.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message