Bug #74192 Setup of the MySQL Fabric backing store fails with utf8
Submitted: 2 Oct 2014 12:30 Modified: 17 Oct 2014 2:28
Reporter: CEDRIC PEINTRE Email Updates:
Status: Closed Impact on me:
Category:MySQL Fabric Severity:S3 (Non-critical)
Version:1.5.2 OS:Linux
Assigned to: CPU Architecture:Any
Tags: fabric

[2 Oct 2014 12:30] CEDRIC PEINTRE
Setup the MySQL Fabric backing store seems to be problem when the target MySQL instance use utf8 as default character set.

An error occurs in this case during the installation process: 1071 (42000): Specified key was too long; max key length is 767 bytes.

How to repeat:
MySQL configuration file parameters:
character_set_server     = utf8

# mysqlfabric manage setup
[INFO] 1412252749.325265 - MainThread - Initializing persister: user (fabric), server (localhost:3306), database (fabric).
Error: Command (CREATE TABLE providers (provider_id VARCHAR(256) NOT NULL, type INT NOT NULL, username VARCHAR(100) NOT NULL, password VARCHAR(128) NOT NULL, url VARCHAR(256) NOT NULL, tenant VARCHAR(100) NOT NULL, default_image VARCHAR(256), default_flavor VARCHAR(256), CONSTRAINT pk_provider_id PRIMARY KEY (provider_id)), ()) failed accessing (localhost:3306). 1071 (42000): Specified key was too long; max key length is 767 bytes.

Suggested fix:
Setting the character set in the table creation order.
[2 Oct 2014 13:22] Peter Laursen
IMO the option "skip-character-set-client-handshake" is crap and should have been deprecated and removed long time ago.

Besides I don't want to comment on the Fabric.

- Peter
- not a MySQL/Oracle eprson
[2 Oct 2014 13:39] CEDRIC PEINTRE
Probably: "this makes MySQL behave like MySQL 4.0"
[9 Oct 2014 7:59] Mats Kindahl
Thank you for the bug report! Verified as described.
[11 Oct 2014 8:42] Alfranio Correia
Draft of patch

Attachment: mysql-bug-74192.diff (text/x-patch), 6.49 KiB.

[11 Oct 2014 8:45] Alfranio Correia
To circumvent this issue, please, use a non-unicode character set or apply the patch above http://bugs.mysql.com/file.php?id=21851&bug_id=74192.

We are working on fixing this issue asap.

Sorry for the inconvenience.
[17 Oct 2014 2:28] Philip Olson
Posted by developer:
Fixed as of the upcoming MySQL Utilities 1.5.3 release, and here's the changelog entry:

Setting up a MySQL Fabric backing store would fail when the target MySQL
instance used a unicode character set as the default.

Thank you for the bug report.