Amazon AWS RDS Aurora Row size too large (VB5)

We're trying to import our vbulletin 5 database into RDS/Aurora and getting this:


ERROR 1118 (42000) at line 5733: Row size too large (> 8126). Changing
some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or
ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of
768 bytes is stored inline.

Here is the table structure for the insert that is failing:

``
DROP TABLE IF EXISTS language;
/!40101 SET @saved_cs_client = @@character_set_client /;
/!40101 SET character_set_client = utf8 /;
CREATE TABLE language (
languageid smallint(5) unsigned NOT NULL AUTO_INCREMENT,
title varchar(50) NOT NULL DEFAULT '',
userselect smallint(5) unsigned NOT NULL DEFAULT '1',
options smallint(5) unsigned NOT NULL DEFAULT '1',
languagecode varchar(12) NOT NULL DEFAULT '',
charset varchar(15) NOT NULL DEFAULT '',
imagesoverride varchar(150) NOT NULL DEFAULT '',
dateoverride varchar(50) NOT NULL DEFAULT '',
timeoverride varchar(50) NOT NULL DEFAULT '',
registereddateoverride varchar(50) NOT NULL DEFAULT '',
calformat1override varchar(50) NOT NULL DEFAULT '',
calformat2override varchar(50) NOT NULL DEFAULT '',
logdateoverride varchar(50) NOT NULL DEFAULT '',
locale varchar(20) NOT NULL DEFAULT '',
decimalsep char(1) NOT NULL DEFAULT '.',
thousandsep char(1) NOT NULL DEFAULT ',',
phrasegroup_global mediumtext,
phrasegroup_cpglobal mediumtext,
phrasegroup_cppermission mediumtext,
phrasegroup_forum mediumtext,
phrasegroup_calendar mediumtext,
phrasegroup_attachment_image mediumtext,
phrasegroup_style mediumtext,
phrasegroup_logging mediumtext,
phrasegroup_cphome mediumtext,
phrasegroup_promotion mediumtext,
phrasegroup_user mediumtext,
phrasegroup_help_faq mediumtext,
phrasegroup_sql mediumtext,
phrasegroup_subscription mediumtext,
phrasegroup_language mediumtext,
phrasegroup_bbcode mediumtext,
phrasegroup_stats` mediumtext,

Well, after researching into this and trying out around 20-30 possibly solutions I could not make it work and as far as I can see the limits are set in Aurora and can NOT be changed. Hence the import fails in every single possible solution.

I killed the Aurora instance and created a MySQL one, imported without any hiccups right away. The import or log size limit is set to a much higher default and doesn't choke on the data. Amazon was quoted to say that in Aurora they will not, so far, ever change the limits on this in Aurora. On the other side in MySQL they made it a editable parameter some time ago with, as I said above, already much higher limit.

TLDR: Aurora will always crap out on you with too large fields no matter what field type you set - use RDS MySQL.

StackExchange Database Administrators Q#112526, answer score: 3