Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.1.2
-
Fix Version/s: 10.1.6
-
Component/s: Storage Engine - Mroonga
-
Labels:None
Description
Mroonga doesn't work in 10.1 tree.
In particular, it creates a wrapped InnoDB table using ha_mroonga::wrapper_create() passing down the TABLE_SHARE from the parent Mroonga table. This kinda worked in 10.0, even though it's not strictly correct — for example, share->db_plugin was Mroonga, not InnoDB. In 10.1 it does not work at all. In 10.1 InnoDB uses engine defined table attributes and it expects share->option_struct to be set to a correctly filled option structure. But that TABLE_SHARE was created for Mroonga, it does not have InnoDB-specific options. InnoDB crashes trying to resolve a NULL pointer.
For a correct solution InnoDB needs to get its own TABLE_SHARE object.
May be there will be other issues with Mroonga in 10.1, I don't know, that was the first one that I got.
Gliffy Diagrams
Attachments
Issue Links
- is part of
-
MDEV-8387 10.1.6 merge
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Ah, great. Our current plan is to release 10.1.6 in about 10 days.
Kentoku, if you could merge mroonga into your mariadb repository by then, then we'll merge it into 10.1 for the release as always. But, please, tell what branch to use — I mean, you can merge new mroonga into 10.0 or directly into 10.1 and we need to know what branch to merge from.
FYI: Mroonga 5.04 has been released. It support MariaDB 10.1: http://mroonga.org/docs/news.html#release-5.04
FYI:
Mroonga at master on GitHub supports MariaDB 10.1.
So Mroonga 5.04, will be released at 2015-06-29, supports MariaDB 10.1.