Future filter improvments
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
- Refer: https://github.com/Pometry/Raphtory/pull/1991#discussion_r2055846482, https://github.com/Pometry/Raphtory/pull/1991#discussion_r2055852860, https://github.com/Pometry/Raphtory/pull/1991#discussion_r2055870114
- Can we add node_list as a filter -- (subgraph called on anything other than the graph) -- node name filter should return a subgraph because it will be a lot faster than the current implementation
- Do we need the non-tokenized? Refer: https://github.com/Pometry/Raphtory/pull/1991#discussion_r2058174196
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 with the three referenced discussions on pull request 1991, then trace the existing filter and subgraph entry points. The scope includes adding a node_list filter for subgraphs and deciding whether non-tokenized filtering is needed; done requires resolving both questions and covering the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100