StorageConfigInfo should be optional for EXTERNAL catalogs
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 140
Description
### Describe the bug
Currently, StorageConfigInfo is required for both INTERNAL and EXTERNAL catalogs.
However for federated catalogs, Polaris does not need this information since it can access it from the source of truth catalog. To fix this issue we need to change the API spec as well as Polaris Server validations during CreateCatalog requests.
Once that is done, we no longer need to set the `ALLOW_OVERLAPPING_CATALOG_URLS` in the regression/integration tests for catalog federation.
### To Reproduce
_No response_
### Actual Behavior
_No response_
### Expected Behavior
_No response_
### Additional context
_No response_
### System information
_No response_
Contributor guide
Research direction
Start by locating the API specification and Polaris Server's CreateCatalog validation for StorageConfigInfo, then inspect the regression and integration tests for catalog federation. Done means StorageConfigInfo is optional for EXTERNAL catalogs while remaining required for INTERNAL catalogs, and the federation tests no longer need ALLOW_OVERLAPPING_CATALOG_URLS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100