Pometry / Pometry/Raphtory

Fix Cached graph load and update

Open
#2,146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
642
Forks
70
Avg merge
2d 13h
Merged PRs (30d)
21

Description

// CachedGraphIndex: Should solve both (A) and (B)
// ren the immutable index dir to index_dirty
// any update goes directly to index_dirty
// write_update -> ren index_dirty to index 

// Continued
// cached a graph, encode the mutable index i.e, just copy-paste
// change the graph + index, this updated the mutable index
// write update -> this should not delete the existing graph; currently nukes existing index and copies over the temp one (A)

// Discontinued
// cached a graph, encode the mutable index i.e, just copy-paste
// decode the graph, index is loaded as immutable index 
// change the graph + index, this will copy the immutable index to mutable ver (B) and then updated the mutable index

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating CachedGraphIndex and its graph load, mutable-index update, and write_update paths. Reproduce the cached-graph update cases described as (A) and (B), then verify that updates use index_dirty safely and do not delete the existing graph or index before the replacement is ready.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
databases
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.