Stream/TopN result info needs to be passed to FTS backend
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
as this is one piece missing in the basic hello world milestone.
Meantime, are we going to use Pagable in deciding when to use streaming or when to use topN (non stream) in search request.?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how search requests and results reach the FTS backend, then determine how streaming, TopN, and Pageable are intended to interact; done means the required result information reaches the backend and the selection behavior is documented or testable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100