Package-level declarations

The in-memory reference dataset storage: tables of rows, each row a record with its fields at the root, and the InMemoryQueryBackend of each dataset bound to one, which passes DatasetQueryBackendSpec (the :query test fixtures). A dataset names its table in its storage binding, {"table": "<name>"} (binding).

The in-memory reference backend of the events model: the InMemoryQueryBackend of each aggregate type over the event streams streams gives for it, each as stored (EventStreamRecords.stored), in the order given. It passes QueryBackendSpec as the snapshot one does, and declares the same capabilities: every filter operator but full-text search, element scopes and their expansion, sorts, pages, counts and aggregation, HAVING, top-N, dense fill and windows left to the core.

The query backend of one record set: an aggregate type's snapshots in an InMemoryQueryStorage, or a dataset's rows in an InMemoryDatasetStorage. It evaluates every filter operator but full-text search, sort, offset and keyset pages, bounded counts, projection and aggregation; HAVING, top-N by a metric, dense fill and windows are left to the core (InMemoryQueryStorageAdapter). timeouts records the timeout of every query it received, so a test can see that the timeout reached the backend.

The in-memory reference query storage: the snapshots of every aggregate type it holds, and the InMemoryQueryBackend of each, which passes QueryBackendSpec (:query-tck). A snapshot replaces the stored one of its ref only with a higher version, as a snapshot store does; a rebuilt one (rewrite) also replaces one of the same version. The host serves the snapshot queries of a node on the memory backend from it when wow.query.memory.enabled is on: for local runs, demos and tests, whose data does not outlive the node.