Bug #52061 MySQL Cluster docs : Wrong parameter effect description
Submitted: 15 Mar 2010 10:36 Modified: 17 Mar 2010 15:02
Reporter: Frazer Clement Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:mysql-5.1 OS:Any
Assigned to: Jon Stephens CPU Architecture:Any
Tags: --ndb-log-update-as-write

[15 Mar 2010 10:36] Frazer Clement
Description:
http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-replication-issues.html

"Replication from NDB to a nontransactional storage engine.   When replicating from NDB to a nontransactional storage engine such as MyISAM, you may encounter unnecessary duplicate key errors when replicating INSERT ... ON DUPLICATE KEY UPDATE statements. You can suppress these in MySQL Cluster NDB 6.2 by using --ndb-log-update-as-write=0, which forces all columns from updated rows to be sent (and not just those that were updated). For MySQL Cluster NDB 6.3.3 and later, there are additional way to determine whether or not an update to the row on the master should be applied on the slave mysqld; see Section 17.6.11, “MySQL Cluster Replication Conflict Resolution”, for more information about these methods."

Specifically :
"by using --ndb-log-update-as-write=0, which forces all columns from updated rows to be sent (and not just those that were updated)"

The ndb-log-update-as-write option controls whether updates are logged as WRITE_ROW or UPDATE_ROW events in the Binlog.

There is a separate option ndb-log-updated-only that controls whether only updated, or all columns are written to the Binlog.

How to repeat:
Cross check parameter descriptions.

Suggested fix:
Put correct description of ndb-log-update-as-write in the paragraph.
[16 Mar 2010 21:15] Jon Stephens
Corrected status/lead.
[17 Mar 2010 15:02] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.