Bug #20168 Change in behavior --default-storage-engine=ndb or ndbcluster

Description:
In the last month or so we have had a change in behavior where --default-storage-engine= is concerned.

Use to you could use either ndb of ndbcluster. Now if you try and use ndb you get back "Unknown/unsupported table type: NDB". This is breaking Alcatel. 

How to repeat:
start mysqld with --default-storage-engine=ndb

Suggested fix:
Allow either ndb or ndbcluster to be used.

both ndb and ndbcluster should be valid specification of storage engine in all cases

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

I have a similar problem with default_storage_engine.

I used to set
  default_storag_engine =  InnoDB
in my.cnf. It set the default engine to InnoDB.

5.0.19-debug
[21:31] root@test>show engines;
+------------+---------+----------------------------------------------------------------+
| Engine     | Support | Comment                                                        |
+------------+---------+----------------------------------------------------------------+
| MyISAM     | YES     | Default engine as of MySQL 3.23 with great performance         |
| MEMORY     | YES     | Hash based, stored in memory, useful for temporary tables      |
| InnoDB     | DEFAULT | Supports transactions, row-level locking, and foreign keys     |

However, in 5.1.12 it is not the case anymore. 

5.1.12-beta-debug-log
[21:31] root@(none)>show engines;
+------------+----------+----------------------------------------------------------------+--------------+-----+------------+
| Engine     | Support  | Comment                                                        | Transactions | XA  | Savepoints |
+------------+----------+----------------------------------------------------------------+--------------+-----+------------+
| EXAMPLE    | YES      | Example storage engine                                         | NO           | NO  | NO         |
| MRG_MYISAM | YES      | Collection of identical MyISAM tables                          | NO           | NO  | NO         |
| BerkeleyDB | YES      | Supports transactions and page-level locking                   | YES          | NO  | YES        |
| BLACKHOLE  | YES      | /dev/null storage engine (anything you write to it disappears) | NO           | NO  | NO         |
| FEDERATED  | YES      | Federated MySQL storage engine                                 | YES          | NO  | NO         |
| InnoDB     | YES      | Supports transactions, row-level locking, and foreign keys     | YES          | YES | YES        |
| ARCHIVE    | YES      | Archive storage engine                                         | NO           | NO  | NO         |
| CSV        | YES      | CSV storage engine                                             | NO           | NO  | NO         |
| MyISAM     | DEFAULT  | Default engine as of MySQL 3.23 with great performance         | NO           | NO  | NO         |
| MEMORY     | YES      | Hash based, stored in memory, useful for temporary tables      | NO           | NO  | NO         |
| ndbcluster | DISABLED | Clustered, fault-tolerant tables                               | YES          | NO  | NO         |
+------------+----------+----------------------------------------------------------------+--------------+-----+------------+
11 rows in set (0.00 sec)

lmy001:~ # grep default_storage /etc/my.cnf
default_storage_engine=InnoDB

Regards, Hakan

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

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

Pushed to 5.1.12-beta repository

Noted in 5.1.12 changelog.

The --default-storage-engine server option did not work.