cube-js/cube · warning
The CUBEJS_DB_CATALOG is deprecated. Please, use the CUBEJS_
Error message
The CUBEJS_DB_CATALOG is deprecated. Please, use the CUBEJS_DB_PRESTO_CATALOG instead.
What it means
A deprecation warning printed while resolving the Presto catalog: the environment still sets CUBEJS_DB_CATALOG, whose role is now served by the data-source-scoped CUBEJS_DB_PRESTO_CATALOG. The old variable is still honored for backward compatibility, so this is only a migration notice, not a failure.
Source
Thrown at packages/cubejs-backend-shared/src/env.ts:1674
} must be either 'true' or 'false'.`
);
}
} else {
return false;
}
},
/** ****************************************************************
* Presto Driver *
***************************************************************** */
/**
* Presto catalog.
*/
dbCatalog: ({
dataSource,
preAggregations,
}: DataSourceOpts) => {
console.warn(
'The CUBEJS_DB_CATALOG is deprecated. ' +
'Please, use the CUBEJS_DB_PRESTO_CATALOG instead.'
);
return get(keyByDataSource('CUBEJS_DB_CATALOG', dataSource, preAggregations)).asString();
},
/** ****************************************************************
* duckdb *
***************************************************************** */
duckdbMotherDuckToken: ({
dataSource,
preAggregations,
}: DataSourceOpts) => (
get(keyByDataSource('CUBEJS_DB_DUCKDB_MOTHERDUCK_TOKEN', dataSource, preAggregations)).asString()
),
duckdbDatabasePath: ({View on GitHub (pinned to 7d981676b3)
Solutions
- Replace CUBEJS_DB_CATALOG with CUBEJS_DB_PRESTO_CATALOG (suffixed variants likewise)
- Remove the deprecated variable after verifying the new one applies
- Restart Cube and confirm the catalog resolves correctly in queries
Example fix
// before CUBEJS_DB_CATALOG=hive // after CUBEJS_DB_PRESTO_CATALOG=hive
Defensive patterns
Strategy: validation
Validate before calling
if (process.env.CUBEJS_DB_CATALOG) console.warn('Use CUBEJS_DB_PRESTO_CATALOG instead of deprecated CUBEJS_DB_CATALOG'); Prevention
- Use driver-prefixed env vars (CUBEJS_DB_PRESTO_CATALOG) for Presto/Trino
- Check per-datasource suffixed variants too
- Validate catalog names resolve in Presto after migration
When it happens
Trigger: dbCatalog env accessor is invoked (when configuring a Presto/Trino datasource, including suffixed per-datasource variants) and CUBEJS_DB_CATALOG is defined.
Common situations: Old Presto driver configurations; multi-datasource setups with CUBEJS_DB_CATALOG_<DS>; docs from before the Presto-specific rename.
Related errors
- The ${keyByDataSource('CUBEJS_DB_SCHEMA', dataSource)} is de
- The ${keyByDataSource('CUBEJS_DATABASE', dataSource)} is dep
- CreateOptions.dbType was removed in v1.7.0. Use driverFactor
- Unable to resolve file "${value}" from ${key}
- Worker thread transpilation is enabled by default and cannot
AI-assisted analysis of cube-js/cube@7d981676b3 (2026-09-02).
Data as JSON: /api/errors/64a6839d693ef39a.
Report an issue: GitHub.