Umesh Patil created ATLAS-5377:
----------------------------------
Summary: Remove duplicate NotificationREST endpoint from webapp
Key: ATLAS-5377
URL: https://issues.apache.org/jira/browse/ATLAS-5377
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 3.0.0
Reporter: Umesh Patil
h2. Background
Apache Atlas currently exposes two functionally identical REST endpoints for
hook notification ingress (HTTP → Kafka):
|| Module || Class || HTTP Path || Port ||
| webapp | org.apache.atlas.web.rest.NotificationREST | POST
/api/atlas/v2/notification/topic/\{topicName} | 21000 |
| rest-notification-webapp |
org.apache.atlas.notification.rest.web.rest.NotificationREST | POST
/rest/api/atlas/v2/notification/topic/\{topicName} | 41000 |
Both endpoints validate topic name, enforce SERVICE_NOTIFICATION_POST
authorization, and publish to Kafka via KafkaNotification.sendInternal().
Entity processing still occurs in main Atlas webapp Kafka consumers — neither
endpoint writes to the graph directly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
