From e2170098b3a4205ad5872682f1058f4e9e0f56df Mon Sep 17 00:00:00 2001 From: =?utf8?q?Laimis=20Juzeli=C5=ABnas?= Date: Wed, 19 Mar 2025 14:33:04 +0200 Subject: [PATCH] doc/radosgw /notifications: fix topic details This commit fixes documentation about many-to-many topic relationship for notifications. The current sentence states the same fact twice instead of clarifying. Fixes: https://tracker.ceph.com/issues/64956 Signed-off-by: Laimis Juzeliunas (cherry picked from commit 058b95abe62893c5c13f02cdf7dd438b0a95a128) --- doc/radosgw/notifications.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/radosgw/notifications.rst b/doc/radosgw/notifications.rst index c358c5c01a874..93c090207166f 100644 --- a/doc/radosgw/notifications.rst +++ b/doc/radosgw/notifications.rst @@ -28,8 +28,9 @@ of event types or for all "Removed" and "Created" event types (which is the defa notification may also filter out events based on matches of the prefixes and suffixes of (1) the keys, (2) the metadata attributes attached to the object, or (3) the object tags. Regular-expression matching can also be used on these -to create filters. There can be multiple notifications for any specific topic, -and the same topic can used for multiple notifications. +to create filters. Notifications and topics have a many-to-many relationship. +A topic can receive multiple notifications and a notification could be delivered +to multiple topics. REST API has been defined so as to provide configuration and control interfaces for the bucket notification mechanism. -- 2.47.3