Ramachandran Krishnan created RANGER-5658:
---------------------------------------------
Summary: Remove obsolete atlas.kafka.zookeeper.connect requirement
from Tag Sync
Key: RANGER-5658
URL: https://issues.apache.org/jira/browse/RANGER-5658
Project: Ranger
Issue Type: Task
Components: Ranger
Affects Versions: 3.0.0
Reporter: Ramachandran Krishnan
Assignee: Ramachandran Krishnan
Remove the legacy atlas.kafka.zookeeper.connect configuration requirement from
Ranger Tag Sync's Atlas Kafka source.
Background:
- Tag Sync consumes Atlas entity notifications via kafka-clients
(bootstrap.servers).
- atlas.kafka.zookeeper.connect was never used by the Atlas 2.4
KafkaNotification
consumer path; it was only required by Ranger startup validation.
- With Kafka 3.9.x / KRaft brokers, Kafka clients do not use ZooKeeper.
Changes:
- Drop TAGSYNC_ATLAS_ZOOKEEPER_ENDPOINT validation from AtlasTagSource
- Remove TAG_SOURCE_ATLAS_KAFKA_ZOOKEEPER_CONNECT from install.properties,
installprop2xml.properties, setup.py, and docker sample config
Out of scope:
- Tag Sync HA (ranger-tagsync.server.ha.zookeeper.*) — unchanged; still
requires ZooKeeper when HA is enabled
Upgrade note:
Existing deployments may still have atlas.kafka.zookeeper.connect in
conf/atlas-application.properties; it is harmless and can be removed manually.
New installs no longer generate or require it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
