<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>GraphRAG on Jeanphilo Blog</title><link>https://shio-chan-dev.github.io/jeanblog/zh/tags/graphrag/</link><description>Recent content in GraphRAG on Jeanphilo Blog</description><generator>Hugo -- 0.165.0</generator><language>zh-cn</language><lastBuildDate>Wed, 26 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://shio-chan-dev.github.io/jeanblog/zh/tags/graphrag/index.xml" rel="self" type="application/rss+xml"/><item><title>管线只负责一次运行：文档索引系统不该默认共享跨 Run 节点</title><link>https://shio-chan-dev.github.io/jeanblog/zh/thoughts/thoughts/pipeline-is-not-cross-run-task-sharing/</link><pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/thoughts/thoughts/pipeline-is-not-cross-run-task-sharing/</guid><description>一次 RAG 与知识图谱独立运行模式的架构讨论，让我重新分清了 Pipeline、Run、动态 Target 和跨请求 Singleflight。我的结论是：文档索引系统更适合让每次 Run 独立拥有状态和节点，同一文件只保留一个活动 Run，并通过持久化产物复用结果，而不是共享正在执行的节点任务。</description></item></channel></rss>