flinkcdc我们在生产环境遇到一个非常奇怪的问题要怎么解决？

我们在生产环境遇到一个非常奇怪的问题，CDC在监听到一个TABLE_MAP事件后，在context里找不到表信息而出现了... whose schema isn't known to this connector异常，怀疑可能和这里的TODO有关系导致schema里没有这个表。2024-03-01 00:00:07,215 ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource - Encountered change event 'Event{header=EventHeaderV4{timestamp=1709222407000, eventType=TABLE_MAP, serverId=34153158, headerLength=19, dataLength=62, nextPosition=459864703, flags=0}, data=TableMapEventData{tableId=4322148, database='dj_log', table='t_map_crash_log_202403', columnTypes=3, 8, 8, 3, 15, 15, 15, 18, columnMetadata=0, 0, 0, 0, 256, 1020, 2048, 0, columnNullability={}, eventMetadata=null}}' at offset {transaction_id=null, ts_sec=1709222392, file=binlog.010032, pos=459863947, gtids=0f6fc04c-6a08-11ed-bcb2-f29b611b6193:1-14394004114, server_id=34153158, event=2} for table dj_log.t_map_crash_log_202403 whose schema isn't known to this connector. One possible cause is an incomplete database history topic. Take a new snapshot in this case.
Use the mysqlbinlog tool to view the problematic event: mysqlbinlog --start-position=459864622 --stop-position=459864703 --verbose binlog.010032

2024-03-01 00:00:07,215 ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource - Error during binlog processing. Last offset stored = null, binlog reader near position = binlog.010032/459864622

2024-03-01 00:00:07,215 WARN com.ververica.cdc.connectors.mysql.debezium.task.context.MySqlErrorHandler - Schema for table dj_log.t_map_crash_log_202403 is null

2024-03-01 00:00:07,215 INFO io.debezium.connector.mysql.MySqlStreamingChangeEventSource - Error processing binlog event, and propagating to Kafka Connect so it stops this connector. Future binlog events read before connector is shutdown will be ignored.然后这个问题在2.3之后修复了？这个有相关的pr或者什么资料可以参考下嘛？