|
Scheduled upgrade
Your Vault 4.0 upgrade is scheduled
We’re upgrading every Lumenrack Vault service on your account from 3.x to Vault 4.0, a new major version of Lumenrack’s managed analytics database, during a single maintenance window.
Maintenance window
Tuesday, October 6, 2026
02:00–04:00 UTC
Each service is upgraded once within this window. The exact start time for each region is on the status page.
|
Affected services
| Service |
Region |
| events-prod |
us-east-1 |
| metrics-warehouse |
eu-west-1 |
What to expect
Each service is upgraded in place with a rolling restart. Open connections are closed once, and queries in flight at that moment fail once. The Lumenrack drivers reconnect and retry automatically, so most applications see a pause of under 60 seconds.
Data, schemas, and service settings are not changed. No action is required before or after the window to complete the upgrade. Services stay on 4.0 afterwards; there is no rollback to 3.x. Further details are in the upgrade guide.
Compatibility note: MySQL integration
One change is backward-incompatible: the default MySQL type mapping. MySQL DATE columns read through the MySQL integration now map to Date32 instead of Date, which fixes pre-1970 dates. If you have a MySQL integration, you should verify it after the upgrade.
|
Notable changes in Vault 4.0
- Token authentication is available in beta. Details are in the token authentication docs.
- Async inserts are on by default for newly created services. Small inserts are batched automatically, reducing write amplification for high-throughput workloads. Existing services keep their current setting; set
async_insert = 0 on a new service to turn it off.
- Skip indexes work on JSON columns. Bloom filter, token, and ngram index types now apply to JSON columns, so granules that do not contain a queried JSON path are skipped instead of scanned.
- Column statistics are generally available. Vault now creates minmax and uniq statistics for new columns automatically and builds them during merges, so the query planner can order filters and prune parts.
- Materialized CTEs. A
WITH clause referenced more than once in a query is evaluated once and stored in a temporary table instead of being recomputed.
The full release notes are in the changelog.
Questions? Lumenrack support can help.
|
