-
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]: Milvus crashes with segment fault when using skip index #35882
Labels
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
chyezh
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
Aug 31, 2024
/assign |
@chyezh what is 'skip index'? |
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
Aug 31, 2024
it's used to filter out the segment that never meet a incoming expr. |
|
This was referenced Sep 2, 2024
sre-ci-robot
pushed a commit
that referenced
this issue
Sep 3, 2024
issue: #35882 Signed-off-by: chyezh <[email protected]>
Verify the issue by asan with following operations:
Before fixing:
After fixing, no memory violation reported. |
sre-ci-robot
pushed a commit
that referenced
this issue
Sep 3, 2024
issue: #35882 pr: #35907 Signed-off-by: chyezh <[email protected]>
jaime0815
pushed a commit
that referenced
this issue
Sep 4, 2024
issue: #35882 pr: #35907 Signed-off-by: chyezh <[email protected]>
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.
Is there an existing issue for this?
Environment
Current Behavior
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: