From 41dc494d5b27d604bc93cf5238769aa75554e8d5 Mon Sep 17 00:00:00 2001 From: Zhen Ye Date: Wed, 17 Sep 2025 10:26:00 +0800 Subject: [PATCH] enhance: segment not flush at coord after schema change (#44412) issue: #43289 - introduced by #43500 Signed-off-by: chyezh --- internal/flushcommon/pipeline/flow_graph_dd_node.go | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/internal/flushcommon/pipeline/flow_graph_dd_node.go b/internal/flushcommon/pipeline/flow_graph_dd_node.go index a522f998b8..06e75ac9dc 100644 --- a/internal/flushcommon/pipeline/flow_graph_dd_node.go +++ b/internal/flushcommon/pipeline/flow_graph_dd_node.go @@ -282,6 +282,16 @@ func (ddn *ddNode) Operate(in []Msg) []Msg { } else { logger.Info("handle manual flush message success") } + case commonpb.MsgType_AddCollectionField: + schemaMsg := msg.(*adaptor.SchemaChangeMessageBody) + logger := log.With( + zap.String("vchannel", ddn.Name()), + zap.Int32("msgType", int32(msg.Type())), + zap.Uint64("timetick", schemaMsg.SchemaChangeMessage.TimeTick()), + zap.Int64s("segmentIDs", schemaMsg.SchemaChangeMessage.Header().FlushedSegmentIds), + ) + logger.Info("receive schema change message") + ddn.msgHandler.HandleSchemaChange(ddn.ctx, schemaMsg.SchemaChangeMessage) } }