Summary
After upgrading Airbyte cluster on Kubernetes from 0.63.11 to 1.2.0 and then downgrading back to 0.63.11, encountering an ‘Internal Server Error’ related to a SQL query. User is seeking guidance on potential schema changes in the Airbyte repository.
Question
Hi friends
I am having an issue with my airbyte cluster deployed on kubernetes. I had 0.63.11 deployed which was working and wanted to upgrade to 1.2.0 - managed to deploy 1.2.0 but had some issues so now trying to redeploy back 0.63.11. I could redeploy 0.63.11 successfully via helm but when I launch the UI, I am now seeing the following error:
"message": "Internal Server Error: SQL [select * from \"public\".\"user\" left outer join \"public\".\"auth_user\" on \"public\".\"user\".\"id\" = \"public\".\"auth_user\".\"user_id\" where \"public\".\"user\".\"id\" = cast(? as uuid)]; Error while reading field: \"public\".\"user\".\"updated_at\", at JDBC index: 11",
"exceptionClassName": "org.jooq.exception.DataAccessException",
"exceptionStack": [
"org.jooq.exception.DataAccessException: SQL [select * from \"public\".\"user\" left outer join \"public\".\"auth_user\" on \"public\".\"user\".\"id\" = \"public\".\"auth_user\".\"user_id\" where \"public\".\"user\".\"id\" = cast(? as uuid)]; Error while reading field: \"public\".\"user\".\"updated_at\", at JDBC index: 11",
"\tat org.jooq_3.19.7.POSTGRES.debug(Unknown Source)",
"\tat org.jooq_3.19.7.POSTGRES.debug(Unknown Source)",
[...]```
Any idea on how I can get around this issue?
Is there a schema change applied on deployment on the postgres db tied to my deployment?
If so where can I find it in the airbyte repo so that I can fix my DB manually?
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1732526337697119) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["airbyte-cluster", "kubernetes", "upgrade", "downgrade", "internal-server-error", "sql-query", "schema-change", "postgres-db"]
</sub>