deepset-ai / deepset-ai/haystack-core-integrations
Refactor AstraDocumentStore to use `astrapy` natively
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 203
- Forks
- 332
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 80
Description
Currently AstraDocumentStore uses AstraClient, a custom interface over astrapy.
The current implementation is based on astrapy<2 and does not support native async (uses threads instead), which is supported natively by astrapy.
This also makes it hard to properly release resources. Note that astrapy>2 only allows releasing async resources, not sync ones.
We should investigate if it's worth dropping AstraClient and using astrapy (>=2.0) natively.
We could use Document Store tests as a safeguard.
We only accept contributions to this refactoring from actual Astra users, interested in making this integration better and of course having an account to test things out.
Contributor guide
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
Start by locating AstraDocumentStore and its AstraClient dependency, then review the existing Document Store tests as the stated safeguard. Investigate whether astrapy >=2 can replace the custom interface while preserving behavior and enabling native async resource handling. Done means the integration uses the chosen approach, resources are released correctly, and the Document Store tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100