exec_order
The exec_order store kind: its columns, partitioning, what venue and symbol mean for it, and the producers that write it.
exec_order is one of the shapes the historical store holds. A stored series lives under a
kind= path segment, and that segment is the layout contract its producers and its consumers
have to agree on: the columns, how the leaf is partitioned, and what venue and symbol mean
for this particular kind. All of it is below, rendered from the same table the runtime dispatches
on.
One decoded row becomes a crate::exec_log::ExecOrderRow. The codec that owns the schema is ExecOrderCodec; the
store writes through append_exec_orders and reads through scan_exec_orders.
Identity
venue/symbol as for exec_fill, duplicated into row columns the same way. Rows are order LIFECYCLE SNAPSHOTS, so one client_order_id appears many times with different status
This is the field most often assumed and most often wrong, which is why it is stated per kind rather than once for the store.
Columns
Every Arrow column today's writer emits, in schema order, with the codec flavor that picks its Arrow type and nullability.
| Column | Flavor | Note |
|---|---|---|
ts | i64 | — |
client_order_id | str | — |
venue | str | — |
symbol | str | — |
side | i64 | — |
qty | f64 | — |
order_type | str | — |
status | str | — |
price | f64_null | always PRESENT, and may hold SQL NULL |
trigger_price | f64_null | always PRESENT, and may hold SQL NULL |
venue_order_id | str_null | always PRESENT, and may hold SQL NULL |
filled_qty | f64 | — |
avg_fill_px | f64 | — |
Layout
| Property | Value |
|---|---|
| Partitioning | symbol |
| Grouped form | no — one series per part |
| In the cross-kind tick report | no |
Traps
price/trigger_price/venue_order_id are _null, not _add: the columns are always PRESENT and a NULL means the order genuinely had no such value (a market order has no price). Reading them as absent-tolerant would conflate 'the venue never told us' with 'an older part'.
Pinned rather than fixed: the contradiction is recorded with both sides named, so a reader meets it here instead of in production.
Known producers
Idempotency in this store is batch-level and keyed on a commit-key string, never on per-row value dedup. Two producers that collide on one template silently no-op each other's appends, and a producer that changes its template re-admits history it already wrote — both invisible unless the shapes are written side by side.
| Producer | Commit-key template |
|---|---|
crates/vike-ops/src/journal_mat.rs | mat-order-{venue}-{symbol}-{after}-{max_seq} |
⚠ That list is observed, not exhaustive, and no gate can make it so: a commit key is an ordinary string argument, so proving the list complete would mean following every call in the workspace. What is gated per listed entry is that the producer exists and spells the template verbatim. Read it as "these producers write this kind", never as "only these do".
Where this comes from
vike_data::store_kind::STORE_KINDS, exported as rosters.json at every release. The store's
own gate derives the live kind set from the code — the series directory literals, the compaction
dispatch and the write verbs — and fails until a new kind has a row, so this page cannot describe
a shape the store does not write.