Columns and types
These columns come from the same versioned logical catalog used by the query validator and engine. They describe the fields you can query. Some historical rows have missing values; fields absent from older shards can return typed NULL.
| backtest_uuid | VARCHAR |
| strategy_idx | INTEGER |
| strategy_uuid | VARCHAR |
| action_type | VARCHAR |
| action_target_symbol | VARCHAR |
| action_payload | JSON |
| condition_tree | JSON |
| n_comparisons | INTEGER |
| indicator_types | VARCHAR[] |
No matching rows. Clear the filter to see all records.
Current logical schema for lake.backtest_strategies
Coverage and timing
The logical view is backed by canonical manifest-resolved data. Query this name rather than guessing a physical database collection or object-storage path.
Backtest corpus: each run's strategy rules, one row per strategy. Join to `lake.backtest_runs` on `backtest_uuid`; `strategy_idx` orders a run's strategies. `condition_tree` and `action_payload` are JSON. Read fields with `json_extract_string(condition_tree, '$.type')`. `indicator_types` is VARCHAR[].
Run a limited query
Use a registered API key with lake scope. Select needed columns, bind user-supplied values and restrict dates when the table has a time dimension. Query results are durable parts with a schema and manifest rather than an unbounded in-memory array.
This reference documents the schema and its meaning. Run queries in your signed-in workspace; this page does not execute SQL or show private results and datasets.
SELECT "backtest_uuid", "strategy_idx", "strategy_uuid"
FROM lake.backtest_strategies
LIMIT 20;