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
warehouse: gs://<bucket-name> # Use bq://projects/<gcp-project-id> for federation option (see docs)
562
+
auth:
563
+
type: google
564
+
header.x-goog-user-project: <gcp-project-id>
565
+
header.X-Iceberg-Access-Delegation: "" # For user-credentials authentication, set to empty string.
566
+
```
567
+
568
+
<!-- prettier-ignore-start -->
569
+
570
+
!!! Note "Metastore Authentication Models"
571
+
If your BigLake Metastore catalog is configured for "user credentials" authentication instead of "vendor credentials", set the `header.X-Iceberg-Access-Delegation` header to an empty string as shown above. Standard GCP Application Default Credentials (ADC) will be used to authenticate requests to the BigLake Metastore REST API.
572
+
You can retrieve the configuration details for your BigLake Iceberg catalog at the [GCP Console BigLake Metastore page](https://console.cloud.google.com/biglake/metastore/catalogs). Select your catalog, then find the necessary parameters such as `uri`, `warehouse`, and authentication method (e.g. user-creds or vendor).
573
+
574
+
<!-- prettier-ignore-end -->
575
+
554
576
### SQL Catalog
555
577
556
578
The SQL catalog requires a database for its backend. PyIceberg supports PostgreSQL and SQLite through psycopg2. The database connection has to be configured using the `uri` property. The init_catalog_tables is optional and defaults to True. If it is set to False, the catalog tables will not be created when the SQLCatalog is initialized. See SQLAlchemy's [documentation for URL format](https://docs.sqlalchemy.org/en/20/core/engines.html#backend-specific-urls):
0 commit comments