Bug #47228 Incorrect conducting or loading binary logs

Description:
At restoring from binary logs on ndbcluster engine if in the table it is used "UNIQUE KEY" the data load incorrectly.

How to repeat:
mysql>  CREATE TABLE `testndb`( `id` int(11) NOT NULL DEFAULT '0',
`name` varchar(32) DEFAULT NULL, `name2` varchar(32) DEFAULT NULL,
`number` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `number` (`number`) ) ENGINE=ndbcluster DEFAULT CHARSET=latin1;

mysql> insert into test.testndb set id=1,name='ivan',name2='ivanov',number=10;
Query OK, 1 row affected (0.02 sec)                                           

mysql> update test.testndb set number=20 where id=1;
Query OK, 1 row affected (0.00 sec)                 
Rows matched: 1  Changed: 1  Warnings: 0            

mysqlbinlog mysql-bin.000001 > load.sql

mysql> delete from test.testndb;
Query OK, 1 row affected (0.00 sec)

mysql> \. ./load.sql
ERROR 1062 (23000): Duplicate entry '1' for key 'PRIMARY'

Suggested fix:
not known

Thank you for the report.

Verified as described.

To repeat one needs to follow instructions manually. If issue same statements using MTR I get no error, but table is not updated same time.

Здравствуйте!
Мы можем как-нибудь помочь решению данной проблемы?
Наша база данных содержит множество уникальных ключей, поэтому мы крайне заинтересованы в скорейшем ее исправлении.

Ivan,

thank you for the feedback.

But this bug database is used by people from different countries, so English is official language and is only language which should be used here.

We will ask you for additional information if such information would be needed to fix the bug.