[
https://issues.apache.org/jira/browse/RANGER-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513483#comment-14513483
]
Sethukumar Ramachandran commented on RANGER-420:
------------------------------------------------
Hi Alok,
Here are my initial thoughts on your questions.
1. It is not specifically meant for Hive or HDFS in particular but in general
but could be treated as an optional one because not every use case might
require multi tenant scenarios.
2. Yes, it looks like there should be an external parameter or something of
configurable nature should exist in Ranger which can be used for the multi
tenancy. So based on this parameter every other data could be linked and could
be thought of as a one 'schema' separated from the rest. No, it is not a schema
per se.
3. Yes, of course we need to have more detailed discussions on this to have a
concrete set of requirements to start with to support multi tenancy.
Let's start concretizing these.
Thanks
Sethukumar
> 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)
