mirror of https://github.com/milvus-io/milvus.git
7cf2be09b5
When the TimeTravel functionality was previously removed, it inadvertently affected the MVCC functionality within the system. This PR aims to reintroduce the internal MVCC functionality as follows: 1. Add MvccTimestamp to the requests of Search/Query and the results of Search internally. 2. When the delegator receives a Query/Search request and there is no MVCC timestamp set in the request, set the delegator's current tsafe as the MVCC timestamp of the request. If the request already has an MVCC timestamp, do not modify it. 3. When the Proxy handles Search and triggers the second phase ReQuery, divide the ReQuery into different shards and pass the MVCC timestamp to the corresponding Query requests. issue: #29656 pr: #29749 Signed-off-by: zhenshan.cao <zhenshan.cao@zilliz.com> |
||
|---|---|---|
| .. | ||
| internalpb | ||
| OWNERS | ||
| data_coord.proto | ||
| etcd_meta.proto | ||
| index_cgo_msg.proto | ||
| index_coord.proto | ||
| internal.proto | ||
| plan.proto | ||
| proxy.proto | ||
| query_coord.proto | ||
| root_coord.proto | ||
| segcore.proto | ||