API key
A credential created for a user with a SQL statement. Its secret is returned once and never shown again, and it is exchanged for a bearer to sign in.
Read more· Users and API keysEvery term the docs use for your tables, the state derived from them, the queries that stay open, and the storage, access and operations underneath, defined in plain words and linked to the page that defines it in full.
A to Z
Each definition restates the docs page that defines the term. Follow the link for the grammar, the examples and the rules in full.
39 terms
A credential created for a user with a SQL statement. Its secret is returned once and never shown again, and it is exchanged for a bearer to sign in.
Read more· Users and API keysA table that keeps every row it accepts and carries no primary key. Use it for events, readings and other facts that are never corrected in place.
Read more· TablesOn a federation host, the record that names one remote instance allowed to connect, with a secret minted once and per-table grants that each carry a row predicate.
Read more· FederationA clause that reads a versioned table as it stood at a given commit: each key’s winner at that commit, under the current schema. The operand is a commit sequence.
Read more· Versioned tablesA join that pairs each left row with the latest right row, per key, whose time is not after the left row’s time. With no such row, the right-side outputs are null.
Read more· JoinsA named set of columns of a keyed table that is its own write and conflict domain. Several writers each own part of one row, and a write to one group never overwrites another.
Read more· Attribute groupsThe short-lived, signed credential a password or an API key is exchanged for, and the only credential a session can be opened from.
Read more· AuthenticationThe number a tablet’s owner assigns to each of its commits, in order. It is what a read at a past commit names.
Read more· Consistency and visibilityThe position each subscriber keeps for itself on the committed feed. It acknowledges only what it has applied, resumes from the cursor after a restart, and producers never wait on it.
Read more· PSIThe clause of a streaming query that chooses the output form, append-style or carrying retractions, and the trigger that releases results: when a window closes, on an interval, on update or per event.
Read more· STREAM SELECTThe part of a node that accepts clients: HTTP for session exchange, one-shot SQL and bulk writes, and a WebSocket session that multiplexes many requests, including streaming reads, by request id.
Read more· ArchitectureConcurrent commits written to the write-ahead log together, behind one persistence barrier per group. A write is acknowledged, and published to consumers, only after its group is durable.
Read more· Storage modelA join that enriches each event with the current value of a keyed relation, read by key when the event is processed. Every event emits exactly one row.
Read more· JoinsA named query maintained continuously into an engine-owned table and read by its name. It is written only by the engine and is exact after a restart.
Read more· Views and materialized viewsA secondary index that keeps the smallest and largest value per region of data, so a range read skips regions that cannot match. Like every index, it changes how much data a read touches, never what it returns.
Read more· IndexesThe single owner of a tablet. It orders the tablet’s commits and assigns each one its commit sequence, and acknowledges a write only once its record is durable.
Read more· ArchitectureHow the rows of a shard are bucketed for pruning: none, a UTC time bucket by hour, day or month of a column, or a hash of a column into buckets.
Read more· TablesThe engine’s one internal contract for publishing committed changes to every consumer that derives state from them. It has no SQL of its own; you use it through streaming queries, transformations and materialized views.
Read more· PSIThe guarantee that when a write returns its receipt, the next read sees it, with no retry. A read that overlaps a write returns the state before it or after it, never a partly applied row.
Read more· Consistency and visibilityA named policy bound to a table that expires its rows by age.
Read more· Storage modelThe clause that decides which recording wins among versions at the same effective position. It is compared after the effective order, and the commit order breaks any remaining tie.
Read more· Versioned tablesWhat every request runs under. It is opened by exchanging a bearer for a session token, which is presented on each HTTP request and in the first frame of a WebSocket connection, never in a URL.
Read more· AuthenticationThe state a continuous query keeps, shared by every subscriber of the same statement. When the last subscriber leaves, it stays ready for a configured time so a returning subscriber joins without reseeding.
Read more· Streaming readsOn a federation consumer, the declaration that connects to a host instance with a stored credential and registers the host’s exposed tables as read-only external relations under local names.
Read more· FederationA named policy bound to a table that tiers its data between local devices and object storage.
Read more· Storage modelThe per-table choice of physical layout: a row-oriented projection, a columnar projection, or both. Omitting the clause takes the node’s default.
Read more· Storage modelA query that stays open. It sends one snapshot of its result, then exact changes to that result as new writes commit, over a WebSocket session.
Read more· Streaming readsWhat a subscriber selects changes by: a relation, a component of its stored state such as one attribute group, and a key. Never a stream name alone.
Read more· PSIA consumer of the committed feed: a streaming query session, a transformation, a materialized view, an index, a projection or a cache, each with its own durable cursor.
Read more· PSIThe read-only relations the engine maintains about itself, read with an ordinary query or followed with a streaming one. Each read needs the permission the docs list for it.
Read more· System relationsOne shard of a table, split by its shard key. Each tablet has one owner, is replicated across nodes, and splits and merges as the table grows.
Read more· ArchitectureA named, catalog-owned writer that keeps a table, or one attribute group of it, derived from other relations. It applies every committed change once, across restarts, until it is dropped.
Read more· TransformationsThe three windows a streaming query can open over a relation and a time: fixed, non-overlapping windows; overlapping windows that advance by a step; and windows closed by a gap in activity.
Read more· STREAM SELECTA table that holds one current row per primary key. A later write to the same key changes that row, and the previous value is not retained.
Read more· TablesA principal created with a SQL statement, its password passed as a bound parameter so it never appears in statement text. A new user holds no permission until a role grants one.
Read more· Users and API keysThe clause that declares the effective order of a key’s versions: where a value takes effect, for example a ledger position. It is compared first when the engine chooses the current row.
Read more· Versioned tablesA table that keeps one current row per primary key and retains every accepted version beside it, so you can read the table as it stood at a past commit.
Read more· Versioned tablesWhat a write statement returns once it has committed. A write is acknowledged only after its record is durable in the write-ahead log.
Read more· Consistency and visibilityThe local, segmented, checksummed log a tablet’s commits go to before they are acknowledged. On restart a tablet replays the suffix written after its last checkpoint.
Read more· Durability and recoveryInstall a node, create the two tables the docs build, and meet every term on this page in a statement of your own.