TimelyDataflow / TimelyDataflow/differential-dataflow

Collections with primary key can support more efficient cursors

Open
#212 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3k
Forks
211
Avg merge
10h 42m
Merged PRs (30d)
34

Description

From @quodlibetor: When collections have primary keys, we should be able to perform key-wise actions through a cursor by traversing new-to-old batches and looking for the first positive accumulation. Once identified, this should be the only record, under the hypothesis that each prior collection accumulated to something non-negative. This seems like an eminently plausible case, and the optimization of avoiding seeks into the large batches is appealing.

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

The issue names no file, test, or entry point. Start by locating the collection cursor implementation and existing key-wise actions, then determine how cursor traversal handles accumulated batches. Done means the proposed primary-key case is covered by tests and avoids unnecessary seeks without changing results.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
data-engineering, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.