poojanilangekar commented on code in PR #1959:
URL: https://github.com/apache/polaris/pull/1959#discussion_r2176088079
##########
polaris-core/src/main/java/org/apache/polaris/core/config/FeatureConfiguration.java:
##########
@@ -263,12 +264,14 @@ public static void enforceFeatureEnabledOrThrow(
.defaultValue(true)
.buildFeatureConfiguration();
- public static final FeatureConfiguration<List<String>>
SUPPORTED_CATALOG_CONNECTION_TYPES =
- PolarisConfiguration.<List<String>>builder()
- .key("SUPPORTED_CATALOG_CONNECTION_TYPES")
- .description("The list of supported catalog connection types for
federation")
- .defaultValue(List.of(ConnectionType.ICEBERG_REST.name()))
- .buildFeatureConfiguration();
+ public static final FeatureConfiguration<List<String>>
+ SUPPORTED_EXTERNAL_CATALOG_CONNECTION_TYPES =
+ PolarisConfiguration.<List<String>>builder()
+ .key("SUPPORTED_EXTERNAL_CATALOG_CONNECTION_TYPES")
+ .deprecatedKey("SUPPORTED_CATALOG_CONNECTION_TYPES")
Review Comment:
I can make the changes. Just so we are on the same page, does the following
approach make sense to both of you?:
1. Support a single `key` per config, because ideally at any given time, we
want at most one active key per configuration.
2. Support multiple `legacyKeys` per config. So we can make multiple calls
to `legacyKey()` while building a config.
--
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: issues-unsubscr...@polaris.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
