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

Bhavik Patel commented on RANGER-2634:
--------------------------------------

Couple of things I would like to point:

1. I don't find any Index mapping file in your patch so I assume the user has 
to manually create the index and fields(attributes) mappings. 
It is better if you add an index mapping file at this location 
"security-admin/contrib/es_for_audit_setup" and add shell/python script to 
install Elasticsearch service and creating/configuring index and field mappings.

2. Testing in Kerberos environment: I had tested with ES service username and 
password, that worked but in case of Keytab it will no work, right?

> Add ElasticSearch support
> -------------------------
>
>                 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)

Reply via email to