[MDEV-20860] Mariadb 10.0.38 datetime representation in binlog Created: 2019-10-18 Updated: 2019-10-24 Resolved: 2019-10-24 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Temporal Types |
| Affects Version/s: | 10.0.38 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Dawid Szymaniuk-Paryż | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | binlog, datetime | ||
| Description |
|
HI. I'm trying to connect kafka connector to my existing database and it reports problem when I try to insert/delete/update rows:
I use datetime field in my table:
This is my sample insert:
When I select this record I get proper value:
But the problem is that this filed has strange value in binlog file:
This is my configuration file:
In new version of mariadb I don't have this problem. Unfortunately version 10.0.38 is our production version and I can't migrate to newer version for now. Do you know how to fix this problem without upgrading mariadb? Thanks |
| Comments |
| Comment by Dawid Szymaniuk-Paryż [ 2019-10-21 ] |
|
Hi, any chance that someone will look at this issue? |
| Comment by Sergei Golubchik [ 2019-10-24 ] |
|
In MariaDB 5.3 to 10.0 the binary format for high-res temporal values is different from what MySQL is using (because MariaDB implementation predates MySQL 5.6 implementation). You have some kind of a binlog reader client, and apparently it expects MySQL high-res temporal values in the binlog and is not compatible with MariaDB binlog. In 10.1 you can use --opt_mysql56_temporal_format option to make MariaDB to use MySQL-compatible temporal format. In 10.0 there is no way to do it. Besides, 10.0 has reached end of life more than a half a year ago, there will be no more 10.0 releases. There is nothing we can change in 10.0 at this point. |