Rework the PathFromGraph paging API
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
The nested page(...) field on GqlPathFromGraph is of limited use because columnar outputs on the same handle (e.g. degree) cannot be paged alongside it: the page narrows the row set but the columnar fields still cover the whole collection. Revisit the shape; one option is for page to return a restricted GqlPathFromGraph so every field on the returned handle is consistently scoped to the page.
Raised in review: https://github.com/Pometry/Raphtory/pull/2675#discussion_r3812010215
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 at the GqlPathFromGraph API, especially the nested page(...) field and columnar fields such as degree, then read the discussion on PR #2675. Done means the paging shape is revised so fields on a paged handle consistently refer to the restricted row set, with the chosen API behavior made clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100