[jira] [Commented] (RANGER-420) Support for storing multi tenant audit data preserving the multi tenant nature in ranger schema

["Nigel Jones (JIRA)" <ji...@apache.org>]

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

Nigel Jones commented on RANGER-420:
------------------------------------

I see a need for broad multitenancy support too, in order to support easier cloud deployment.

As mentioned above this is broader than audit logs (perhaps we can update the headline?). Most requests & objects will need to be associated with a tenant id.

In addition we need to consider
 - multiple user synchronization plugins (could different tenants need the list of users/groups synced from different sources - though we could insist it's common infra so only one source)
 - changes in the atlas tag synchronizer as per  ATLAS-872 (not delivered yet), does the tag mechanism need support for multi tenancy
 - that each tenant should have a distinct namespace
 - plugins too need to have access to the tenant information in their context

.... 

> Support for storing multi tenant audit data preserving the multi tenant nature in ranger schema
> -----------------------------------------------------------------------------------------------
>
>                 Key: RANGER-420
>                 URL: https://issues.apache.org/jira/browse/RANGER-420
>             Project: Ranger
>          Issue Type: Bug
>            Reporter: Sethukumar Ramachandran
>
> We have multi tenant data injestion, processing and analytics on the data in our HDP based hadoop platform. Ranger is used as a common audit framwork in this platform. But we are not able to segregate audit data based on tenant. It might be a future requirement for us to expose audit data through some custom portal to each tenant but at this point of time we are not able to do that because data in persistent storage in ranger schema do not accomodate this factor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)