MySQL Bugs: #57360: mysql cluster >= 7.0 ignores max

Bug #57360	mysql cluster >= 7.0 ignores max_rows argument to create-table
Submitted:	11 Oct 2010 6:35	Modified:	12 Oct 2010 15:58
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
$subject

max_rows is a (ugly) way to specify that you want to have more fragments
per node than default. This is necessary to enable multi threaded ordered index
build.

This code was incorrectly merged from 6.3 to 7.0

How to repeat:
.

Suggested fix:
.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/120462

3845 Jonas Oreland	2010-10-11
      ndb - bug#57360 - readd max_rows hack

Pushed into mysql-5.1-telco-7.0 5.1.47-ndb-7.0.20 (revid:jonas@mysql.com-20101011064837-t9mg46riaoj35k0f) (version source revid:jonas@mysql.com-20101011064837-t9mg46riaoj35k0f) (merge vers: 5.1.47-ndb-7.0.20) (pib:21)

pushed to 7.0.20 and 7.1.9

Documented bugfix as follows in the NDB-7.0.20 and 7.1.9 changelogs:

      The MAX_ROWS option for CREATE TABLE was ignored, which 
      meant that it was not possible to enable multi-threaded 
      building of indexes.

Also added warning about this issue to info about MAX_ROWS + NDB at http://dev.mysql.com/doc/refman/5.1/en/create-table.html.

Closed.