Skip to content

Latest commit

 

History

History
43 lines (26 loc) · 1.66 KB

File metadata and controls

43 lines (26 loc) · 1.66 KB

MEP: [Title]

  • Created: YYYY-MM-DD
  • Author(s): @github-handle
  • Status: Draft | Under Review | Approved | Implemented | Deprecated
  • Component: DataNode | QueryNode | Proxy | Coordinator | Storage | Index | SDK | Other
  • Related Issues: #xxx
  • Released: [Milvus Release Version, if applicable]

Summary

What are we going to do? Provide a brief overview of the proposal.

Motivation

Why are we doing this? What problem does it solve?

Public Interfaces (optional)

Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed.

Design Details

Describe the new thing you want to do in appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgment based on the scope of the change.

Compatibility, Deprecation, and Migration Plan (optional)

  • What impact (if any) will there be on existing users?
  • If we are changing behaviors how will we phase out the older behavior?
  • If we need special migration tools, describe them here.
  • When will we remove the existing behavior?

Test Plan

Describe in a few sentences how the MEP will be tested. We are mostly interested in system tests (since unit tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?

Rejected Alternatives (optional)

If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other ways.

References (optional)

Briefly list all references.