Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: --drop_exist_collection and --drop_exist_index not work when execute restore command #505

Open
hellogitee opened this issue Jan 16, 2025 · 2 comments
Open

[Bug]: --drop_exist_collection and --drop_exist_index not work when execute restore command #505

hellogitee opened this issue Jan 16, 2025 · 2 comments
Assignees
@huanghaoyuanhhy

Comments

@hellogitee
Copy link

Current Behavior

When I execute restore command and add these two parameters,It still reported error The collection to restore already exists

Expected Behavior

these two parameters can work

Steps To Reproduce

No response

Environment

0.4.30 (Built on 2025-01-14T11:41:59Z from Git SHA f369636e6fda80fee354778480ddd260f2f93dcb)

Anything else?

No response
@hellogitee
Copy link
Author

milvus-backup restore -n full_bak_20250116 -c default.my_collection1 --drop_exist_collection --drop_exist_index --config configs/backup-19061.yaml

0.4.30 (Built on 2025-01-14T11:41:59Z from Git SHA f369636)
The collection to restore already exists, backupCollectName: default.my_collection1, targetCollectionName: default.my_collection1
duration:0 s

@huanghaoyuanhhy
Copy link
Collaborator

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@huanghaoyuanhhy huanghaoyuanhhy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hellogitee @huanghaoyuanhhy