milvus-io/milvus

[Feature]: How to migrate data from Milvus 2.x to another milvus

Open

#26,621 opened on Aug 28, 2023

View on GitHub
 (3 comments) (0 reactions) (2 assignees)Go (4,000 forks)batch import
help wantedkind/feature

Repository metrics

Stars
 (44,298 stars)
PR merge metrics
 (Avg merge 7d 8h) (280 merged PRs in 30d)

Description

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe.

我本地初始化了一部分数据，要迁移到线上的Milvus，如何M2M 迁移， DM版本好像不支持2.x

Describe the solution you'd like.

No response

Describe an alternate solution.

No response

Anything else? (Additional Context)

No response

Contributor guide

Research direction
First, review the issue comments to gather any additional context about the M2M migration request and the DM tool limitation. Then, search the Milvus codebase for existing migration utilities or documentation in the 'tools' or 'docs' directories. Consider proposing a high level design or a minimal viable migration script. Avoid diving deep into implementation until the scope is clarified with maintainers.
Tech stack
go
Domain
database
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Milvus architectureVector database conceptsData migration strategies
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15