Immutable solution version
Knowledge created in versions prior to 1.9.1 is not usable after upgrading to 1.9.2
Complete solution
Dify: Contributor DhruvGorasiya identified the root cause: Weaviate 1.27.0+ requires the new named-vectors schema format (vectorConfig); existing knowledge data stored by Weaviate 1.19.0 uses the old format, so queries with weaviate-client v4 fail. The team published a migration guide and migration scripts preserving embeddings (see docs/weaviate/WEAVIATE_MIGRATION_GUIDE).
The problem
Issue langgenius/dify#27291 (closed, 113 comments): ### Self Checks - [x] I have read the Contributing Guide and Language Policy. - [x] This is only for bug report, if you would like to ask a question, please head to Discussions. - [x] I have searched for existing issues search for existing issues, including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文
The verified fix
Contributor DhruvGorasiya identified the root cause: Weaviate 1.27.0+ requires the new named-vectors schema format (vectorConfig); existing knowledge data stored by Weaviate 1.19.0 uses the old format, so queries with weaviate-client v4 fail. The team published a migration guide and migration scripts preserving embeddings (see docs/weaviate/WEAVIATEMIGRATIONGUIDE). Reporter-confirmed workaround from xiaoyesoso: change the knowledge base's embedding model, which triggers an automatic index rebuild and restores the knowledge base.
Evidence
In gh:langgenius/dify#27291 (https://github.com/langgenius/dify/issues/27291), someone reported: Issue langgenius/dify#27291 (closed, 113 comments): ### Self Checks - [x] I have read the Contributing Guide and Language Policy. - [x] This is only for bug report, if you would like to ask a question, please head to Discussions. - [x] I have searched for existing issues search for existing issues, including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文 The verified resolution from the thread: Contributor DhruvGorasiya identified the root cause: Weaviate 1.27.0+ requires the new named-vectors schema format (vectorConfig); existing knowledge data stored by Weaviate 1.19.0 uses the old format, so queries with weaviate-client v4 fail. The team published a migration guide and migration scripts preserving embeddings (see docs/weaviate/WEAVIATEMIGRATIONGUIDE). Reporter-confirmed workaround from xiaoyesoso: change the knowledge base's embedding model, which triggers an automatic index rebuild and restores the knowledge base.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_cz12WqH4ui1EBc8nugeTew" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Knowledge created in versions prior to 1.9.1 is not usable after upgrading to 1.9.2 <span>— Vectle</span></a>