Pometry / Pometry/Raphtory

Can we support ranking via the old search nodes/edges apis

Open
#2,258 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

filter_expr = filter.Node.property("p1").contains("pometry")

graph.search_nodes(filter_expr) returns nodes that match filter_expr
which order should be returned based on some ranking.

Ranking

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 reviewing the old graph.search_nodes(filter_expr) API and the related nodes/edges search behavior. The issue points to TF-IDF-style ranking but does not define the ranking contract, ordering, or acceptance criteria. Done would require an agreed ranking design and matching behavior for the affected search APIs.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.