[
https://issues.apache.org/jira/browse/BEAM-12993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474815#comment-17474815
]
Beam JIRA Bot commented on BEAM-12993:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: stale-P2
> 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)
