Remove catalogConfigUnsafe() and drop related old config property names in Polaris 2.0
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 527
- Avg merge
- 2d 16m
- Merged PRs (30d)
- 139
Description
### Is your feature request related to a problem? Please describe.
Following up on #1970 and #1894.
### Describe the solution you'd like
Existing calls to `catalogConfigUnsafe()` should be removed.
Support for related old catalog property names should be dropped to simplify project maintenance.
Users are expected to migrate to new and supported property names by 2.0
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Review issues #1970 and #1894 first, then search the repository for catalogConfigUnsafe() and the related old catalog property names. Done means existing calls and compatibility support for those old names are removed for Polaris 2.0, while the new supported property names remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100