mirror of https://github.com/milvus-io/milvus.git
[skip ci] Improve the developer_guides (#7592)
Signed-off-by: min.tian <min.tian.cn@gmail.com>pull/7659/head
parent
f8beb6d409
commit
9c4170d24f
|
@ -2,7 +2,7 @@
|
|||
|
||||
## 1. System Overview
|
||||
|
||||
In this section, we sketch the system design of Milvus, including data model, data organization, architecture, and state synchronization.
|
||||
In this section, we sketch the system design of Milvus, including the data model, data organization, architecture, and state synchronization.
|
||||
|
||||
|
||||
|
||||
|
@ -14,7 +14,7 @@ Milvus exposes the following set of data features to applications:
|
|||
|
||||
* a query language specifies data definition, data manipulation, and data query, where data definition includes create, drop, and data manipulation includes insert, upsert, delete, and data query falls into three types, primary key search, approximate nearest neighbor search (ANNS), ANNS with predicates.
|
||||
|
||||
The requests' execution order is strictly in accordance with their issue-time order. We take proxy's issue time as a request's issue time. For a batch request, all its sub-requests share a same issue time. In cases there are multiple proxies, issue time from different proxies are regarded as coming from a central clock.
|
||||
The requests' execution order is strictly in accordance with their issue-time order. We take proxy's issue time as a request's issue time. For a batch request, all its sub-requests share the same issue time. In cases there are multiple proxies, issue time from different proxies are regarded as coming from a central clock.
|
||||
|
||||
Transaction is currently not supported by Milvus.
|
||||
|
||||
|
|
Loading…
Reference in New Issue