Data truncation: Incorrect datetime value: '0' for column 'notice_date' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '0' for column 'notice_date' at row 1

insert 语句挂起
otter 4.2.13
源 mysql5.7
目标 mysql5.6
Data truncation: Incorrect datetime value: '0' for column 'notice_date' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '0' for column 'notice_date' at row 1

源表+目标表，都是timestamp
desc
| notice_date | timestamp | YES | | NULL | |

EventColumn[index=23,columnType=93,columnName=notice_date,columnValue=0,isNull=false,isKey=false,isUpdate=true]

Start by tracing the insert path for EventColumn values, focusing on notice_date with columnType 93 and columnValue 0 when synchronizing from MySQL 5.7 to 5.6. Reproduce the reported timestamp case and determine what behavior is expected; done means the insert no longer raises the reported MysqlDataTruncation error.

Written by the indexing model from the issue text.