Clarify LiveObjects retention as a guaranteed minimum#3271
Open
Clarify LiveObjects retention as a guaranteed minimum#3271
Conversation
- Clarify that the 6.5 MB object size limit is an aggregate across all objects on a channel, with no limit on object count - Document the 64 KiB per-operation size constraint and that objects can grow beyond it via incremental updates - Note that large objects may be split across multiple sync messages, affecting billing message counts - Add documentation for the new 'notification' inband objects mode, which sends a REST API link instead of streaming full state - Restructure inband-objects.mdx into 'objects mode' and 'notification mode' sections - Fix limits.mdx description to say "aggregate size of all objects"
The previous wording implied retention was measured from the last data update and stated exactly 90 days. Retention is actually measured from last channel activity (client attached) and 90 days is a lower bound, not an exact duration. - Rewrite storage page to say "at least 90 days", explain activity-based measurement, and add note that the period is a guaranteed minimum - Link operation storage section to retention anchor instead of hardcoding "90 days" - Update index page to say "at least 90 days"
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan for PR comments
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
zknill
force-pushed
the
zak/live-objects-size-notifications
branch
2 times, most recently
from
a7585c9 to
2e2ac11
Compare
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
1 participant
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.
The previous wording implied retention was measured from the last data update and stated exactly 90 days. Retention is actually measured from last channel activity (client attached) and 90 days is a lower bound, not an exact duration.