Skip to main content

Module record

Module record 

Source
Expand description

Core record types: payloads, metadata, and the flow-control signal.

A Record is what moves through an operator chain: a payload (which may borrow from the source’s buffers), a Copy metadata struct, and a clone of the source batch’s acknowledgement handle (AckRef). Records are born inside a chain’s push_batch call (deserialization) and die inside the same call (serialized into shard frames, filtered out, or failed) — they are never stored across the chain boundary, which is what makes borrowed payloads sound. See docs/DESIGN.md (§ Frozen v1 contracts).

Structs§

PartitionId
Identifier of a source partition (dense, source-assigned).
RawPayload
A raw payload borrowed from the source’s buffers, valid for 'buf.
Record
A record flowing through the chain.
RecordMeta
Per-record metadata. Copy, no drop glue — moves through operators for free and never touches the heap.

Enums§

Flow
Flow-control result of pushing one record downstream.

Functions§

stable_key_hash
Stable, seedless 64-bit hash for shard routing (FNV-1a). Not for adversarial input — routing only. Stability across processes, versions, and platforms is a contract: changing this function reshuffles shards.