Internalise update_node/update_edge
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
Currently on a vectorised graph we need to call update_node and update_edge to create new documents (after new information has been added into the graph via add_node add_edge). This is done automatically on the server, but is manual in python.
This should happen automatically if the user has vectoried a graph once we have pushed the vectors into the storage along with the index.
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 comparing the Python vectorised-graph flow using add_node/add_edge with the server behavior that already updates documents automatically. Trace where vectors and the index are pushed into storage, then verify that update_node and update_edge are triggered automatically after vectorisation without manual calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100