Pometry / Pometry/Raphtory

Bi-temporal querying

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

There are several use cases where it is incredibly useful to query by event time vs processing time - i.e. when an event occured and when we heard about it. We can already store this information but we need some APIs to help the exploration of it.

It may make sense for this to be part of the new History object #1759

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 reading the existing implementation that stores event time and processing time, then review the proposed History object in issue #1759. The issue does not name files, tests, or a settled API; the work is done only once the temporal querying APIs and their expected behavior are defined and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
databases
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.