Internal Server Error when Upgrading Airbyte and Testing Connectors

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

The error message indicates an Internal Server Error related to a null value in a column ‘default_version_id’ of the ‘actor’ relation, violating a not-null constraint. This occurred after upgrading Airbyte from version 0.50.7 to 0.50.33 and testing connectors.


Question

"event": "response content is:
b'{\"message\":\"Internal Server Error: SQL [insert into \\\\\"public\\\\\".\\\\\"actor\\\\\"
(\\\\\"id\\\\\", \\\\\"workspace_id\\\\\", \\\\\"actor_definition_id\\\\\",
\\\\\"name\\\\\", \\\\\"configuration\\\\\", \\\\\"actor_type\\\\\", \\\\\"tombstone\\\\\", \\\\\"created_at\\\\\", \\\\\"updated_at\\\\\") values
(cast(? as uuid), cast(? as uuid), cast(? as uuid), ?, cast(? as jsonb), cast(?
as \\\\\"public\\\\\".\\\\\"actor_type\\\\\"),
?, cast(? as timestamp(6) with time zone), cast(? as timestamp(6) with time
zone))]; ERROR: null value in column \\\\\"default_version_id\\\\\"
of relation \\\\\"actor\\\\\" violates
not-null constraint\\\\n Detail: Failing row contain

Above errors are showing when we upgraded Airbyte from 0.50.7 to 0.50.33 and testing connectors


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["internal-server-error", "upgrading", "airbyte", "testing-connectors", "null-value", "not-null-constraint"]
2

Based on the information provided in the extracts, it seems like you’re encountering an error related to a null value in the “default_version_id” column of the “actor” relation in your database. This error is occurring after upgrading Airbyte from version 0.50.7 to 0.50.33 and testing connectors. However, the extracts do not provide a direct solution or workaround for this specific issue. It’s possible that this could be a bug or an issue with the upgrade process. In a similar situation mentioned in the extract from Github Issue 28314, a user faced issues with upgrading Source Connectors after upgrading Airbyte. They were able to resolve the issue by running docker-compose down and docker-compose up again. However, this may not directly apply to your situation as the error messages are different. I would recommend reaching out to the Airbyte community on their discussion forum or Github for more specific assistance.