MonkeyCanCode commented on code in PR #1966:
URL: https://github.com/apache/polaris/pull/1966#discussion_r2191020311
##########
polaris-core/src/main/java/org/apache/polaris/core/config/FeatureConfiguration.java:
##########
@@ -327,4 +327,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")
Review Comment:
> In Iceberg code this method of computing table locations is apparently
called an "object store" location provider :thinking:
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)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
