Kev
08/11/2026, 12:43 AMRocky
08/11/2026, 12:43 AM9030), not the standard MySQL port (3306).
* Host: Use the IP or hostname of your StarRocks Frontend (FE).
Known Considerations for BI Layers
While the protocol is compatible, keep these tips in mind when using generic MySQL connectors:
1. Metadata Discovery: Some BI tools may attempt to query MySQL-specific system tables (like information_schema). StarRocks supports a large portion of these, but if you encounter issues with "table not found" or "column not found" during the initial setup, it’s often due to the tool expecting specific MySQL metadata that StarRocks handles slightly differently.
2. SSL/TLS: If your StarRocks cluster requires SSL, ensure the BI tool's MySQL connector is configured to trust the StarRocks FE certificate.
3. Functions and Syntax: StarRocks supports standard SQL, but if a BI tool generates highly specific MySQL-only syntax (like certain administrative commands), you may need to use "Pass-through" or "Custom SQL" modes in the BI tool to leverage StarRocks-specific optimizations like BITMAP or HLL functions.
Other BI Tools Using MySQL/JDBC
* Tableau: While StarRocks has a dedicated Tableau JDBC Connector, many users also successfully use the generic MySQL JDBC driver.
* Superset: Uses the mysqlclient or PyMySQL drivers to connect to StarRocks.
* DBeaver: Uses the standard MySQL driver or the dedicated StarRocks driver (available in newer versions).
If you run into specific errors while connecting Sigma, it is usually helpful to check the FE audit logs (fe/log/fe.audit.log) to see the exact SQL Sigma is sending during the connection phase.
References
• integrations/BI_integrations/Rill.md
• loading/loading_tools.md
• integrations/BI_integrations/FineBI.md
• integrations/BI_integrations/Tableau_Desktop.md
• integrations/BI_integrations/QuickBI.md
• quick_start/shared-nothing.md