You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Umesh Patil (Jira)" <ji...@apache.org> on 2026/08/18 15:25:00 UTC

[jira] [Updated] (ATLAS-5377) Remove duplicate NotificationREST endpoint from webapp

     [ https://issues.apache.org/jira/browse/ATLAS-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Umesh Patil updated ATLAS-5377:
-------------------------------
    Description: 
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(). 

  was:
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.


> 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
>            Assignee: Umesh Patil
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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(). 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)