MySQL Bugs: #25877: After DROP INDEX non-indexed data isn't moved from memory into tablespace

Bug #25877	After DROP INDEX non-indexed data isn't moved from memory into tablespace
Submitted:	26 Jan 2007 17:37	Modified:	23 Mar 2007 10:31
Reporter:	Serge Kozlov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Disk Data	Severity:	S3 (Non-critical)
Version:	5.1.15-bk	OS:	Linux (Linux FC4 64bit)
Assigned to:	justin he	CPU Architecture:	Any

Description:
There is ndb_dd table with indexed column. The data of this column is in memory. After dropping index on the column the data should be moved into tablespace because there are no reasons to save it in memory. But data remains there...

How to repeat:
1. Create ndb_dd table with additional indexed column:

create table t1 (a int not null auto_increment primary key, b varchar(1), index(
b)) tablespace ts1 storage disk engine=ndb;

2. Put a few rows into table and make sure that they are in memory:

$ ./builds/bin/ndb_select_all --disk -d test t1
a       b
5       a
1       a
2       a
4       a
8       a
7       a
3       a
9       a
10      a
6       a
10 rows returned

NDBT_ProgramExit: 0 - OK

3. Drop index and add one new row.

drop index b on t1;
insert into t1(a,b) values (100, 'z');

4. Repeat step 2:

$ ./builds/bin/ndb_select_all --disk -d test t1
a       b
5       a
1       a
2       a
4       a
8       a
7       a
3       a
9       a
10      a
100     z
6       a
11 rows returned

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/21140

ChangeSet@1.2441, 2007-03-05 19:14:56+08:00, Justin.He@dev3-240.dev.cn.tlan +1 -0
  BUG#25877, After DROP INDEX non-indexed data isn't moved from memory into tablespace

Fixed in 5.1.17

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.17 and ndb-6.1.6 changelogs.