-
Notifications
You must be signed in to change notification settings - Fork 332
Introduce an option to add object storage prefix to table locations #1966
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
Changes from all commits
1289636
afbc949
8be48de
6004d88
268963f
6b50023
9d1a0f6
cf10e8c
f88a122
d7e2f7c
f6572d5
e2aa85f
eaf82cb
408603e
3338d5b
eaf6178
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -339,4 +339,17 @@ public static void enforceFeatureEnabledOrThrow( | |
| + "to enforce this when new locations are added. Only supported by the JDBC metastore.") | ||
| .defaultValue(false) | ||
| .buildFeatureConfiguration(); | ||
|
|
||
| public static final FeatureConfiguration<Boolean> DEFAULT_LOCATION_OBJECT_STORAGE_PREFIX_ENABLED = | ||
| PolarisConfiguration.<Boolean>builder() | ||
| .key("DEFAULT_LOCATION_OBJECT_STORAGE_PREFIX_ENABLED") | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is it "DEFAULT"? It was not default in Polaris 🤔
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In Iceberg code this method of computing table locations is apparently called an "object store" location provider 🤔
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yes, it is only for the object store as they are flat and use those hashes for different compute on the backend to handle based on prefix (not a problem nor needed is backend is block storage)
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, yeah, the naming is really tough here. It's The Iceberg feature doesn't have this component because it applies within the user-specified table location, whereas the Polaris feature applies above the table location only if there isn't a user-specified location.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How about
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. But it's not always applied like the Iceberg option, it's only applied when using the "default location" for a table
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ok |
||
| .catalogConfig("polaris.config.default-table-location-object-storage-prefix.enabled") | ||
| .description( | ||
| "When enabled, Iceberg tables and views created without a location specified will have a prefix " | ||
| + "applied to the location within the catalog's base location, rather than a location directly " | ||
| + "inside the parent namespace. Note that this requires ALLOW_EXTERNAL_TABLE_LOCATION to be " | ||
| + "enabled, but with OPTIMIZED_SIBLING_CHECK enabled " | ||
| + "it is still possible to enforce the uniqueness of table locations within a catalog.") | ||
| .defaultValue(false) | ||
| .buildFeatureConfiguration(); | ||
| } | ||
Uh oh!
There was an error while loading. Please reload this page.