New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail during upgrade from 48.3 to 49.7 #41924
Comments
@qnkhuat tagging you as you might be more familiar with the matter here |
@paoliniluis this scope has been moved to another team, and @qnkhuat is OOO anyway. |
about the same error here, upgrading from v0.48.7 to v0.49.8:
|
Similar failure here:
@mmoole were you able ever to find a solution? I'm not certain that a downgrade is a viable supported solution so I hesitant to move back versions. |
I immediately retried the upgrade with v0.49.10 when it was available, and it gut stuck at the migration tasks. Restarting metabase didn't help: it complained about migration lock being present in the database. |
@mmoole thank you! I'll see if this will work in my case. Also, I just looked through some closed issues and saw that this issue may be resolved in 49.11 |
@ZencareJake try with 49.11, your db details are encrypted and that might be the issue here |
@darksciencebase should we close this? I don't know if we tackled this at some point |
we didn't fix the issue with json extract limit. |
I didn't specify in my original comment that those logs were from an attempt to initialize Edit: I realized that you're suggesting I should try with the fix coming up in 49.11, I will do that! Thank you! |
@ZencareJake you're right, 49.11 is not out yet, but is expected to be released today. |
Describe the bug
Hello! We use Metabase 0.48.3 with MariaDB 10.5 and have tried to update to the 0.49.7 version. During the updating process we got the migration error:
Limit of 32 on JSON nested strucures depth is reached in argument 1 to function 'json_extract'
.As i got right the error refer to MariaDB. We found several issues with such problem:
https://jira.mariadb.org/browse/MDEV-30343
https://jira.mariadb.org/browse/MDEV-33437
In the new version of MariaDB this problem can be solved by new parameter - https://jira.mariadb.org/browse/MDEV-32854.
But the documentation says MariaDB 10.2 supported and migration process should be done without errors.
To Reproduce
Try to update the Metabase from 48.3 to 49.7.
Expected behavior
Migrations should be done without errors.
Logs
Information about your Metabase installation
Severity
This blocks the use of the new version of Metabase
Additional context
No response
The text was updated successfully, but these errors were encountered: