[
https://issues.apache.org/jira/browse/RANGER-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paras reassigned RANGER-5679:
-----------------------------
Assignee: Paras
> Document OpenSearch audit destination setup in Ranger docker README
> -------------------------------------------------------------------
>
> Key: RANGER-5679
> URL: https://issues.apache.org/jira/browse/RANGER-5679
> Project: Ranger
> Issue Type: Improvement
> Components: audit
> Reporter: Paras
> Assignee: Paras
> Priority: Major
>
> Background
> The Ranger docker dev environment (dev-support/ranger-docker/) documents
> one-line setup steps for Solr and HDFS audit destinations, and for bringing
> up the OpenSearch container. However, once the OpenSearch native audit path
> lands (RANGER-5615), there is no documentation showing how to route audits to
> OpenSearch (audit_store=opensearch) the way Solr/HDFS are documented. The
> setup instructions across DB flavors are also inconsistent — only the
> postgres install.properties carries the OpenSearch block;
> mysql/oracle/sqlserver do not.
> Scope
> - Add OpenSearch audit setup one-liners in
> dev-support/ranger-docker/README.md, parallel to the existing Solr and HDFS
> dispatcher sections (bring up OpenSearch node → core stack → audit ingestor +
> OpenSearch dispatcher).
> - Add the audit_store=opensearch (native) configuration block to the mysql,
> oracle, and sqlserver install.properties files, matching what exists for
> postgres, with all three options (Solr / elasticsearch-legacy /
> opensearch-native) clearly labeled and commented.
> - Remove/correct stale instructions that tell users to "switch audit_store to
> elasticsearch" now that a native opensearch value exists (e.g. in the e2e
> audit script).
> - Add a brief mention of OpenSearch as a supported audit store in the
> top-level README.md (alongside Solr/Elasticsearch).
> Acceptance criteria
> - A new user can enable OpenSearch auditing by following README steps only,
> without reading source.
> - All four install.properties files (postgres/mysql/oracle/sqlserver) expose
> the same three labeled audit-store options.
> - No remaining references instructing users to use the legacy elasticsearch
> value when native opensearch is intended.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
