Published segments cache in Brokers shouldn't use Interners
Open
Area - Metadata
Area - SQL
Evergreen
Performance
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 58m
- Merged PRs (30d)
- 233
Description
Regarding #6901 (proposal: #6834)
Published segments cache in Brokers shouldn't use Interners. Instead, `MetadataSegmentView` should probe into `BrokerServerView`'s data and vice versa, similar to was is done in Coordinator's memory: #6357.
FYI @surekhasaharan
Contributor guide
Research direction
Read #6901, proposal #6834, and the Coordinator memory precedent in #6357 first. Then inspect MetadataSegmentView and BrokerServerView to understand how their data can be probed in both directions. Done means the published segments cache no longer uses Interners and follows the referenced Coordinator approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100