Bug #37913 in ndb cluster not dump auto_increment info
Submitted: 7 Jul 2008 6:28 Modified: 21 Jul 2009 8:55
Reporter: ws lee Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.2, *-6.3, *-7.0 OS:Solaris
Assigned to: CPU Architecture:Any
Tags: ndb 6.2.15

[7 Jul 2008 6:28] ws lee 
Description:
In ndb cluster not dump auto_increment info.

How to repeat:
table t1, t2 is same table definition and have same data.
only table type not same.
t1 is ndb , t2 is myisam.

# mysqldump -uroot -p test t1 t2 > test.dmp
# more test.dmp

...
...

CREATE TABLE `t1` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `command` text,
  PRIMARY KEY (`id`)
) ENGINE=ndbcluster DEFAULT CHARSET=utf8;

...
...
...

CREATE TABLE `t2` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `command` text,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM AUTO_INCREMENT=916950 DEFAULT CHARSET=utf8;

...
...

like to upper, only ndb table not dump AUTO_INCREMENT=916950  info.
[7 Jul 2008 12:27] Hartmut Holzgraefe 
mysqltest test case

Attachment: bug39713.tgz (application/x-gtar, text), 942 bytes.
[1 Jun 2009 13:46] Jonathan Miller 
Can you produce a test case that shows this acts wrong according to documentation?
[1 Jul 2009 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[2 Jul 2009 0:23] ws lee 
this bug was not patched in new version ndb 6.3.24 yet.
maybe ndb 7.0.6 wiil same.
[21 Jul 2009 8:55] Hartmut Holzgraefe 
Still reproducible with ndb-7.0.6 with the provided test case