mirror of
https://github.com/agentscope-ai/ReMe.git
synced 2026-10-16 04:33:12 +00:00
b616944265
* docs(operations): explain that reindex cannot refresh stale chunks #524 reports that persisted chunks survive a chunker change and are never re-chunked. Maintainers closed #528 with the position that automatic invalidation stays out of scope and the recovery path is to clear derived state and let the watchers rescan, but that path was only described in the issue thread. The operations guide already warned that reindex does not rechunk; add the missing half: reindex reuses stored chunks as-is, so a chunker change requires the re-chunk recovery instead. * docs(operations): narrow recovery scope and stop the service before cleanup Review on #585: moving the whole metadata/ tree makes the resource watcher treat existing resources as newly added, which can update daily notes - so 'source files are never modified' was too broad, and the cleanup should target only the affected store's derived state while preserving unrelated catalogs. The recovery sequence now also stops the service before moving anything, so shutdown persistence cannot write the old in-memory state back over the cleanup. The reindex paragraph drops the repeated 'does not rechunk' explanation and focuses on when a rebuild from source is needed. English and Chinese pages stay symmetric. * docs(operations): simplify rechunk recovery guidance --------- Co-authored-by: jinli.yl <jinli.yl@alibaba-inc.com> |
||
|---|---|---|
| .. | ||
| reference | ||
| auto_dream.md | ||
| auto_link.md | ||
| auto_memory.md | ||
| auto_resource.md | ||
| blog_20260920.md | ||
| blog_20261009.md | ||
| configuration.md | ||
| contributing.md | ||
| docker.md | ||
| faq.md | ||
| framework.md | ||
| index.md | ||
| integrations.md | ||
| memory_as_file.md | ||
| memory_search.md | ||
| operations.md | ||
| plugin_development.md | ||
| plugin_management.md | ||
| proactive.md | ||
| quick_start.md | ||
| reme-blog.md | ||
| reme_scene.md | ||
| services.md | ||
| traffic.md | ||