Skip to content

feat(graph): add TerminusDB backend with incremental updates and versioning - #35

Open
jjk9090 wants to merge 1 commit into
OpenDCAI:codex/optional-data-accessfrom
jjk9090:feat/terminusdb-graph-versioning
Open

jjk9090 wants to merge 1 commit into
OpenDCAI:codex/optional-data-accessfrom
jjk9090:feat/terminusdb-graph-versioning

Conversation

@jjk9090

@jjk9090 jjk9090 commented Oct 25, 2026

Copy link
Copy Markdown

Summary

This PR introduces TerminusDB as a graph storage backend for DataMind, with support for incremental updates and version-aware graph operations.

This work is stacked on top of #34, which provides the versioned workspace evidence foundation.

Key Changes

  • TerminusDB backend: Add a TerminusDB-backed implementation of the graph storage interface.
  • Incremental updates: Support incremental graph updates to avoid unnecessary full graph rebuilds.
  • Version management: Add graph versioning and rollback support. Specifically:
    • Implemented new graph query APIs: search_entities_at_version, traverse_at_version, neighbors_at_version, and list_versions.
    • Added rollback support to restore the graph to a specific version.
  • Integration: Update the graph and ingest layers to support version-aware operations.
    • Added graph_delete_path to the ingest layer to support path deletion during ingestion.
  • Testing: Add integration tests for graph versioning and rollback in test_graph_versioning.py.

…ioning

- Add TerminusDB as a graph storage backend
- Implement incremental graph updates and version control
- Update graph and ingest layers to support version-aware operations
- Add integration tests for graph versioning and rollback in `test_graph_versioning.py`
- Ensure all tests pass

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant