graphprotocol / graphprotocol/graph-node
[Feature] Allow for both pruned and unpruned versions to be live simultaneously
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Description
As the title suggests, allow for both pruned and unpruned versions to be live simultaneously.
This means I have Subgraph X which will be living in two different forms - pruned and unpruned.
The most important thing needs to be that both should be accessible based on query needs, simultaneously.
If the block/data range queried falls inside the pruned version range, send queries to it.
If not, send the historical queries to the unpruned version.
This has to be done with zero input from the infrastructure operator.
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out
- Tick this box if you plan on implementing this feature yourself.
- I have searched the issue tracker to make sure this issue is not a duplicate.
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
No files or tests are named. Start by tracing the existing query-routing and subgraph version-selection entry points, then determine how block ranges can select between pruned and unpruned versions. Done means both versions remain accessible simultaneously, with routing based on the queried range and no infrastructure-operator input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100