MySQL Bugs: #47758: MySQL Cluster : logging of all columns for delete rows event

Bug #47758	MySQL Cluster : logging of all columns for delete rows event
Submitted:	1 Oct 2009 9:11	Modified:	11 May 2017 7:13
Reporter:	Frazer Clement	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Cluster: Replication	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-6.2	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
When testing the mysqlbinlog --verbose tool, I noticed a difference in the output for DELETE ROW events between 6.2 and 6.3 +.

In 6.2, DELETE ROW events *always* include just the primary key, e.g.

DELETE FROM test.ba WHERE   @1=2

In 6.3+, DELETE ROW events include just the primary key when ndb_log_updated_only is ON.

When it's off, DELETE ROW events include all columns.  e.g. :

DELETE FROM test.ba WHERE   @1=2   @2=2   @3=2

This could be :
 1) A mysqlbinlog --verbose bug
 2) A real change in behaviour

It's not clear that ndb_log_updated_only is supposed to affect the columns logged for a DELETE, but we should have consistency.

How to repeat:
See mysql-test/suite/ndb_binlog/t/ndb_binlog_variants.test

Suggested fix:
Align 6.2 behaviour with 6.3+.
Document?