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

Nigel Jones commented on RANGER-1488:
-------------------------------------

Just an update ... the plugin has been coded and is working. The code is 
currently at [https://github.com/GaianRangerPlugin/ranger-gaian-plugin] and 
some associated issues in the github tracker

 

It's not been pushed to ranger yet as we work through a few questions around 
gaian & where the source is managed, but I wanted to update people on progress. 
If interested do get in touch and am happy to explain/demo etc..

> Create Ranger plugin for gaiandb
> --------------------------------
>
>                 Key: RANGER-1488
>                 URL: https://issues.apache.org/jira/browse/RANGER-1488
>             Project: Ranger
>          Issue Type: New Feature
>          Components: plugins
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>            Priority: Major
>              Labels: VirtualDataConnector
>         Attachments: GaianDebuggingResearch.docx
>
>
> GaianDB is a distributed, federated database built on Apache Derby.
> The documentation is at 
> https://github.com/gaiandb/gaiandb/blob/master/README.md - navigate up for 
> the source.
> As part of a Virtual Connector Project based on Atlas we are using gaianDB to 
> provide a virtualization layer. We need to control access to underlying 
> resources and will be building a Ranger plugin for gaiandb to support this. 
> GaianDB already has support for a form of policy plugin which allows the SQL 
> to be intercepted.
> It is unclear if this code will sit
>  - external to ranger/atlas ie in the gaianDB sources
>  - as a sample in the Atlas project (so that we collate what is needed for 
> the virtual connector project)
>  - as a sample, or component in the Ranger project
> However it seems helpful to describe the proposal here and get 
> feedback/dialogue in the ranger community :-)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to