weaviate / weaviate/weaviate-agents-python-client
Allow search-only pagination state to be extracted / persisted / reinitialised
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
The current design for pagination involves keeping the response instance alive, since it's holding hidden state that keeps searches consistent between pages. We should add methods to extract this state (allowing it to be persisted in a DB etc between requests), and to reinitialise/rerun the searches using this state.
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
The issue names no files or tests. Start by tracing how the pagination response instance holds hidden search state and how searches advance between pages. Done means callers can extract that state for persistence and reinitialise or rerun the searches from the persisted state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100