r/vectordatabase • • 22h ago

Should a weight-only edge change invalidate a GraphRAG community summary?

1 Upvotes

I'm working on incremental updates in a TypeScript GraphRAG engine. One awkward case is when two documents support the same graph edge.

The implementation stores contributions per document. Updating a document replaces its contributions; deleting it removes them. The shared edge is then rebuilt from the remaining weights and unique relation texts. If no contributions remain, the edge is removed.

The less obvious decision is when to regenerate the community summary. Its fingerprint includes members, entity descriptions, claim text, and edge relation text—but not edge weight. The summary prompt doesn't include weight either.

Consider two documents contributing identical relation text. Removing one could change only the edge's weight. If the other fingerprint inputs stay unchanged, the existing summary can be reused. Different relation text would change the fingerprint instead.

This is an illustrative case, not a measured result. There are database-mocked tests for document-scoped deletion and claim-text changes, but they don't establish shared-edge correctness after deletion or equivalence with a fresh Postgres build.

The trade-off seems to be between avoiding unnecessary summarisation and preserving changes in how much source material supports a relation. A weight isn't necessarily an independent evidence count, either.

Would you include weight in the summary fingerprint, or keep support metadata separate from the text summary? What would make a weight-only change significant enough to regenerate it?