Issue while Upgrading to 3.2

Hello ,

I have come across a situation where my up gradation from 0.31.2 to 32.0 in the aws staging/testing environment works fine which is the same replication of Production , when i am trying to do it same in the AWS production environment , my jar initialization
is getting failed by giving the error “n.data is undefined” .

Below are the My Environment details
AWS Staging Environment
Deployment : By running Jar
OS : Centos 8
Version of Metabase : 0.32
Application database : Maria DB

AWS Prod Environment
Deployment : By running Jar
OS : Centos 8
Version of Metabase : 0.32
Application database : Maria DB

Please help me on this

Hi @sushant.naik

It sounds like your production and staging environment doesn’t match.
You might want to duplicate your production to a new staging, and remove the old staging.

It is not recommended to upgrade from 0.31.2 to 0.32.0 - upgrade to 0.32.5

And where does that error n.data is undefined show? What errors do you see in the log?

hello @flamber,

Thanks for the suggestion  and i am doing it.

Ya , sure i will take the latest release while upgrading :slight_smile:
I am getting this error while accessing query_execution table .
Sorry for the wrong information , i am able to start the jar but the issue with query_execution table.
i am not able to access the query_execution , i get “n.data is undefined” in the log.

If you’re having issues with accessing a table, then it sounds like the problem is with MariaDB.
I have never seen that error before and without more information/logs, then I cannot help.

Oh okay …
ya sure i will come back with the more detail about the logs.