[MDEV-15695] Can't replicate multiple DATETIME columns from 10.2 to 5.5 Created: 2018-03-27  Updated: 2018-03-27  Resolved: 2018-03-27

Status: Closed
Project: MariaDB Server
Component/s: Data types
Affects Version/s: 5.5, 10.2.13
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Doug Van Hollen Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Linux



 Description   

When executing the below on a 10.2 master, a 5.5 slave will fail:

DROP TABLE IF EXISTS _repfailuretest4;
CREATE TABLE _repfailuretest4 (
dt1 DATETIME,
dt2 DATETIME
)ENGINE=INNODB ROW_FORMAT=COMPACT;
INSERT INTO _repfailuretest4 VALUES ('2018-03-27 00:00:00', '2018-03-28 00:00:00');

180327 14:54:01 [ERROR] Slave SQL: Column 0 of table 'entdata_utf8._repfailuretest4' cannot be converted from type '<unknown type>' to type 'datetime', Error_code: 1677
180327 14:54:01 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.004139' position 730736627

xref https://bugs.mysql.com/bug.php?id=70124 where it is discussed that something like this symptom is resolvable under MySQL 5.6.20 using certain slave_type_conversions values, but I am unable to determine if/how this applies to MariaDB versions, and/or if a particular slave_type_conversions value would help my case.



 Comments   
Comment by Elena Stepanova [ 2018-03-27 ]

In general, replication from a newer master to an older slave, while might be possible in some cases, is not supported either in MariaDB or in MySQL.

If you still want to try to set it up, you can experiment with mysql56_temporal_format variable, it might help, although it's in a no way a guarantee.

Generated at Thu Feb 08 08:23:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.