[destination-postgres] custom `connectTimeout` JDBC parameter does not override the default timeout

airbytehq / airbyte

The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.

https://airbyte.com

Other

15.78k stars 4.04k forks source link

[destination-postgres] custom `connectTimeout` JDBC parameter does not override the default timeout #35402

Open alvinwanyeki opened 7 months ago

alvinwanyeki commented 7 months ago

Connector Name

destination-postgres

Connector Version

2.0.0

What step the error happened?

Configuring a new connector

Relevant information

Specifying the connectTimeout JDBC URL parameter on the connector config does not override the default timeout of 60 seconds.

CleanShot 2024-02-19 at 08 36 19@2x

Relevant log output

No response

Contribute

[ ] Yes, I want to contribute

stephane-airbyte commented 4 months ago

there's a CDK refactor that happened in sources but not in destinations. That should allow to fix this

alvinwanyeki commented 4 months ago

@stephane-airbyte -- to confirm, has the refactor happened on destinations yet?

asking because, i've noticed that our syncs have not been timing out over the past couple of days yet i couldn't find a change related to this on the destination-postgres' release notes.

stephane-airbyte commented 4 months ago

No, the refactor didn't happen yet