You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`type`| Engine type name - must be `trino`| string | Y |
87
-
|`user`| The username (of the account) to log in to your cluster. When connecting to Starburst Galaxy clusters, you must include the role of the user as a suffix to the username. | string | Y |
88
-
|`host`| The hostname of your cluster. Don't include the `http://` or `https://` prefix. | string | Y |
89
-
|`catalog`| The name of a catalog in your cluster. | string | Y |
90
-
|`http_scheme`| The HTTP scheme to use when connecting to your cluster. By default, it's `https` and can only be `http` for no-auth or basic auth. | string | N |
91
-
|`port`| The port to connect to your cluster. By default, it's `443` for `https` scheme and `80` for `http`| int | N |
92
-
|`roles`| Mapping of catalog name to a role | dict | N |
93
-
|`http_headers`| Additional HTTP headers to send with each request. | dict | N |
94
-
|`session_properties`| Trino session properties. Run `SHOW SESSION` to see all options. | dict | N |
95
-
|`retries`| Number of retries to attempt when a request fails. Default: `3`| int | N |
96
-
|`timezone`| Timezone to use for the connection. Default: client-side local timezone | string | N |
|`type`| Engine type name - must be `trino`| string | Y |
87
+
|`user`| The username (of the account) to log in to your cluster. When connecting to Starburst Galaxy clusters, you must include the role of the user as a suffix to the username. | string | Y |
88
+
|`host`| The hostname of your cluster. Don't include the `http://` or `https://` prefix. | string | Y |
89
+
|`catalog`| The name of a catalog in your cluster. | string | Y |
90
+
|`http_scheme`| The HTTP scheme to use when connecting to your cluster. By default, it's `https` and can only be `http` for no-auth or basic auth. | string | N |
91
+
|`port`| The port to connect to your cluster. By default, it's `443` for `https` scheme and `80` for `http`| int | N |
92
+
|`roles`| Mapping of catalog name to a role | dict | N |
93
+
|`http_headers`| Additional HTTP headers to send with each request. | dict | N |
94
+
|`session_properties`| Trino session properties. Run `SHOW SESSION` to see all options. | dict | N |
95
+
|`retries`| Number of retries to attempt when a request fails. Default: `3`| int | N |
96
+
|`timezone`| Timezone to use for the connection. Default: client-side local timezone | string | N |
97
+
|`schema_location_mapping`| A mapping of regex patterns to S3 locations to use for the `LOCATION` property when creating schemas. See [Table and Schema locations](#table-and-schema-locations) for more details. | dict | N |
98
+
|`catalog_type_overrides`| A mapping of catalog names to their connector type. This is used to enable/disable connector specific behavior. See [Catalog Type Overrides](#catalog-type-overrides) for more details. | dict | N |
97
99
98
100
## Table and Schema locations
99
101
@@ -204,6 +206,25 @@ SELECT ...
204
206
205
207
This will cause SQLMesh to set the specified `LOCATION` when issuing a `CREATE TABLE` statement.
206
208
209
+
## Catalog Type Overrides
210
+
211
+
SQLMesh attempts to determine the connector type of a catalog by querying the `system.metadata.catalogs` table and checking the `connector_name` column.
212
+
It checks if the connector name is `hive` for Hive connector behavior or contains `iceberg` or `delta_lake` for Iceberg or Delta Lake connector behavior respectively.
213
+
However, the connector name may not always be a reliable way to determine the connector type, for example when using a custom connector or a fork of an existing connector.
214
+
To handle such cases, you can use the `catalog_type_overrides` connection property to explicitly specify the connector type for specific catalogs.
215
+
For example, to specify that the `datalake` catalog is using the Iceberg connector and the `analytics` catalog is using the Hive connector, you can configure the connection as follows:
0 commit comments