lake.intraday_crypto dataset schema

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.

No matching rows. Clear the filter to see all records.

Current logical schema for lake.intraday_crypto

Coverage and timing

Minute-level crypto bars, keyed on the canonical `BTC-USD` ticker. Requires a literal `timestamp` range. One object per UTC day, so the range decides what is read and an unbounded query is rejected: e.g. `timestamp >= TIMESTAMP '2026-09-01' AND timestamp < TIMESTAMP '2026-09-19'`, with an explicit ticker list. For coverage questions (first/last date on file), bound a window or use lake.crypto_daily.

Minute bars for crypto, one row per minute every day of the week. `ticker` is the canonical storage form `{TICKER}-{QUOTE}` — `BTC-USD`, the same value `crypto_daily.symbol` uses. The vendor's `X:BTCUSD` form is normalised away at write time and matches nothing here (see CRYPTO_INTRADAY_SCHEMA in tigrisHydrationSchemas.ts). Always give an explicit ticker list and a bounded `timestamp` range. Because crypto trades continuously, a bar's timestamp is the only thing that establishes when its price was knowable — see the availability rule in the catalog header before joining these bars to any market with trading hours.

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 "ticker", "timestamp", "open"
FROM lake.intraday_crypto
LIMIT 20;