Feat/resource watches: Users can watch resource paths and stream the bell#308
Open
St4NNi wants to merge 20 commits into
Open
Feat/resource watches: Users can watch resource paths and stream the bell#308St4NNi wants to merge 20 commits into
St4NNi wants to merge 20 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users subscribe to events on resource path prefixes and see matches in the bell as a transient activity feed. Subscriptions live on the user's notification inbox holder, holders publish their interest realm-wide, origin nodes match events locally and forward one record per interested holder, and the holder expands matches into per-subscriber inbox rows. Also adds the SSE stream endpoint so the bell updates live.
Stacked on #307 (feat/notifications); diff shows only the resource-watch commits.
Changes
{bucket}/{key}andmeta/{group_id}/{document_id}.GET/POST /api/v1/notifications/watchesandDELETE /api/v1/notifications/watches/{id}, served from any node via holder proxy over the notification transport.metadata_createdanddata_uploadednotification kinds.GET /api/v1/notifications/stream(SSE): a wake signal fires on fresh inbox writes and mark-read, the stream pushes unread counts when the holder is local, degrades to 5s holder-polling when remote, and re-resolves the holder every 60s so it survives re-ranking.GitHub Issues
Notes
Known alpha limitations, called out deliberately: