How collections enable streaming of records.
Because a collection is a sequence of independent records, it is naturally streamable: a producer can emit records over time and a consumer can process each as it arrives, without waiting for the whole document.
~ $schema: { name: string, address: { street, city, state }, active: bool }
---
~ John Doe, { Red Street, Phoenix, AZ }, T
~ Alex, { Carnival Street, San Francisco, CA }, TFurther records for the same collection can be sent later in additional batches; a processor merges them into the same collection. Each record is validated on its own, so a malformed record does not interrupt the stream.
The full protocol lives in its own chapter. Framing, the stream-item model, schema and state, the error model, and reader and writer obligations are specified normatively in the Streaming chapter. This page only shows why a collection is streamable; the contract is there.
Streaming — the normative, platform-agnostic streaming protocol
Last updated
Was this helpful?
Was this helpful?