Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi-registry/pull/131
Thanks @scottyaslan @kevdoran for reviewing this! I've incorporated your
feedback. Here are the answers to Kevin's previous questions:
> How do we envision distributing the Ranger functionality?
I think we should follow how NiFi does with its Ranger component. I added
'include-ranger' build profile to bundle the extension into NiFi Registry
binary. Since the extension is large, 50MB, I wouldn't recommend bundle it with
Registry release by default.
If needed, anyone can build the extension easily by executing:
```
$ mvn clean install -Pcontrib-check -Pinclude-ranger -f
nifi-registry-extensions/nifi-registry-ranger-extension
```
Then extract the built zip file
'nifi-registry-extensions/nifi-registry-ranger-extension/target/nifi-registry-ranger-extension-0.3.0-SNAPSHOT-bin.zip'
into some directory that NiFi Registry can access.
Specify the directory from nifi-registry.properties:
```
nifi.registry.extension.dir.ranger=./ext/ranger/lib
```
We should document these somewhere though..
> Also, is there a certain build or version of Ranger that is required for
this integration, or any special instructions for configuring things on the
Ranger end?
You need to apply a patch to Ranger since the NiFi Registry service is not
merged into Ranger yet.
Please check https://issues.apache.org/jira/browse/RANGER-2157 to get the
patch, or you can use my ranger branch.
https://github.com/ijokarumawak/ranger/tree/nifi-registry
---
