milvus/internal/datanode
Zhen Ye 99dff06391
enhance: using streaming service in insert/upsert/flush/delete/querynode (#35406)
issue: #33285

- using streaming service in insert/upsert/flush/delete/querynode
- fixup flusher bugs and refactor the flush operation
- enable streaming service for dml and ddl
- pass the e2e when enabling streaming service
- pass the integration tst when enabling streaming service

---------

Signed-off-by: chyezh <chyezh@outlook.com>
Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
2024-08-29 10:03:08 +08:00
..
allocator Replace manual composed grpc call with Broker methods (#27676) 2023-10-13 09:55:34 +08:00
channel fix: Use correct release func when datanode unwatch a channel (#35655) 2024-08-23 14:09:03 +08:00
compaction enhance: Add back BF lazy load logic for datanode watch channel (#35646) 2024-08-22 19:42:57 +08:00
importv2 fix: Fix panic due to empty candidate import segments (#35673) 2024-08-27 17:08:59 +08:00
iterators enhance: Add ctx in SyncTask.Run to be cancellable (#34042) 2024-06-25 14:22:04 +08:00
util enhance: Implement flusher in streamingNode (#34942) 2024-08-02 18:30:23 +08:00
data_node_test.go enhance: Implement flusher in streamingNode (#34942) 2024-08-02 18:30:23 +08:00
data_node.go enhance: using streaming service in insert/upsert/flush/delete/querynode (#35406) 2024-08-29 10:03:08 +08:00
metrics_info.go enhance: Implement flusher in streamingNode (#34942) 2024-08-02 18:30:23 +08:00
OWNERS [skip ci]Update OWNERS files (#11898) 2021-11-16 15:41:11 +08:00
README.md [skip ci]Change uppercase of MinIO (#9539) 2021-10-09 11:22:58 +08:00
services_test.go enhance: Add back BF lazy load logic for datanode watch channel (#35646) 2024-08-22 19:42:57 +08:00
services.go enhance: Add back BF lazy load logic for datanode watch channel (#35646) 2024-08-22 19:42:57 +08:00

Data Node

DataNode is the component to write insert and delete messages into persistent blob storage, for example MinIO or S3.

Dependency

  • KV store: a kv store that persists messages into blob storage.
  • Message stream: receive messages and publish imformation
  • Root Coordinator: get the latest unique IDs.
  • Data Coordinator: get the flush information and which message stream to subscribe.