TimelyDataflow / TimelyDataflow/differential-dataflow
Holding on to a trace with physical/logical compaction to the empty frontier stalls compaction
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 211
- Avg merge
- 10h 42m
- Merged PRs (30d)
- 34
Description
(Placeholder, @antiguru to add more info+repro)
While working on https://github.com/MaterializeInc/materialize/pull/18766, we noticed that allowing physical and logical compaction of a trace to the empty frontier prevents compaction, even if other owners of the trace eventually allow compaction. It is required to repeatedly allow compaction with a sensible frontier (i.e., read_upper followed by allowing compaction) to enable compaction of the spine.
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
The issue is a placeholder and names no source file, test, or reproduction; begin by reading the context from PR 18766 and tracing physical and logical compaction of a trace. Done means compaction proceeds after other owners allow a sensible frontier, with a regression test covering the empty-frontier case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100