I need to use it via the Python `ReadFromDebezium` interface which makes that more tricky as it just goes and fetches the prebuilt jar.
On Fri, 1 Oct 2021, 19:26 Luke Cwik, <lc...@google.com> wrote: > Based upon the PR, it doesn't look like there were any code changes. Would > overriding the debezium version in your application to 1.7 solve the issue? > > On Fri, Oct 1, 2021 at 10:08 AM Judah Rand <judah.r...@thread.com> wrote: > >> I was wondering if there might be any possibility of cherry-picking the >> changes from https://github.com/apache/beam/pull/15636 into the 2.33.0 >> release for next week? >> >> Currently DebeziumIO is completely unusable for both Azure and Google >> CloudSQL Postgres instances due to a bug in the Postgres JDBC driver which >> has only recently been updated in Debezium. >> >> I’m currently completely blocked from using Beam for our intended use >> case. >> >> Appreciate it’s probably quite late in the day for changes but >> consideration would be appreciated. >> >> On 2021/09/21 17:32:40, Udi Meiri <u...@apache.org> wrote: >> > Hi everyone,> >> > Please review and vote on the release candidate #1 for the version >> 2.33.0,> >> > as follows:> >> > [ ] +1, Approve the release> >> > [ ] -1, Do not approve the release (please provide specific comments)> >> > >> > >> > Reviewers are encouraged to test their own use cases with the release> >> > candidate, and vote +1 if> >> > no issues are found.> >> > >> > The complete staging area is available for your review, which >> includes:> >> > * JIRA release notes [1],> >> > * the official Apache source release to be deployed to dist.apache.org >> [2],> >> > which is signed with the key with fingerprint 587B049C36DAAFE6 [3],> >> > * all artifacts to be deployed to the Maven Central Repository [4],> >> > * source code tag "v2.33.0-RC1" [5],> >> > * website pull request listing the release [6], the blog post [6], and> >> > publishing the API reference manual [7].> >> > * Java artifacts were built with Maven 3.6.3 and OpenJDK 1.8.0_181.> >> > * Python artifacts are deployed along with the source release to the> >> > dist.apache.org [2] and pypy[8].> >> > * Validation sheet with a tab for 2.33.0 release to help with >> validation> >> > [9].> >> > * Docker images published to Docker Hub [10].> >> > >> > The vote will be open for at least 72 hours. It is adopted by majority> >> > approval, with at least 3 PMC affirmative votes.> >> > >> > For guidelines on how to try the release in your projects, check out >> our> >> > blog post at https://beam.apache.org/blog/validate-beam-release/.> >> > >> > Thanks,> >> > Release Manager> >> > >> > [1]> >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12350404> >> >> > [2] https://dist.apache.org/repos/dist/dev/beam/2.33.0/> >> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS> >> > [4] >> https://repository.apache.org/content/repositories/orgapachebeam-1234/> >> > [5] https://github.com/apache/beam/tree/v2.33.0-RC1> >> > [6] https://github.com/apache/beam/pull/15543> >> > [7] https://github.com/apache/beam-site/pull/619> >> > [8] https://pypi.org/project/apache-beam/2.33.0rc1/> >> > [9]> >> > >> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1705275493> >> >> > [10] https://hub.docker.com/search?q=apache%2Fbeam&type=image> >> > > >
