RANGER-5679: Document OpenSearch audit setup in docker README and per…#1057
Draft
paras200 wants to merge 1 commit into
Draft
RANGER-5679: Document OpenSearch audit setup in docker README and per…#1057paras200 wants to merge 1 commit into
paras200 wants to merge 1 commit into
Conversation
paras200
force-pushed
the
RANGER-5679
branch
4 times, most recently
from
3128bf5 to
aeae793
Compare
mneethiraj
reviewed
Jul 11, 2026
mneethiraj
left a comment
mneethiraj
left a comment
Contributor
There was a problem hiding this comment.
@paras200 - docker-compose.ranger.yml starts ranger-solr implicitly. With Opensearch as the audit destination, bringing up Solr is unnecessary. I suggest removing references to ranger-solr from docker-compose.ranger.yml and have Solr started explicitly similar to from docker-compose.ranger-opensearch.yml
| # export ENABLE_FILE_SYNC_SOURCE=true | ||
|
|
||
| # valid values for RANGER_DB_TYPE: mysql/postgres/oracle | ||
| # valid values for RANGER_DB_TYPE: mysql/postgres/oracle/sqlserver |
Contributor
There was a problem hiding this comment.
sqlserver is no more supported. Please revert the change in line 82.
Contributor
Author
There was a problem hiding this comment.
Thanks @mneethiraj , Done
Also, The pull request is currently in Draft mode, I still need to test everything locally again to mark it as ready for review.
…-DB install.properties - Append a commented native OpenSearch audit block (audit_store=opensearch + audit_opensearch_*) to mysql, oracle and sqlserver install.properties so the README's 'enable the OpenSearch block' step is actionable; Solr and Elasticsearch lines are left unchanged - Note that the default RANGER_DB_TYPE=postgres ships audit_store=opensearch preconfigured, so the OpenSearch setup commands auto-run with no install.properties edits; manual enablement is only needed for mysql/oracle/sqlserver - Add OpenSearch audit dispatcher one-liner to the 'audit server services individually' list in the docker README
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…-DB install.properties
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix. Create an issue in ASF JIRA before opening a pull request and
set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. RANGER-XXXX: Fix a typo in YYY))
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)