alkscr ab27609a64 Fix: whole knowledge graph lost after removing any document in the knowledge base (#7151) ... ### What problem does this PR solve? When you removed any document in a knowledge base using knowledge graph, the graph's `removed_kwd` is set to "Y". However, in the function `graphrag.utils.get_gaph`, `rebuild_graph` method is passed and directly return `None` while `removed_kwd=Y`, making residual part of the graph abandoned (but old entity data still exist in db). Besides, infinity instance actually pass deleting graph components' `source_id` when removing document. It may cause wrong graph after rebuild. ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)		2025-04-30 09:43:17 +08:00
..
__init__.py
community_report_prompt.py	Optimize graphrag again (#6513)	2025-03-26 15:34:42 +08:00
community_reports_extractor.py	fix(nursery): Fix Closure Trap Issues in Trio Concurrent Tasks (#7106)	2025-04-18 18:00:20 +08:00
entity_embedding.py
extractor.py	<think> tag is missing. (#7256)	2025-04-24 11:44:10 +08:00
graph_extractor.py	perf: Optimize GraphRAG’s LOOP_PROMPT (#7356)	2025-04-28 13:31:04 +08:00
graph_prompt.py	perf: Optimize GraphRAG’s LOOP_PROMPT (#7356)	2025-04-28 13:31:04 +08:00
index.py	Fix: whole knowledge graph lost after removing any document in the knowledge base (#7151)	2025-04-30 09:43:17 +08:00
leiden.py	Optimize graphrag again (#6513)	2025-03-26 15:34:42 +08:00
mind_map_extractor.py	fix(nursery): Fix Closure Trap Issues in Trio Concurrent Tasks (#7106)	2025-04-18 18:00:20 +08:00
mind_map_prompt.py
smoke.py	Refactor graphrag to remove redis lock (#5828)	2025-03-10 15:15:06 +08:00