-
Notifications
You must be signed in to change notification settings - Fork 3k
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 rows when set autoid==true fail #36710
Comments
/assign |
which milvus version are you running? |
2.4.10 |
milvus-io/milvus#36710 Signed-off-by: lixinguo <[email protected]> Co-authored-by: lixinguo <[email protected]>
milvus-io/milvus#36710 Signed-off-by: lixinguo <[email protected]> Co-authored-by: lixinguo <[email protected]>
@yanliang567 could you please help to add some related tests? |
/assign @yanliang567 |
@smellthemoon could you please share the reproduce code or steps, we already had tests for upsert with autoid==true |
@smellthemoon did this fix cp to 2.4 branch? |
yes, update pymilvus version to 2.4.13 can fix it. the problem will only occurs when upsert by rows. |
import time dim = 3 milvus_client.drop_collection(collection_name) schema = milvus_client.create_schema( schema.add_field(field_name="id", datatype=DataType.INT64, is_primary=True) index_params = milvus_client.prepare_index_params() milvus_client.create_collection( res = milvus_client.query(collection_name=collection_name, consistency_level="Strong", filter="id > 0") res = milvus_client.query(collection_name=collection_name, consistency_level="Strong", filter="id > 0") |
working on test verifivcation and development |
verified on master-20241012-d45e2677-amd64 |
related issue: #36710 --------- Signed-off-by: yanliang567 <[email protected]>
related issue: #36710 pr: #36820 --------- Signed-off-by: yanliang567 <[email protected]>
Is there an existing issue for this?
Environment
Current Behavior
raise DataNotMatchException(message=ExceptionsMessage.DataTypeInconsistent) from e
pymilvus.exceptions.DataNotMatchException: <DataNotMatchException: (code=1, message=The Input data type is inconsistent with defined schema, please check it.)>
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: