MySQL Bugs: #55799: main.ctype_utf8mb4_ndb and other NDB tests fail in 5.5

Bug #55799	main.ctype_utf8mb4_ndb and other NDB tests fail in 5.5
Submitted:	6 Aug 2010 10:21	Modified:	17 Dec 2011 17:55
Reporter:	Konstantin Osipov (OCA)	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.5+	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	5.5+, disabled

Description:
As part of the fix for Bug#41158, all storage engine calls are 
done outside LOCK_open. This broke auto-discovery, which expects
to be called with LOCK_open. Thus auto-discovery, which 
currently only works in NDB, was disabled. 
As a result, main.ctype_utf8mb4_ndb test and potentially
all other NDB tests started to fail.

This is done per agreement with NDB, since we need a new
discovery algorithm in 5.5 and on, that doesn't require LOCK_open.
The old algorithm was broken since it was implemented and could
not work with the new MDL, which added a number of new asserts
to guard against violations of the locking protocol.

See also Bug#51907, but this bug is different, since
a) It disables the tests
b) It is to signify that *all* ndb tests are affected.

How to repeat:
Try to run main.ctype_utf8mb4_ndb in 5.5.

Suggested fix:
Instead of one handlerton call that attempts to find a table and create an .frm
for it, implement ha_table_exists_in_engine(), that would check if a table
exists in some engine, and another, ha_create_table_from_engine(), that would
create an .frm for the table.
Alternatively, fix all MySQL DDL operations to not require an .frm
to work, and use the new discovery interface from WL#5308 Plugin API; Allow a storage engine to provide tables without using FRM files to discover files.

Thank you for the report.

Which tree should I use to get this test failed? It does not fail for me in mysql-trunk, mysql-trunk-bugfixing and mysql-next-mr

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".

Use mysql-trunk, please.

I do not see this test neither in 5.5.20, nor in mysql-trunk (5.6.5) any more.