You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// 1.If the event is a single table DDL, it will be added to the sink for writing to downstream(async). If the ddl leads to add new tables or drop tables, it should send heartbeat to maintainer
261
-
// 2. If the event is a multi-table DDL / sync point Event, it will generate a TableSpanStatus message with ddl info to send to maintainer.
277
+
// 2. If the event is a multi-table DDL / sync point Event, it will generate a TableSpanBlockStatus message with ddl info to send to maintainer.
// b. If the tableProgress is not empty, we will generate a CheckTableProgressEmptyTask to periodly check whether the tableProgress is empty,
252
252
// and then add the DDL event to the sink for writing to downstream(async).
253
253
// 2. If it is a multi-table DDL,
254
-
// a. If the tableProgress is empty(previous events are flushed successfully),We will generate a TableSpanStatus message with ddl info to send to maintainer.
254
+
// a. If the tableProgress is empty(previous events are flushed successfully),We will generate a TableSpanBlockStatus message with ddl info to send to maintainer.
255
255
// b. If the tableProgress is not empty, we will generate a CheckTableProgressEmptyTask to periodly check whether the tableProgress is empty,
256
-
// and then we will generate a TableSpanStatus message with ddl info to send to maintainer.
257
-
// for the multi-table DDL, we will also generate a ResendTask to resend the TableSpanStatus message with ddl info to maintainer each 50ms to avoid message is missing.
256
+
// and then we will generate a TableSpanBlockStatus message with ddl info to send to maintainer.
257
+
// for the multi-table DDL, we will also generate a ResendTask to resend the TableSpanBlockStatus message with ddl info to maintainer each 50ms to avoid message is missing.
258
258
//
259
259
// Considering for ddl event, we always do an async write, so we need to be blocked before the ddl event flushed to downstream successfully.
260
260
// Thus, we add a callback function to let the hander be waked when the ddl event flushed to downstream successfully.
0 commit comments