apache / apache/geaflow

[geaflow/ai-memory] Add document replay and deduplication fixtures

Open
#835 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
808
Forks
188
Avg merge
3d 22h
Merged PRs (30d)
2

Description

Priority: P1
Difficulty: Starter

Context: Graph Memory needs replayable ingestion. If the same document is imported twice, downstream graph facts and indexes should not duplicate silently.

Scope:

- Add fixtures for duplicate documents, updated documents, deleted documents, and reordered files.
- Define expected replay behavior for `source_id + content_hash`.
- Add tests that only verify replay metadata, not full extraction.

Constraints:

- No graph backend implementation in this issue.
- No deletion propagation implementation yet; only define fixture and expected state.

Acceptance Criteria:

- Fixture clearly distinguishes duplicate, update, and delete events.
- Replay metadata can be used by later Event Log and projector issues.

Suggested paths:

- `geaflow-ai/src/test/resources/document-replay`
- `docs/graphmemory-design-doc.md` or a new `docs/geaflow-ai-graph-memory-contracts.md`

Contributor guide

Open the contributing guide

Research direction

Start with the existing tests and resources under geaflow-ai/src/test, then inspect geaflow-ai/src/test/resources/document-replay and docs/graphmemory-design-doc.md. Add fixtures for duplicate, updated, deleted, and reordered documents, define expected source_id + content_hash replay metadata, and verify metadata without full extraction; done means later Event Log and projector work can consume the fixtures.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
data-engineering, documentation, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
73/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.