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]: For pk field, it was not allowed to firstly load the index and then load the field data. #32744

Open
1 task done
v1incent opened this issue Apr 30, 2024 · 1 comment
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@v1incent
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: master branch
- 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

For sealed segment and pk field, it was not allowed to firstly load the index and then load the field data.
The related code is in LoadFieldData in SegmentSealedImpl.cpp,

AssertInfo(insert_record_.empty_pks(), "already exists");

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@v1incent v1incent 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 Apr 30, 2024
@yanliang567
Copy link
Contributor

/assign @liliu-z
please help to take a look at this issue and related pr

/unassign

@sre-ci-robot sre-ci-robot assigned liliu-z and unassigned yanliang567 May 1, 2024
@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 1, 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 triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants