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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Add scalar index engine version for compatibility #39203

Closed
1 task done
xiaocai2333 opened this issue Jan 13, 2025 · 2 comments
Closed
1 task done

[Bug]: Add scalar index engine version for compatibility #39203

xiaocai2333 opened this issue Jan 13, 2025 · 2 comments
Assignees
@xiaocai2333
Labels
kind/bug Issues or changes related a bug priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
2.5.4

Comments

@xiaocai2333
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.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

The 2.4 version Milvus cannot load the INVERTED indexes built by the 2.5 version.
This situation can easily occur during a rolling upgrade.

Expected Behavior

Milvus 2.5 will build a 2.4 version of the INVERTED index if it detects that the indexing request comes from Milvus 2.4(distinguished by the scalar index engine version).

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@xiaocai2333 xiaocai2333 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 Jan 13, 2025
@xiaocai2333 xiaocai2333 mentioned this issue Jan 13, 2025
Merged
@yanliang567
Copy link
Contributor

/assign @xiaocai2333
/unassign

@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 Jan 13, 2025
@yanliang567 yanliang567 added this to the 2.5.3 milestone Jan 13, 2025
@yanliang567 yanliang567 added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Jan 13, 2025
@xiaocai2333 xiaocai2333 mentioned this issue Jan 14, 2025
Merged
sre-ci-robot pushed a commit that referenced this issue Jan 14, 2025
@xiaocai2333
fix: [2.5] Add scalar index engine version for compatibility (#39236)
4270174 
issue: #39203 

master pr: #39204

---------

Signed-off-by: Cai Zhang <[email protected]>
sre-ci-robot pushed a commit that referenced this issue Jan 15, 2025
@xiaocai2333
fix: Add scalar index engine version for compatibility (#39204)
6d45dd5 
issue: #39203

---------

Signed-off-by: Cai Zhang <[email protected]>
@yanliang567 yanliang567 modified the milestones: 2.5.3, 2.5.4 Jan 16, 2025
gifi-siby pushed a commit to gifi-siby/milvus that referenced this issue Jan 16, 2025
@xiaocai2333 @gifi-siby
fix: Add scalar index engine version for compatibility (milvus-io#39204)
03e504f 
issue: milvus-io#39203

---------

Signed-off-by: Cai Zhang <[email protected]>
@yanliang567
Copy link
Contributor

verified on 2.5-20250119-57bcb1bf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xiaocai2333 xiaocai2333

Labels
kind/bug Issues or changes related a bug priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
2.5.4
Development

No branches or pull requests
2 participants
@xiaocai2333 @yanliang567