milvus/internal/metastore
congqixia b53e9e80d3
fix: [2.5] Make MultiSaveAndRemove execute removal first (#43409)
Cherry-pick from master
pr: #43408 
Related to #43407

When `MultiSaveAndRemove` like ops contains same key in saves and
removal keys it may cause data lost if the execution order is save first
than removal.

This PR make all the kv execute removal first then save the new values.
Even when same key appeared in both saves and removals, the new value
shall stay.

Signed-off-by: Congqi Xia <congqi.xia@zilliz.com>
2025-07-18 15:44:56 +08:00
..
kv fix: [2.5] Make MultiSaveAndRemove execute removal first (#43409) 2025-07-18 15:44:56 +08:00
mocks enhance: [2.5] Skip modify field meta when rename collection or rename dbName (#42876) 2025-06-23 18:24:43 +08:00
model enhance: [2.5] Use v2 package name for pkg module (#40117) 2025-02-23 00:46:01 +08:00
catalog.go enhance: [2.5] Skip modify field meta when rename collection or rename dbName (#42876) 2025-06-23 18:24:43 +08:00
catalog_test.go Refactor RootCoord (#18930) 2022-09-05 13:29:11 +08:00