Hi all, I encountered an issue in the Polaris console while setting up an external catalog and have filed a GitHub issue and an associated PR.
Currently, the create-catalog form offers all three EXTERNAL connection types but fails to collect the type-specific fields: `remoteCatalogName` for ICEBERG_REST, and `warehouse` for HADOOP and HIVE. Because ConnectionConfigInfo in the console's types only mirrors the base schema, these subtype fields have no representation. While the server accepts the resulting catalog, it cannot resolve against a prefix-scoped remote. Additionally, there is no repair path since UpdateCatalogRequest does not accept connectionConfigInfo. Here are the links to the issue and PR: - Issue: https://github.com/apache/polaris-tools/issues/266 - PR: https://github.com/apache/polaris-tools/pull/267 The PR flattens both fields onto ConnectionConfigInfo, matching how StorageConfigInfo handles the S3/Azure/GCS discriminator. While properly modeling the subtypes would be more faithful to the specification, it diverges from the existing pattern, so I opted for local consistency. I am happy to rework this if the project prefers to change the current pattern. I have verified this end-to-end against Polaris 1.5.0 with a prefix-scoped remote. p.s. also, would it be possible for me to join the slack channel without @ apache.org email domain? I tried to join the slack channel, but I couldn't. Thanks for your time in advance! Yong-Jin Lee Senior Data Engineer 1-703-999-9402
