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]: Failed to delete data resulting in repeated insertion of data(删除数据未成功导致重复插入数据) #38712

Open
1 task done
uniqueSkeeter opened this issue Dec 24, 2024 · 1 comment
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@uniqueSkeeter
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:V2.40
- Deployment mode(standalone or cluster):standalone
- SDK version(e.g. pymilvus v2.0.0rc2): 2.4.4
- OS(Ubuntu or CentOS): Ubuntu

Current Behavior

Failed to delete data resulting in repeated insertion of data

code as below:

先删除已有的商品

    for product in param.productList:
        query_filter = f"display_prd_id=={product.disPlayPrdId}"
        product_kb.delete(expr=query_filter)
    # 将商品信息转为Document
    docs = to_product_docs(param.productList)
    text_splitter = RecursiveCharacterTextSplitter(chunk_size=600, chunk_overlap=0)
    split_docs = text_splitter.split_documents(docs)
    # 文档向量化,并创建数据库
    product_kb.add_documents(split_docs)

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

20241224-172604

@uniqueSkeeter uniqueSkeeter 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 Dec 24, 2024
Copy link
Contributor

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

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 needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants