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.

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

[Bug]: upsert into milvus use hybridSearch and search get same id result is diff #37677

Open
1 task done
I-am-DJ opened this issue Nov 14, 2024 · 16 comments
Open
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@I-am-DJ
Copy link

I-am-DJ commented Nov 14, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:V2.4.5
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

对应collection结构

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@I-am-DJ I-am-DJ 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 Nov 14, 2024
Copy link
Contributor

The title and description of this issue contains Chinese. Please use English to describe your issue.

@I-am-DJ I-am-DJ changed the title [Bug]: upsert写入milvus后用hybridSearch和search得到的结果不一样 [Bug]: upsert into milvus use hybridSearch and search get same id result is diff Nov 14, 2024
@I-am-DJ
Copy link
Author

I-am-DJ commented Nov 14, 2024

对应collection结构
image
hybridSearch结果:

@I-am-DJ
Copy link
Author

I-am-DJ commented Nov 14, 2024

hybridSearch结果:
image
search:
image

@yanliang567
Copy link
Contributor

@I-am-DJ could you please try
collection.query(expr='id==136300913', output_fields=['count(*)'] meanswhile, i will try to reproduce it in house.

/assign @I-am-DJ

@I-am-DJ
Copy link
Author

I-am-DJ commented Nov 14, 2024

@I-am-DJ您能否同时尝试 collection.query(expr='id==136300913', output_fields=['count(*)'] 一下,我会尝试在家里重现它。

/分配@I-am-DJ

[{"extInfo":{"count(*)":6}}] @yanliang567

@yanliang567
Copy link
Contributor

[{"extInfo":{"count(*)":6}}]

it means that you have 6 entities that have the same id==136300913 :(
I believe that it was caused by duplicated id...

@I-am-DJ
Copy link
Author

I-am-DJ commented Nov 14, 2024

[{"extInfo":{"count(*)":6}}]

it means that you have 6 entities that have the same id==136300913 :( I believe that it was caused by duplicated id...

it not delete the original data when upsert the same id ? @yanliang567

@I-am-DJ
Copy link
Author

I-am-DJ commented Nov 14, 2024

i see the doc can be overwritten https://milvus.io/docs/insert-update-delete.md#Upsert-entities

@I-am-DJ
Copy link
Author

I-am-DJ commented Nov 14, 2024

is need update to v2.4.12 ? #36274 @yanliang567

@yanliang567
Copy link
Contributor

do you only use upsert() for data ingestion? no insert() or bulk_insert()?

@I-am-DJ
Copy link
Author

I-am-DJ commented Nov 14, 2024

do you only use upsert() for data ingestion? no insert() or bulk_insert()?

yes only use upsert()

@xiaofan-luan
Copy link
Collaborator

maybe this is a bug for 2.4.5

@I-am-DJ
Copy link
Author

I-am-DJ commented Nov 15, 2024

maybe this is a bug for 2.4.5

how can i solve this problem, delete first then upsert? @xiaofan-luan

@yanliang567
Copy link
Contributor

please try to upgrade to 2.4.15

@yanliang567
Copy link
Contributor

@I-am-DJ any updates

@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 25, 2024
@yanliang567 yanliang567 removed their assignment Nov 25, 2024
Copy link

stale bot commented Dec 28, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants