docs: define Self-Describing Summary (SDS) structures - #523
Merged
Merged
Conversation
zzylol
changed the title
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.
Define SDS using three logical layers: Summary Descriptor (operator and fidelity guarantees), Data Descriptor (source and summarized population), and Summary Instance (instance metadata and actual state).
Before this PR, these concerns were distributed across schema, dictionary and record structures. After this PR, KLL with k=200 and the cpu_usage population container_type=login can share descriptors across [0,10), [10,20) and [20,30) instances carrying S0, S1 and S2. The document distinguishes an algorithm parameter from a numerical fidelity guarantee.
Documentation proposal only; no runtime or wire-format changes. Validation: git diff --check passed.