Repository navigation
Document Milvus 2.6 full-feature roadmap - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Define a version-pinned roadmap for full Milvus 2.6.23 user-facing data and management support over both MySQL and PostgreSQL. Document the current 2.3.3 SDK / 2.6.2 test baseline, P0–P8 delivery stages, proposed SQL contracts, dependencies and real E2E acceptance requirements.
Add an inventory mapping all 117 MilvusService RPC declarations to delivery stages or evidenced boundaries, distinguishing deprecated, unimplemented and internal APIs. Link the roadmap from the README and explicitly label planned capabilities as unimplemented.
Validation: all 117 RPC names checked for omissions/duplicates against the pinned proto; local document links and whitespace checks pass; independent review found no blocking issues. Documentation only; existing CI will run before merge.