error in azure mysql when installing container gateway on AKS

[Johan Velde]

Hello,

We are trying to install the container gateway (10.0) on azure kubernetes. The install using the integrated mysql container has succeeded. As a next step, we would like to use azure mysql as an external database. We have set the configuration options in the HELM values.yml as follows:

database:
# DB Backed or ephemeral
enabled: true
# A MySQL Database is configured with this Chart, set to false and set jdbcURL to use your own DB server
create: false
jdbcURL: jdbc:mysql://xxxxxxxxx.mysql.database.azure.com:3306/ssg?useSSL=true&requireSSL=true&verifyServerCertificate=false
# Configurable, update the mysql.auth.<settings> if you change this and would like to use the demo database server.
username: xxxxxxxx
password: xxxxxxxx
name: ssg

Unfortunately, the deploy results in an error:

Unexpected error running Liquibase: Error executing SQL CREATE TABLE ssg.resource_entry (goid BINARY(16) NOT NULL, version INT(10) NOT NULL, description VARCHAR(2048) NULL, uri VARCHAR(4096) NOT NULL, uri_hash VARCHAR(128) NOT NULL, type VARCHAR(32) NOT NULL, content_type VARCHAR(1024) NOT NULL, content MEDIUMTEXT NOT NULL, resource_key1 VARCHAR(4096) NULL, resource_key2 VARCHAR(4096) NULL, resource_key3 VARCHAR(4096) NULL, security_zone_goid BINARY(16) NULL): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

We have tried setting innodDB_strict_mode to off, but this doesn't work. What could be causing this issue?

[Sebastian van Voorn]

I think it is the MEDUIMTEXT definition for row content:
Maximum length for MySQL TEXT field types;

MEDIUMTEXT

16,777,215 bytes

~16MB

this exceeds the maximum row size of 65535

[Johan Velde]

We have found the solution, there is a kb article: https://knowledge.broadcom.com/external/article/227991/api-gateway-container-gateway-deployed.html

This thread can be closed.