docs(plan): Epic B2 design — multi-source (merge-join + enrichment) - #71
Merged
Conversation
Blueprint for multi-source reports before coding (design-before-code per D23). Two explicit, user-chosen strategies, each producing a source the existing pipeline consumes unchanged: - keyset merge-join (streaming, constant memory, inner + left-outer); - enrichment/lookup (batched per page, O(pageSize), no N+1). docs/epic-b2-multisource.md has the architecture, the API sketches, the open sub-decisions (Pro vs free — no natural MIT/Pro split, so a straight monetization call — package name, join types, dynamic config, validation gate), and a B2.1-B2.4 PR breakdown. DECISIONS adds D28 (strategies) and D29 (packaging, open). PLAN reshapes Epic B2. Docs only.
|
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.
Design / decision PR — no code yet. Opens Epic B2 (multi-source), following the same design-first flow as Epic A / B1.
What's here (docs only)
docs/epic-b2-multisource.md— the blueprint:IStreamingSource<TResult>merging two same-key-ordered sources; constant memory (bounded per-key multiplicity); inner + left-outer;IBatchSource<TResult>that makes one batched lookup per page and maps it in (O(pageSize), structurally no N+1).Decisions I need from you (in the doc)
NeoReports.Sources.Join.Pro, same model as the XLSX Pro package) for consistency with your B1 choice; the free-MIT alternative maximizes adoption but forgoes B2 revenue.Once you approve the approach (and answer the above), I'll start B2.1 (enrichment) — the more contained of the two.