exec_fill
The exec_fill store kind: its columns, partitioning, what venue and symbol mean for it, and the producers that write it.
exec_fill 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::ExecFillRow. The codec that owns the schema is ExecFillCodec; the
store writes through append_exec_fills and reads through scan_exec_fills.
Identity
venue/symbol are the account's execution venue and instrument — and are ALSO stored as row COLUMNS, because one decode context string cannot re-inject two values. Nothing checks the path and the columns agree
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 | — |
trade_id | str | — |
client_order_id | str | — |
venue | str | — |
symbol | str | — |
side | i64 | — |
qty | f64 | — |
px | f64 | — |
commission | f64 | — |
mark_price | f64_add | may be ABSENT ENTIRELY from a part sealed before the column was added |
liquidity_side | str_add | may be ABSENT ENTIRELY from a part sealed before the column was added |
commission_asset | str_add | may be ABSENT ENTIRELY from a part sealed before the column was added |
Layout
| Property | Value |
|---|---|
| Partitioning | symbol |
| Grouped form | no — one series per part |
| In the cross-kind tick report | no |
Traps
The ACCOUNT fill log, NOT market prints — a distinct kind from trade precisely so the two never collide on one (venue, symbol). scan_exec_fills takes no TsRange: it and scan_exec_orders are the only two members of the scan_*/load_* SERIES-READ family that do not (every other one takes a range — crates/vike-data/tests/store_kind_gate.rs's only_the_exec_reads_take_no_range is the gate), so a caller wanting a window filters after the scan. ⚠ That is a claim about the series-read family and NOT about the seam: the point-in-time and inventory verbs properties_as_of, chain_as_of, list_series, inventory and series_gaps take no range either, and for chain_as_of that is the unbounded-read trap the chain row warns about.
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-fill-{venue}-{symbol}-{after}-{max_seq} |
crates/vike-backfill/src/bin/exec_trade_backfill.rs | import-{venue}-{symbol}-{first}-{last} |
⚠ 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.