-
Notifications
You must be signed in to change notification settings - Fork 411
docs: add GCP BigLake Metastore Catalog configuration example #2740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add GCP BigLake Metastore Catalog configuration example #2740
Conversation
raulcd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can the warehouse be of type bq://projects/PROJECT_ID? As shown here:
https://docs.cloud.google.com/biglake/docs/blms-rest-catalog#configure-catalog
If applicable, should we add a note?
rambleraptor
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks awesome! Thanks for doing this.
Add note about warehouse uri format for the federation option (bq:// ).
Added a comment about the bq:// alternative |
Add extend bq uri example
raulcd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
|
Is there a process for requesting review by someone with write permissions? |
kevinjqliu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
"BigLake Metastore Catalog Iceberg REST" is a mouthful 😅 |
|
Thanks for the PR @heathkh-recursion and thanks for the review @rambleraptor @raulcd |

Rationale for this change
GCP had the GA release of the BigLake Metastore Catalog Iceberg REST api Nov 30 (see release notes). There are few GCP docs available how to set this up in general, and with pyiceberg specifically. Ray Data and probably many other tools use pyiceberg under the hood, so documenting this would make it much easier for folks in the GCP cloud to use pyiceberg at scale.
Are these changes tested?
Yes, using the following test plan:
Are there any user-facing changes?
Would add a new section in the docs when docs are published.