mirror of
https://github.com/ModernRelay/omnigraph.git
synced 2026-06-09 01:35:18 +02:00
c9a81266e4
Fetched https://lance.org/format/table/mem_wal/ in full via npx mdrip. The "Overview / Details / Implementation" sidebar items turned out to be anchor sections on the same URL, not separate pages. Key findings (relevant to MR-847's recovery reconciler design): * MemWAL is opt-in. Requires (1) unenforced primary key in schema, (2) explicit shard config, (3) writers using the LSM-tree write path. omnigraph does NOT enable it; we use direct write_fragments + commit(Operation::Append). * MemWAL is intra-table — addresses streaming-write throughput for one Lance base table via MemTables → flushed MemTables → async merge. It does not coordinate across multiple tables. * MemWAL's recovery is intra-table: WAL replay reconstructs MemTable state for one table. It does NOT help with omnigraph's cross-table manifest-pinned-vs-Lance-HEAD drift class. Conclusion: MR-847's recovery reconciler design is unaffected. The two operate at different abstraction layers. Borrowable: MemWAL's epoch-based fencing pattern is structurally similar to a future multi-coordinator sidecar protocol; noted on MR-847 for if MR-668 (multi-process) ever lands. |
||
|---|---|---|
| .. | ||
| releases | ||
| architecture.md | ||
| audit.md | ||
| branches-commits.md | ||
| changes.md | ||
| ci.md | ||
| cli-reference.md | ||
| cli.md | ||
| constants.md | ||
| deployment.md | ||
| embeddings.md | ||
| errors.md | ||
| execution.md | ||
| indexes.md | ||
| install.md | ||
| invariants.md | ||
| lance.md | ||
| maintenance.md | ||
| merge.md | ||
| policy.md | ||
| query-language.md | ||
| runs.md | ||
| schema-language.md | ||
| server.md | ||
| storage.md | ||
| testing.md | ||