[
https://issues.apache.org/jira/browse/RANGER-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705617#comment-15705617
]
Nigel Jones commented on RANGER-1234:
-------------------------------------
Yes indeed, it was filtering I was thinking of .. as we have in hive but I was
wondering how we can make it a more generic framework with some capabilities
available "ootb" and others user supplied.
Plugins might support
- masking
- filtering of specific rows
- de-identification
- ability to trigger an external event (like auditing, but kafka messages for
example, perhaps based on a data value returned)
I'm in the process of reading through/trying to understand the
code/architecture with a view to using the ranger framework for additional
plugins to connect to non-hadoop data repositories/services.
> Post-evaluation phase user extensions
> -------------------------------------
>
> Key: RANGER-1234
> URL: https://issues.apache.org/jira/browse/RANGER-1234
> Project: Ranger
> Issue Type: Improvement
> Reporter: Nigel Jones
>
> As per
> https://cwiki.apache.org/confluence/display/RANGER/Dynamic+Policy+Hooks+in+Ranger+-+Configure+and+Use
> we have the ability to add
> - content enricher
> - condition evaluator
> user extensions to a ranger plugin.
> However the third phase -- post evaluation -- could also lend itself to user
> extension such as additional user defined filtering of resultant data sets
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
