[
https://issues.apache.org/jira/browse/BEAM-12993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441860#comment-17441860
]
Beam JIRA Bot commented on BEAM-12993:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> DebeziumIO cannot connect to cloud Postgres instances
> -----------------------------------------------------
>
> Key: BEAM-12993
> URL: https://issues.apache.org/jira/browse/BEAM-12993
> Project: Beam
> Issue Type: Bug
> Components: dependencies, io-java-debezium
> Affects Versions: 2.32.0
> Reporter: Judah
> Assignee: Judah
> Priority: P2
> Labels: stale-assigned
> Time Spent: 4h
> Remaining Estimate: 0h
>
> I identified the other day that Debezium does not work with many cloud
> providers Postgres instances. This includes Azure and Google CloudSQL. I
> determined that this is due to the version of Postgres JDBC that Debezium
> uses (42.2.14).
>
> I've been working with the Debezium devs to update this dependency to
> 42.2.22 which should solve the connection problems. This dependency update
> was released today in Debezium 1.7.0.Final.
>
> See:
> [https://issues.redhat.com/browse/DBZ-4060]
> [https://github.com/pgjdbc/pgjdbc/issues/1868]
>
> However, this means that for the DebeziumIO connector dependency in Apache
> Beam will also need updating. Is this something which people will be happy
> with?
>
> Is it something which could likely be included in the next Beam release?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
