-
Notifications
You must be signed in to change notification settings - Fork 27
fix: use the cloud catalog when doing save_as_table in a cloud session #91
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
base: main
Are you sure you want to change the base?
fix: use the cloud catalog when doing save_as_table in a cloud session #91
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
5906010 to
c2218e9
Compare
9d19ab6 to
eac9275
Compare
c2218e9 to
513da9a
Compare
eac9275 to
796a233
Compare
796a233 to
8397d8c
Compare
bcallender
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.
looks fine, just a few minor nits
8397d8c to
293ea49
Compare
rohitrastogi
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.
needs one more round of reviews
7646651 to
ec78306
Compare
f040c35 to
b80ea4c
Compare
b80ea4c to
fdbfa46
Compare
b2b040a to
6b9a23e
Compare
|
My bad, this was out for a while. I've addressed all the comments. |
6b9a23e to
f451b4f
Compare
4260ef1 to
222310d
Compare
| catalog_name: str | ||
| catalog_id: UUID | ||
|
|
||
| CLOUD_SUPPORTED_SCHEMES = ["s3"] |
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.
we'll have to adjust this in #157
| return schema_type | ||
|
|
||
| @staticmethod | ||
| def _get_table_location_from_table_identifier(table_identifier: TableIdentifier) -> str: |
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.
wouldn't the location be based on the base location in the catalog? if the user provides a bucket or prefix as the catalog's base location, all of the paths for dbs and tables should be relative to that base location, i would think.
| f"2) Use a different table name.") | ||
| elif table_exists and query_metrics: | ||
| # trunk-ignore-begin(bandit/B101) | ||
| assert mode == "ignore", "only mode to fulfill this invariant is ignore." |
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.
particular reason to choose assert here and not raise an exception?

TL;DR
Added support for specifying a location when saving DataFrames as tables using a cloud session.
What changed?