RFC: Rename OptimizerConfig to OptimizerProps
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
### Is your feature request related to a problem or challenge?
Following up PR #6706, I think the name `OptimizerConfig` no longer make sense because it contains per-query execution state such as query execution start time and alias generator.
### Describe the solution you'd like
I think `OptimizerConfig` trait should be renamed to `OptimizerContext` and the existing `OptimizerContext` which is a concrete class should be renamed to `OptimizerState`.
### Describe alternatives you've considered
Leave it as it is
### Additional context
cc @alamb @jackwener
Contributor guide
Research direction
Start by reviewing PR #6706 and locating the definitions and references for OptimizerConfig and OptimizerContext. The issue's title and requested renames disagree, so confirm the intended naming before changing references; done means the agreed names are applied consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100