[
https://issues.apache.org/jira/browse/RANGER-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965230#comment-16965230
]
Bosco commented on RANGER-2634:
-------------------------------
Hi [~acharneski]
Thanks for your interest in contributing to Ranger.
I am curious if you considered of just creating another implementation of
AuditDestination,. e.g. ElasticAuditDestination? And override the log()
methods? In this way, you can just configure Ranger plugin to use your
destination?
I feel, the plugins are easy. However, the Ranger Portal might need more work
in supporting Elastic Search. You design might be more applicable on the portal
side.
> Modularize Solr dependency
> --------------------------
>
> Key: RANGER-2634
> URL: https://issues.apache.org/jira/browse/RANGER-2634
> Project: Ranger
> Issue Type: Wish
> Components: audit
> Reporter: Andrew Charneski
> Priority: Major
>
> Hello,
> Our organization is working on integrating and rolling out Apache Ranger for
> our internal toolset, and firstly, we'd like to thank you all for your great
> work!
> Although we have decided to adopt Ranger, for a variety of reasons we would
> very much like to use an alternate indexing service (Elasticsearch) in
> preference to the currently-supported Solr.
> We are happy to develop this extension on our own, and the initial efforts
> are underway at [https://github.com/acharneski/ranger/pull/1] however we
> would like to engage the community for guidance and suggestions with the aim
> of getting this change merged into the main codebase when it is ready.
> Our initial approach is in three main phases:
> # Isolate all usages of Solr packages/classes to pass through an API
> wrapper, delegating to the original Solr code with minimal changes. (Dev
> complete)
> # Refactor api package as a pluggable interface with greater simplicity and
> implementation agnosticism.
> # Provide alternate implementation for the new interface for Elasticsearch.
> Any guidance and feedback is appreciated. Thank you for reading!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
