Yosua Simanjuntak
04/21/2026, 2:58 AMRocky
04/21/2026, 2:58 AM.env file or Cube Cloud UI):
1. CUBEJS_DB_TYPE: mysql
2. CUBEJS_DB_HOST: Your StarRocks FE (Frontend) host address.
3. CUBEJS_DB_PORT: 9030 (the default MySQL query port for StarRocks).
4. CUBEJS_DB_NAME: The name of your StarRocks database.
5. CUBEJS_DB_USER: Your StarRocks username (e.g., root).
6. CUBEJS_DB_PASS: Your StarRocks password.
Key Integration Tips:
* MySQL Protocol Compatibility: Since Cube treats StarRocks as a MySQL source, most standard SQL features will work out of the box.
* Schema Design: StarRocks does not use the "schema" concept in the same way some other warehouses do. You typically just specify the database name in the connection string.
* Performance: To take full advantage of StarRocks' speed within Cube, ensure your Cube "pre-aggregations" are configured to leverage StarRocks' materialized views or internal tables for high-concurrency scenarios.
* Permissions: If you encounter Access Denied errors with non-root users (especially if using external plugins like Apache Ranger), ensure the user has the correct SELECT permissions on the information_schema as well as your target database.
While there isn't a "native" StarRocks-specific driver listed in the main Cube documentation, the MySQL driver is the officially recommended and community-tested way to connect the two.
References
• integrations/integrations.mdx
• integrations/loading_tools/loading_tools_integration.mdx
• integrations/BI_integrations/Querybook.md
• integrations/streaming/pipe.mdx
• cover_pages/bi_tools.mdx
• integrations/batch/Spark-connector-starrocks.mdx
• integrations/batch/SparkLoad.mdx
• integrations/BI_integrations/Hex.md