[google-cloud-sql-discuss] Row size too large + innodb_log_file_size flag

Are there any plans to allow the innodb_log_file_size  setting to be changed view the allowed flags?

Currently having trouble importing a database export of MyISAM tables into my Cloud SQL server. When I hit a certain table that has many columns, the import fails with the following error:

MySQL: Error Code: 1118 Row size too large (> 8126). Changing some columns to TEXT or BLOB

Currently it does not seem we can change the innodb_log_file_size flag on Google Cloud SQL and from what I can see that is one of the leading solutions. That is, to update innodb_log_file_size flag according to the MySQL documentation:

As a result of the redo log BLOB write limit introduced for MySQL 5.6, theinnodb_log_file_size setting should be 10 times larger than the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR,VARBINARY, and TEXT type fields). No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data.

Aside from hoping Google Cloud  eventually allows us to update that flag, if anyone has any ideas or suggestions on other ways to remedy this issue it would be greatly appreciated.

Thank you.

-Mike

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/8a852a37-c69c-46e3-93a4-d4c87a460e6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.