On 21/05/14 10:45, Clint Byrum wrote: > Excerpts from Clint Dilks's message of 2014-05-20 14:30:40 -0700: >> Hi, >> >> I seem to be hitting a known issue with HEAT MySQL 5.6 and UTF8 >> >> ERROR: (OperationalError) (1071, 'Specified key was too long; max key >> length is 767 bytes') 'CREATE INDEX ix_software_config_tenant ON >> software_config (tenant)' () >> >> So based off https://bugs.launchpad.net/heat/+bug/1316646 I have made the >> following modifications to the heat database. >> >> mysql> alter table software_config modify column tenant varchar(64) NOT >> NULL; >> >> mysql> CREATE INDEX ix_software_config_tenant ON software_config (tenant); >> >> Is reducing the size of the tenant column likely to cause issues later? > No, in researching the issue, I found that all of these columns should be > varchar(64). I seem to have lost track of the patches though. We should > definitely fix this in juno, since MySQL 5.6 is starting to arrive in > the distros. > Here we go https://review.openstack.org/#/c/92421/2
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
