Sriram
11/04/2025, 3:58 PMcurl command.
Has anyone successfully integrated StarRocks 3.5.x with Databricks Unity Catalog? Are there any specific configuration properties I might be missing for Unity Catalog within the StarRocks DDL? Please help.
I am running StarRocks version 3.5.7-d2da301 deployed on Kubernetes/AKS.
Configuration Used:
CREATE EXTERNAL CATALOG 'databricks_uc_catalog_new'
PROPERTIES (
"type" = "iceberg",
"iceberg.catalog.type" = "rest",
"iceberg.catalog.uri" = "https://<my-workspace-url>/api/2.1/unity-catalog/iceberg-rest",
"iceberg.auth.type" = "bearer",
"iceberg.auth.bearer.token" = "dapi<MY_VALID_PAT>"
);mysql> show catalogs; +-----------------------+----------+------------------------------------------------------------------+ | Catalog | Type | Comment | +-----------------------+----------+------------------------------------------------------------------+ | databricks_uc_catalog | Iceberg | Unity Catalog via Iceberg REST API (Fixed Auth) | | default_catalog | Internal | An internal catalog contains this cluster's self-managed tables. | +-----------------------+----------+------------------------------------------------------------------+ 2 rows in set (0.062 sec) mysql> show databases from databricks_uc_catalog -> ; ERROR 1064 (HY000): Failed to load rest catalog mysql> Detailed Error from FE Log (Master Node): The logs indicate that the Databricks service is receiving the request but rejects the credentials, and the StarRocks client is having trouble parsing the specific error response JSON structure. 2025-11-04 235446.450+08:00 ERROR (starrocks-mysql-nio-pool-6|336) [IcebergRESTCatalog.<init>():104] Failed to rest load catalog _org.apache.iceberg.exceptions.NotAuthorizedException: Not authorized: {"error_code":401,"message":"Credential was not sent or was of an unsupported type for this API. [ReqId: fde0ad1f-822c-9f48-86fc-dbd917cfec77]"}_