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]: fail to drop an index if there are multpile indexes of multiple vector fields #33327

Closed
1 task done
yanliang567 opened this issue May 23, 2024 · 3 comments
Closed
1 task done

[Bug]: fail to drop an index if there are multpile indexes of multiple vector fields #33327

yanliang567 opened this issue May 23, 2024 · 3 comments
Assignees
@yanliang567
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
2.4.5

Comments

@yanliang567
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: v2.4.2
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka):     
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus   2.4.3

Current Behavior

  1. fail to drop an index if there are multiple indexes
    image

Expected Behavior

  1. drop successfully

Steps To Reproduce

1. create a collection with 3 vector fields
2. build index for the 3 vector fields
3. try to drop one of the vector indexes

Milvus Log

No response

Anything else?

No response
@yanliang567 yanliang567 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 23, 2024
@yanliang567 yanliang567 self-assigned this May 23, 2024
@yanliang567
Copy link
Contributor Author

/assign @XuanYang-cn
/unassign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 23, 2024
@yanliang567 yanliang567 added this to the 2.4.3 milestone May 23, 2024
@smellthemoon smellthemoon mentioned this issue May 29, 2024
Merged
@yanliang567 yanliang567 modified the milestones: 2.4.3, 2.4.4 May 30, 2024
@smellthemoon smellthemoon mentioned this issue May 30, 2024
Closed
@yanliang567 yanliang567 modified the milestones: 2.4.4, 2.4.5 Jun 5, 2024
sre-ci-robot pushed a commit to milvus-io/pymilvus that referenced this issue Jun 5, 2024
@smellthemoon
fix: use the existed index_name (#2107)
e95f5a5 
milvus-io/milvus#33327

Signed-off-by: lixinguo <[email protected]>
Co-authored-by: lixinguo <[email protected]>
smellthemoon added a commit to smellthemoon/pymilvus that referenced this issue Jun 5, 2024
@smellthemoon
fix: use the existed index_name (milvus-io#2107)
915982f 
milvus-io/milvus#33327

Signed-off-by: lixinguo <[email protected]>
Co-authored-by: lixinguo <[email protected]>
@smellthemoon smellthemoon mentioned this issue Jun 5, 2024
Merged
sre-ci-robot pushed a commit to milvus-io/pymilvus that referenced this issue Jun 5, 2024
@smellthemoon
fix: use the existed index_name (#2107) (#2118)
367c4a8 
milvus-io/milvus#33327

Signed-off-by: lixinguo <[email protected]>
Co-authored-by: lixinguo <[email protected]>
@XuanYang-cn
Copy link
Contributor

should be fixed, please help verify
/assign @yanliang567
/unassign

@yanliang567
Copy link
Contributor Author

verified on pymilvus 2.4.4rc8 and milvus 2.4-20240614-5fc1370f-amd64

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

@yanliang567 yanliang567

Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
2.4.5
Development

No branches or pull requests
2 participants
@XuanYang-cn @yanliang567