omnigraph

apunkt/omnigraph

Fork 0

mirror of https://github.com/ModernRelay/omnigraph.git synced 2026-06-27 02:39:38 +02:00

Commit graph

Author	SHA1	Message	Date
Devin AI	c0d7ae6ba4	MR-925: re-align §-references in writeups after full re-read of MR-737 On full re-read of MR-737, the section numbering used in several of the original MR-925 cross-references no longer lines up: - §5.10 in current MR-737 is 'First-class scores and rank fusion', NOT 'custom index types' / 'connector SPI'. The custom-index-type / plugin surface is §5.4 ('Persisted CSR adjacency as Lance index plugin') with the capability shape in §5.6. - §5.11 is 'Substrate choice — DataFusion vs. custom executor (A)' (resolved 2026-05-11), NOT 'per-table txn branches'. Per-table Lance native txn branches live in §5.12 ('Mutation IR, write planner, and external sources') per Ragnor 2026-04-29. - §5.5 is 'Stable row IDs as graph IDs', NOT 'reconciler pattern'. The reconciler is §5.16. - §5.8 is 'Tiering via Lance base paths', NOT SIP-related. SIP is §5.3. - The MR-925 §1.6 cross-reference to 'Open Q5' was to a pre-2026-05-11 numbering; Q5 in current §10 is 'extension rate under filters'. Each writeup now has a §-numbering note at the top mapping its findings to the current MR-737 numbering. The findings themselves are unchanged — this is a numbering-only edit. Co-Authored-By: Ragnor Comerford <ragnor.comerford@gmail.com>	2026-05-12 17:44:42 +00:00
Devin AI	88b338b56b	MR-925: exp 1.5-1.7 code-dives + 2.x deferral rationale + 3.x reference systems - exp 1.5 (bitmap-pushdown): DF 52.5 DynamicFilterPhysicalExpr supports bitmap-shaped pushdown as-written; no fork needed; Path A (per-batch evaluation) ships v1, Path B (Lance RowIdMask) is v2 optimization - exp 1.6 (txn-branches-cost): Lance per-table branches are +4N S3 PUTs per txn vs current lazy-graph-branch model; side-grade not clean win; recommend keeping current model for v1 - exp 1.7 (stable-row-id-compaction): stable row IDs already enabled everywhere in OmniGraph; Path B (OmniGraph-driven remap via FragReuseIndex public API) ships today; Path A (Lance-managed) is v2 follow-up gated on \xa71.2 plugin registry - 2.x deferred with rationale: all calibration / risk-quantification work, per ticket \xa70.3 acceptance criteria do not require 2.x - 3.1 Kuzu: factorization, semi-mask, dual-level hash index, variable-length expansion - 3.2 LanceDB: TableProvider patterns, mutation-as-IR gap, no segment-aware planning in OSS - 3.3 lance-graph: pure-SQL lowering trade-offs, 20-hop cap, Cypher AST liftable - 3.4 Comet/GlareDB/ParadeDB/Spice.ai: capability advertisement, DF API churn budget - 3.5 DuckDB: factorization calibration point (5-100x slower on multi-hop), DuckDB ext API as plugin gold standard - 3.6 Trino: cost model with 3 components (CPU/mem/network), Connector SPI as versioned plugin reference, dynamic filters analog	2026-05-12 17:36:44 +00:00

Author

SHA1

Message

Date

Devin AI

c0d7ae6ba4

MR-925: re-align §-references in writeups after full re-read of MR-737

On full re-read of MR-737, the section numbering used in several of the
original MR-925 cross-references no longer lines up:

- §5.10 in current MR-737 is 'First-class scores and rank fusion', NOT
  'custom index types' / 'connector SPI'. The custom-index-type / plugin
  surface is §5.4 ('Persisted CSR adjacency as Lance index plugin') with
  the capability shape in §5.6.
- §5.11 is 'Substrate choice — DataFusion vs. custom executor (A)'
  (resolved 2026-05-11), NOT 'per-table txn branches'. Per-table Lance
  native txn branches live in §5.12 ('Mutation IR, write planner, and
  external sources') per Ragnor 2026-04-29.
- §5.5 is 'Stable row IDs as graph IDs', NOT 'reconciler pattern'. The
  reconciler is §5.16.
- §5.8 is 'Tiering via Lance base paths', NOT SIP-related. SIP is §5.3.
- The MR-925 §1.6 cross-reference to 'Open Q5' was to a pre-2026-05-11
  numbering; Q5 in current §10 is 'extension rate under filters'.

Each writeup now has a §-numbering note at the top mapping its findings
to the current MR-737 numbering. The findings themselves are unchanged —
this is a numbering-only edit.

Co-Authored-By: Ragnor Comerford <ragnor.comerford@gmail.com>

2026-05-12 17:44:42 +00:00

Devin AI

88b338b56b

MR-925: exp 1.5-1.7 code-dives + 2.x deferral rationale + 3.x reference systems

- exp 1.5 (bitmap-pushdown): DF 52.5 DynamicFilterPhysicalExpr supports bitmap-shaped
  pushdown as-written; no fork needed; Path A (per-batch evaluation) ships v1, Path B
  (Lance RowIdMask) is v2 optimization
- exp 1.6 (txn-branches-cost): Lance per-table branches are +4N S3 PUTs per txn vs
  current lazy-graph-branch model; side-grade not clean win; recommend keeping current
  model for v1
- exp 1.7 (stable-row-id-compaction): stable row IDs already enabled everywhere in
  OmniGraph; Path B (OmniGraph-driven remap via FragReuseIndex public API) ships
  today; Path A (Lance-managed) is v2 follow-up gated on \xa71.2 plugin registry
- 2.x deferred with rationale: all calibration / risk-quantification work, per ticket
  \xa70.3 acceptance criteria do not require 2.x
- 3.1 Kuzu: factorization, semi-mask, dual-level hash index, variable-length expansion
- 3.2 LanceDB: TableProvider patterns, mutation-as-IR gap, no segment-aware planning
  in OSS
- 3.3 lance-graph: pure-SQL lowering trade-offs, 20-hop cap, Cypher AST liftable
- 3.4 Comet/GlareDB/ParadeDB/Spice.ai: capability advertisement, DF API churn budget
- 3.5 DuckDB: factorization calibration point (5-100x slower on multi-hop), DuckDB
  ext API as plugin gold standard
- 3.6 Trino: cost model with 3 components (CPU/mem/network), Connector SPI as
  versioned plugin reference, dynamic filters analog

2026-05-12 17:36:44 +00:00

2 commits