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
[Bug] [cdcsource] There are two bugs related to full database synchronization, specifically when handling the time field type in the source database
#3867
Open
3 tasks done
617450941 opened this issue
Oct 11, 2024
· 2 comments
I had searched in the issues and found no similar issues.
What happened
There are two bugs related to full database synchronization, specifically when handling the time field type in the source database
1.In the inherited subclass, the initTypeConverterList method does not set the convertTimeType method, resulting in the time type data not being processed.
2.Inside the convertTimeType method, there is also an issue with the data type conversion logic.
What you expected to happen
There are two bugs related to full database synchronization, specifically when handling the time field type in the source database
1.In the inherited subclass, the initTypeConverterList method does not set the convertTimeType method, resulting in the time type data not being processed.
2.Inside the convertTimeType method, there is also an issue with the data type conversion logic.
How to reproduce
Create a TIME data type field in the MySQL source database, then use full database synchronization.
Hello @, this issue has not been active for more than 30 days. This issue will be closed in 7 days if there is no response. If you have any questions, you can comment and reply.
Search before asking
What happened
There are two bugs related to full database synchronization, specifically when handling the time field type in the source database



1.In the inherited subclass, the initTypeConverterList method does not set the convertTimeType method, resulting in the time type data not being processed.
2.Inside the convertTimeType method, there is also an issue with the data type conversion logic.
What you expected to happen
There are two bugs related to full database synchronization, specifically when handling the time field type in the source database
1.In the inherited subclass, the initTypeConverterList method does not set the convertTimeType method, resulting in the time type data not being processed.
2.Inside the convertTimeType method, there is also an issue with the data type conversion logic.
How to reproduce
Create a TIME data type field in the MySQL source database, then use full database synchronization.
Anything else
No response
Version
1.1.0
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: