Bug #25295 | ALTER TABLE operations for NDB tables require inclusion of ENGINE=ndbcluster. | ||
---|---|---|---|
Submitted: | 27 Dec 2006 18:03 | Modified: | 6 Jul 2007 9:34 |
Reporter: | Matthew Montgomery | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Cluster: Disk Data | Severity: | S3 (Non-critical) |
Version: | 5.1.14 | OS: | Linux (Linux 2.6) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | alter, cluster, disk, engine, Memory, storage |
[27 Dec 2006 18:03]
Matthew Montgomery
[30 Jan 2007 6:09]
Bugs System
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/19002 ChangeSet@1.2343, 2007-01-11 17:46:23+08:00, Justin.He@dev3-240.dev.cn.tlan +2 -0 BUG#25295, ALTER TABLE operations for NDB tables require inclusion of ENGINE=ndbcluster
[13 Mar 2007 10:07]
Bugs System
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/21788 ChangeSet@1.2444, 2007-03-13 18:00:59+08:00, Justin.He@dev3-240.dev.cn.tlan +1 -0 Bug#25295, ALTER TABLE operations for NDB tables require inclusion of ENGINE=ndbcluster. this patch of bug25295 depends on bug25877 and bug25880
[7 Apr 2007 7:00]
Bugs System
Pushed into 5.1.18-beta
[10 Apr 2007 11:38]
Jon Stephens
mysql> ALTER TABLESPACE ts_1 ADD DATAFILE 'data_2.dat' INITIAL_SIZE 48M; Query OK, 0 rows affected, 1 warning (0.00 sec) mysql> show warnings; +-------+------+------------------------------------------------------------------------------------------------+ | Level | Code | Message | +-------+------+------------------------------------------------------------------------------------------------+ | Error | 1466 | Table storage engine 'MyISAM' does not support the create option 'TABLESPACE or LOGFILE GROUP' | +-------+------+------------------------------------------------------------------------------------------------+ 1 row in set (0.00 sec) Result: "Query OK" and a warning, but no data file is not created. This is IMO very, very wrong. The statement should be reported as successful *only* if the data file is created and associated with the tablespace. One of two things should happen: 1. The statement should clearly *fail* with an *error* (and not a warning), since the storage engine was not specified. 2. The statement should succeed with no warnings or errors (and the data file should be created), due to the fact that tablespace ts_1 is already associated with the NDB storage engine.
[13 Mar 2014 13:35]
Omer Barnir
This bug is not scheduled to be fixed at this time.