Install
openclaw skills install @sdk-team/alibabacloud-lindorm-vector-migrate-skill向量数据库迁移助手 — 从 Milvus、Elasticsearch、Lindorm 或 Qdrant 迁移向量数据至阿里云 Lindorm。支持从源库导出为 CSV 文件后上传 OSS 再导入。通过对话收集参数,直接生成并执行代码完成迁移。支持断点续传、字段排除、DDL 预览确认等。 Triggers: "迁移", "向量数据", "向量迁移", "数据迁移", "vector transfer", "migration", "vector database", "Lindorm 迁移", "迁移到 Lindorm", "ES 迁移", "Qdrant 迁移", "断点续传", "csv 文件导入", "oss 导入", "导出到 CSV", "导出为 CSV", "export to CSV", "CSV 导出".
openclaw skills install @sdk-team/alibabacloud-lindorm-vector-migrate-skillMigrate vector data from Milvus / Elasticsearch / Lindorm / Qdrant / CSV files to Alibaba Cloud Lindorm Search Engine. Supports exporting source indices to CSV files. The Agent is responsible for collecting parameters, generating and executing code to complete all operations.
| Category | Sub-Scenarios | Reference Docs |
|---|---|---|
| 01-Dev | Source migration guides (Milvus/ES/Lindorm/Qdrant/CSV), CSV export, complete workflow | references/01-dev/ |
| 02-Ops | Pre-checks, post-migration validation, TTL configuration, checkpoint resume | references/02-ops/ |
| 03-Ref | Type mapping, bulk write API, code migration, official documentation | references/03-ref/ |
User Request
├── Complete migration workflow → references/01-dev/workflow.md
│
├── Source data reading → 01-dev
│ ├── Milvus → references/01-dev/milvus-migrate.md
│ ├── Elasticsearch → references/01-dev/elasticsearch-migrate.md
│ ├── Lindorm source → references/01-dev/lindorm-migrate.md
│ ├── Qdrant → references/01-dev/qdrant-migrate.md
│ ├── CSV file (OSS) → references/01-dev/csv-import.md
│ └── Export to CSV → references/01-dev/csv-export.md
│
├── Migration operations → 02-ops
│ ├── Post-migration validation → references/02-ops/postcheck.md
│ ├── TTL configuration / source TTL conversion → references/02-ops/ttl-config.md
│ └── Checkpoint resume mechanism → references/02-ops/checkpoint-resume.md
│
├── Reference materials → 03-ref
│ ├── CSV file format specification → references/03-ref/csv-format.md
│ ├── Field types / distance metrics / DDL generation → references/03-ref/type-mapping.md
│ ├── Bulk write / index creation / index building → references/03-ref/bulk-write.md
│ ├── Application code migration advice → references/03-ref/code-migration.md
│ └── API details uncertain → references/03-ref/official-refs.md
Complete workflow (Step 1-7) is detailed in references/01-dev/workflow.md.
| Step | Summary | Detailed Guide |
|---|---|---|
| 1. Collect information | Source/target connection parameters, migration options, network type | workflow.md#step-1 |
| 1.5 Export to CSV (optional) | Export from source index to CSV → user uploads to OSS → connect to CSV import flow | references/01-dev/csv-export.md |
| 2. Pre-checks | Connection validation, space estimation, type compatibility, TTL detection | workflow.md#step-2 |
| 3. Generate DDL | Lindorm ES-compatible mapping generation and confirmation | workflow.md#step-3 |
| 4. Create index | Target index creation | workflow.md#step-4 |
| 5. Execute migration | Source scan → Lindorm bulk write, checkpoint resume | workflow.md#step-5 |
| 6. Post-migration validation | Row count validation, random sampling, vector similarity, TTL validation | workflow.md#step-6 |
| 7. Code migration | Advice for migrating application code from source to Lindorm | workflow.md#step-7 |
"knn.offline.construction": true; after triggering Build, MUST poll until ready or failed, MUST NOT exit polling while in building status; MUST NOT use _forcemerge as a substitute for the Build APIos.environ.get("LINDORM_PASSWORD", "")), MUST NOT use the user's actual password as a fallback default value[INTERRUPTED], fall back to [PROGRESS]), parse the cursor value while preserving its original type (int/str/list) for the resume parameters, and MUST NOT silently restart from the beginning. If parsing fails, MUST inform the user and display the raw log content