[
https://issues.apache.org/jira/browse/BEAM-12993?focusedWorklogId=662973&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-662973
]
ASF GitHub Bot logged work on BEAM-12993:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Oct/21 20:52
Start Date: 08/Oct/21 20:52
Worklog Time Spent: 10m
Work Description: ibzib commented on pull request #15689:
URL: https://github.com/apache/beam/pull/15689#issuecomment-939109179
Run Java_Examples_Dataflow PreCommit
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 662973)
Time Spent: 3h 20m (was: 3h 10m)
> 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
> Time Spent: 3h 20m
> 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.3.4#803005)
