docs: cover v0.4.0 — atomic cross-shard transactions, CRDT collections, sparse vectors#183
Merged
Conversation
…s, sparse vectors
- architecture/query-language: interactive cross-shard BEGIN...COMMIT is
atomic via the Calvin vote/verdict barrier; OCC read validation aborts
stale reads with 40001; TransactionRedo WAL durability; single-node
Calvin default-on; overlay lease reaping and backpressure SQLSTATE
- documents/query-language: CRDT document collections (WITH (crdt=true)),
per-field LWW UPDATE semantics, rejected DML shapes, RETURNING,
movable-list SDK ops
- vectors/query-language: SPARSEVECTOR column type, '{dim: weight}'
literals, sparse_score ORDER BY surface
- real-time: graph edge and node-label writes emit WriteEvents
(__graph_node_labels__ stream, stable edge row_id)
- offline-sync: one-document-per-delta contract rejection
- bitemporal: AS OF read parity (predicates, ORDER BY, window functions)
- databases: pgwire listener idle watchdog vs per-database IDLE_TIMEOUT
- query-language: timestamp string-format coercion in comparisons
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
2 participants
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.
Summary
Docs catch-up for the ~277 commits merged since #174 (v0.4.0). All syntax and semantics verified against the parser and integration tests before documenting.
BEGIN ... COMMITis now atomic via the Calvin sequencer's replicated vote/verdict barrier; serializable OCC read validation (point / predicate / index-value / gathered-JOIN reads) aborting stale reads with SQLSTATE40001;TransactionRedoWAL durability (rebuilds HNSW/FTS on replay);single_node_calvindefault-on;best_effort_non_atomicsemantics clarified; 6-hour staging-overlay lease +nodedb_active_txn_overlaysgauge; backpressure SQLSTATE53200WITH (crdt=true), per-field LWW merge on PK-targeted UPDATE, tombstone DELETE, RETURNING support, rejected DML shapes (predicate UPDATE/DELETE, non-literal SET,ON CONFLICT DO UPDATE), movable-list SDK opsSPARSEVECTORcolumn type (dimensionless,'{dim: weight}'literals), auto-maintained inverted index,sparse_scoreORDER BY top-k surfaceWriteEvents (__graph_node_labels__stream; stable(src, label, dst)edge row_id; no double-publish for implicit edges)crdt_single_document_delta)AS OFreads at parity with non-temporal reads (strict-collection predicates, ORDER BY, computed/window columns)auth.idle_timeout_secs) vs per-databaseSET IDLE_TIMEOUTNotes
single_node_calvintest docstring still says the flag defaults tofalse; code default istruesincedb36bc73. Not touched here (code comment, not docs).Cargo.lock/docs/architecture.htmlworking-tree changes again excluded — unrelated.