[destination-postgres] New destination connector with image airbyte/postgres-destination but different registry doesn't work #54691
Labels
area/connectors
Connector related issues
autoteam
community
needs-triage
team/extensibility
type/bug
Something isn't working
Connector Name
destination-postgres
Connector Version
2.4.0
What step the error happened?
During the sync
Relevant information
I am using Airbyte 1.1.0 in EKS and is deployed using Helm.
Due to company requirements I have to use ECR as image registry. I have pulled the official airbyte/postgres-destination:2.4.0 from docker hub and then pushed it to a private ECR repository.
I have created a new destination connector using the UI (Settings > Destinations > + New Connector) using the image from the ECR repository and the tag 2.4.0 -- Note: I tried with 2.4.3 with same results.
All the tests after creation pass, but at the time of creating a new connection and performing the sync, the job fails and requests to downgrade the connector version or upgrade Airbyte to 0.63.7. When using th built-in connector with same version I don't get the error.
Looking into the Airbyte database, the supports_refreshes column for my custom connector is False, while the built-in is True.
SELECT *
FROM actor_definition_version
WHERE actor_definition_id IN (
SELECT id
FROM actor_definition
WHERE name ilike '%postgres%' and actor_type = 'destination'
);"
Please, am I doing something wrong when creating the connector or is this a bug?
Relevant log output
Contribute
The text was updated successfully, but these errors were encountered: