add top-k to MatchMerger
Open
priority/important-longterm
type/maintenance
- Dominant language
- Python
- Stars
- 31
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the MatchMerger collects the matches from the shards and appends all of them to a single output.
This might be confusing to the user since they get `top-k * num_shards` results.
Please implement the top-k into the match merger
Contributor guide
Research direction
Locate the MatchMerger implementation and inspect how it aggregates matches from shards. Implement the requested top-k behavior so the final output is limited to top-k results rather than top-k multiplied by the number of shards, then run the relevant existing tests if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100