Re: 2.65.0 Branch Cut

Great! Thank you! On Wed, Apr 30, 2025 at 5:40 PM Valentyn Tymofieiev via dev < dev@beam.apache.org> wrote: > Thanks! Good luck with the release. > > On Wed, Apr 30, 2025 at 2:20 PM Yi Hu via dev wrote: > >> Hey everyone, >> >> The Beam 2.65.0 release branch has been cut! There are currently 0 o

Re: 2.65.0 Branch Cut

Thanks! Good luck with the release. On Wed, Apr 30, 2025 at 2:20 PM Yi Hu via dev wrote: > Hey everyone, > > The Beam 2.65.0 release branch has been cut! There are currently 0 open > issues on the milestone . > > I will now start working on stabilizin

2.65.0 Branch Cut

Hey everyone, The Beam 2.65.0 release branch has been cut! There are currently 0 open issues on the milestone . I will now start working on stabilizing the release branch ( https://github.com/apache/beam/tree/release-2.65) and work towards RC1. Thanks

Re: Inquiry About GSoC Project - Beam ML Vector DB/Feature Store Integrations

Hi Danny, I’ve completed the implementation of the OpenAI text embedding handler and have opened a PR for it. Could you please take a look when you get a chance? Thanks, Aditya >

Re: Inquiry About GSoC Project - Beam ML Vector DB/Feature Store Integrations

https://github.com/apache/beam/pull/34700 On Sat, 26 Apr, 2025, 04:57 Aditya, wrote: > Hi Danny, > > I’ve completed the implementation of the OpenAI text embedding handler and > have opened a PR for it. > Could you please take a look when you get a chance? > > Thanks, > Aditya > >>

Re: [DISCUSS] Proposal for Debezium IO Upgrade to 3.1.1 (and Java 17 Build Enablement)

This is super helpful, thank you! I was looking for these kinds of switches in the other build configs, I agree that a generalization of this would be helpful going forward (thinking about other libraries that might require higher Java versions in the future). Thank you for taking the time to test

Re: Make cloudpickle the default library in Beam 2.65.0

Ah yes, and no more saving the main session :) > FWIW - I noticed that the DataFlow Options documentation[1] for setting the pickling library and the Beam documentation Thanks for bringing it up. The doc is outdated, the issue was fixed in https://github.com/apache/beam/issues/21615 . On Wed, Ap

Re: [DISCUSS] Proposal for Debezium IO Upgrade to 3.1.1 (and Java 17 Build Enablement)

Yeah those configurations are needed to accommodate errorprone. I did some test on https://github.com/apache/beam/pull/34788 based on your PR. I get Debezium build on CI and unit test passing (except there is an integration test stuck). On Wed, Apr 30, 2025 at 11:46 AM Tobi Kaymak wrote: > Than

Re: [DISCUSS] Proposal for Debezium IO Upgrade to 3.1.1 (and Java 17 Build Enablement)

Thank you! Yes, that is my understanding too. I tried to force Java 17, in Debezium IOs build.gradle, but I failed so far. I even tried to completely clear the arguments and manually construct them for the gradle command line [0], however then this clashed with ErrorProne. I will give it another sh

Re: [DISCUSS] Proposal for Debezium IO Upgrade to 3.1.1 (and Java 17 Build Enablement)

The purpose of the fallback [0] is to make other Beam components build on Java11, while only `:sdks:java:io:debezium` should be configured to build on Java17, in its build.gradle file. On Wed, Apr 30, 2025 at 11:14 AM XQ Hu via dev wrote: > I think we can remove 11. Looks like we always do this:

Re: [DISCUSS] Proposal for Debezium IO Upgrade to 3.1.1 (and Java 17 Build Enablement)

I think we can remove 11. Looks like we always do this: JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/11.0.27-6/x64 However, we probably need to change that direct github workflow to remove :sdks:java:container:java8 and :sdks:java:container:java11 and add :sdks:java:container:java17.

Re: [DISCUSS] Proposal for Debezium IO Upgrade to 3.1.1 (and Java 17 Build Enablement)

I do have a silly question, I am struggling to find the reason for the fallback need of Java 11 in the beam_PreCommit_Java_Debezium_IO_Direct.yml [0] I was trying to not interfere with the build system outside of the module by doing some tricks within the build.gradle of Debzium IO in the second PR

Re: Make cloudpickle the default library in Beam 2.65.0

Wow this is fantastic! I tested it out and it worked great for my runner. I am also excited for this change now and will eagerly set `cloudpickle` as the default pickler for our code. FWIW - I noticed that the DataFlow Options documentation[1] for setting the pickling library and the Beam document