v2_3_<object> (for example v2_3_customers, v2_3_subscriptions, v2_3_events) inside a namespace Autumn assigns you.
How it works
Autumn’s pipeline continuously reshapes the live billing database into these analytics-friendly tables and syncs them to Iceberg in object storage. You attach your query engine to the catalog once — after that, data keeps flowing in and new columns appear automatically.Data freshness
Schema versioning
Thev2_3 in every table name is the schema version. The Lakehouse schema changes far less often than Autumn’s main API, and all schema updates are applied automatically — you never run a migration.
There are two kinds of change:
- In-version (additive) — a new column added to an existing
v2_3_*table. Your existing saved queries keep working unchanged; the new column simply becomes available. - New version — a future
v2_4_*. This arrives as a new table and is opt-in. Your existingv2_3_*queries keep working untouched, and you adopt the new shape only when you choose to.
Next steps
Connecting
Attach ClickHouse to your catalog.
Schema Reference
Every table and column, with the keys to join on.
Querying
Examples, cross-database joins, and footguns to avoid.