[MDEV-8398] Minimal/NOBLOB Binlog Row Image replication fails when tables from master have different PK in slave Created: 2015-06-30  Updated: 2022-01-18

Status: Open
Project: MariaDB Server
Component/s: Events, Replication
Affects Version/s: 10.1
Fix Version/s: 10.1

Type: Bug Priority: Major
Reporter: Vicențiu Ciorbaru Assignee: Vicențiu Ciorbaru
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-6877 Merge binlog_row_image from MySQL 5.6 Closed
Sprint: 10.1.9-1, 10.1.9-2, 10.1.9-3, 10.1.15

 Description   

Replication fails when using minimal/noblob binlog row image and indexes.

Attempting to update a row causes the replication of the slave to fail with HA_ERR_KEY_NOT_FOUND.



 Comments   
Comment by Vicențiu Ciorbaru [ 2015-06-30 ]

CC elenst. There are some testsuites in MySQL that fail with out implementation. Example: rpl.rpl_row_img_idx_noblob. I have not yet ported these to MariaDB but once I fix them, we'll have all of them in. This is just so you know, in case you begin testing binlog_row_image.

Comment by Rasmus Johansson (Inactive) [ 2016-06-22 ]

cvicentiu, Monty told me that you could take over this and that he hasn't done anything on it so far.

Generated at Thu Feb 08 07:26:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.