mysqldump with generated column doesn't work while importing

[karthikeayan]

I am getting below error when importing mysqldump taken from this docker image.

ERROR 3105 (HY000) at line 82: The value specified for generated column 'column_name' in table 'table_name' is not allowed.

Source and destination mysql server having same version.

MySQL server version:

mysqld Ver 5.7.26 for Linux on x86_64 (MySQL Community Server (GPL))

MySQL Dump client version:

mysqldump Ver 10.17 Distrib 10.3.12-MariaDB, for Linux (x86_64)

[deitch]

@karthikeayan can you run the dump manually off the database and see?

Also, if you run the mysql-backup image with debug enabled - DB_DUMP_DEBUG=true - you should see the mysqldump line. If it is possible to pull that line, post it here (omitting credentials, of course), and then see if we can replicate it? It is likely a version mismatch or some mysqldump bug, but let's figure it out and get it fixed either way.

Also, can you paste the relevant part of the dump output, based on the above, line 82 and its surrounding areas? Again, masking any sensitive info.

[karthikeayan]

I am not sure if this is fixable as this seems an mismatch between mysql and mariadb json functions. Your dockerfile uses alpine and alpine by default install mariadb client not mysql client.

More info: https://dba.stackexchange.com/questions/240880/can-we-use-mariadb-mysqldump-cli-to-take-dump-from-mysql-community-version

I also tried changing the base image to ubuntu in your Dockerfile to take dump. It works with 30MB database but when I use my image on 30GB database, mysqldump was very very slow and after creating 5-6GB of sql file the container got killed.

[deitch]

mismatch between mysql and mariadb json functions

And so it appears. I would be tempted to ask the MariaDB team to fix it (they are pretty good about it), but this just may be a divergence. We may need to have separate mysql and mariadb images then.

It works with 30MB database but when I use my image on 30GB database, mysqldump was very very slow and after creating 5-6GB of sql file the container got killed.

If you can replicate it without using your own sensitive data, can you open a new issue and put in exact steps to replicate?

[deitch]

mismatch between mysql and mariadb json functions

I am curious as to why this hasn't been an issue until now. Do only certain scenarios trigger it? If you look at your dump file, what is it that triggered the problem?

[deitch]

Important reference point: https://elephantdolphin.blogspot.com/2018/11/a-tale-of-two-json-implementations.html

[karthikeayan]

I am just posting the first few characters from the line 82, as the complete line is too huge.

https://gist.github.com/karthikeayan/2f4e18f204786c78ff2874becf6af260

[deitch]

Can you put it in a gist or somewhere we can see it?

[karthikeayan]

Created PR

[prvucetic]

Hey, what's the status of this? I'm facing this issue when try to restore to the same db server I created backup from.

I have the following:

/# mysql --version mysql Ver 8.0.21 for Linux on x86_64 (MySQL Community Server - GPL)

/# mysqldump --version mysqldump Ver 8.0.21 for Linux on x86_64 (MySQL Community Server - GPL)

Tnx

[deitch]

There is a PR open, linked in this issue, needs to be rebased and cleaned.

[ToshY]

@deitch The only thing really needed is to replace mariadb-client in favor for mysql-client.

Submitted a PR, could you take a quick look at it?

[Kirgod]

Still facing with same error :(