Skip to content

RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.

docs: add tag migration description (#21020)

YanZhangbf64bedbab91
diff --git a/docs/administrator/migration/migration_overview.md b/docs/administrator/migration/migration_overview.md
index 4c124fe886..2c4bec45fa 100644
--- a/docs/administrator/migration/migration_overview.md
+++ b/docs/administrator/migration/migration_overview.md
@@ -16,6 +16,8 @@ Use this page to identify the correct path, prepare a recoverable backup, and th
Every `v0.x` deployment must successfully start and pass verification on `v0.27.2`, and must then be upgraded to `v1.0.0-rc1`. Do not skip either version or upgrade directly from `v0.x` to a later `v1.x` release.
The `v0.27.2` to `v1.0.0-rc1` migration is irreversible. Before starting it, stop all data-writing tasks and create a complete, verified `v0.27.2` recovery point. If migration fails, do not retry against the partially migrated data; restore the complete recovery point before trying again.
+
+The Go backend no longer binds tag files to dedicated datasets. Tag datasets created by the Python backend are not valid after this migration; plan to reconfigure their tag files after the upgrade. See [Upgrade from v0.x to v1.x](./upgrade_from_v0_to_v1.md#3-upgrade-from-v0272-to-v100-rc1) for details.
:::
:::note Command assumptions
diff --git a/docs/administrator/migration/upgrade_from_v0_to_v1.md b/docs/administrator/migration/upgrade_from_v0_to_v1.md
index 55ca25667e..e69a5e5b96 100644
--- a/docs/administrator/migration/upgrade_from_v0_to_v1.md
+++ b/docs/administrator/migration/upgrade_from_v0_to_v1.md
@@ -129,6 +129,10 @@ Do not continue until `v0.27.2` passes all checks. The older GraphRAG and RAPTOR
This mandatory step is different from the earlier checkpoints. It introduces the v1 runtime and performs an irreversible data migration.
+:::warning Tag datasets are not migrated
+In the Python backend, tag files are bound to a dedicated dataset. The Go backend does not bind tag files to datasets. After the migration, existing Tag datasets from the Python backend are no longer valid. Reconfigure the tag files in the Go backend after the upgrade.
+:::
+
### 3.1. Stop and back up v0.27.2
Make sure that document parsing, synchronization, and Agent tasks have finished. From the `v0.27.2` repository root, stop the deployment:
@@ -206,6 +210,8 @@ First verify that `v1.0.0-rc1` started successfully and that its migration compl
Sign in to RAGFlow and confirm that existing data and configuration are present, then test document retrieval, a new document upload, one Chat, and one Agent run.
+If the Python deployment used Tag datasets, confirm that they are no longer treated as datasets, reconfigure their tag files in the Go backend, and verify tag extraction on a representative document.
+
Keep the `v0.27.2` backup until the upgraded deployment has completed acceptance testing and operated successfully under normal workload.
## 6. Recover from a failed upgrade