StarRocks
StarRocks is its own database type in QueryDesk. It speaks the MySQL protocol, so the schema sync, data protection and peer reviews work as they do on MySQL, with StarRocks' catalogs and SQL.
Connect a cluster
Add the database as in Connect a database, with these values:
| Field | Value |
|---|---|
| Database type | StarRocks |
| Database IP or hostname | A frontend (FE) node, or the load balancer in front of them. |
| Port | 9030, the FE's MySQL port. |
| Database name | The database to query, or catalog.database for an external catalog such as Hive or Iceberg, for example hive_catalog.sales. A bare name is in default_catalog. |
A mysql:// or starrocks:// connection string pasted under Update with connection string keeps the StarRocks type.
Click Test Connection under the credential to check the connection.
What works differently
- One catalog per database. The schema sync reads the catalog the database name gives, and data protection refuses a statement that switches catalog (
SET CATALOG) or reads another catalog's tables. Add a database in QueryDesk for each catalog you query. - AI read-only rests on QueryDesk's parser alone: StarRocks accepts
SET TRANSACTION READ ONLYbut doesn't enforce it. The parser refusesFILES(), which reads and writes object storage. Give the AI's credentials onlySELECT. - SHOW is refused under a policy:
SHOW PROCandSHOW RUNNING QUERIEScan print other sessions' SQL. - Timeouts use StarRocks'
query_timeout, in whole seconds, so a cap under a second rounds up.