Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify overlapping event rules #19130

Open
wants to merge 1 commit into
base: production
Choose a base branch
from
+3 −0
Open

Clarify overlapping event rules #19130

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/content/docs/r2/buckets/event-notifications.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,3 +232,6 @@ Queue consumers receive notifications as [Messages](/queues/configuration/javasc
## Notes

- Queues [per-queue message throughput](/queues/platform/limits/) is currently 5,000 messages per second. If your workload produces more than 5,000 notifications per second, we recommend splitting notification rules across multiple queues.
- Rules without prefix/suffix apply to all objects in the bucket. To add prefix/suffix to the existing event type, delete and create a new rule.
- For the same queue, you can have same event type rules with different prefix/suffix configurations.
- For the same queue and prefix/suffix, you cannot create rules with overlapping event types. Example: If a rule handles PutObject and DeleteObject events, another rule cannot include PutObject or CopyObject for the same queue and prefix/suffix configuration.
Loading