+1 on a patch release - we've done a fair amount of work to make releasing easier, and one of my hopes is that it will enable quick patches like this. I'd vote we try to fix the underlying Java piece as well, though, doing a patch release for one language shouldn't be significantly cheaper than doing it for multiple languages.
Thanks, Danny On Wed, Mar 27, 2024 at 7:19 PM Robert Burke <rob...@frantil.com> wrote: > +1 to a targeted patch release. > > We did the same for the Go SDK a little while back. It would be good to > see what's different for a different SDK. > > On Wed, Mar 27, 2024, 4:01 PM Robert Bradshaw via dev <dev@beam.apache.org> > wrote: > >> Given the severity of the breakage, and the simplicity of the workaround, >> I'm in favor of a patch release. I think we could do Python-only, which >> would make the process even more lightweight. >> >> On Wed, Mar 27, 2024 at 3:48 PM Jeff Kinard <j...@thekinards.com> wrote: >> >>> Hi all, >>> >>> Beam 2.55 was released with a bug that causes WriteToJson on Beam YAML >>> to fail when using the Java variant. This also affects any user attempting >>> to use the Xlang JsonWriteTransformProvider - >>> https://github.com/apache/beam/blob/master/sdks/java/io/json/src/main/java/org/apache/beam/sdk/io/json/providers/JsonWriteTransformProvider.java >>> >>> This is due to a change to >>> https://github.com/apache/beam/blob/master/sdks/java/io/json/build.gradle >>> that removed >>> a dependency on everit which also removed it from being packaged into >>> the expansion service JAR: >>> beam-sdks-java-extensions-sql-expansion-service-2.55.0.jar >>> >>> There is a temporary fix to disable the provider in Beam YAML: >>> https://github.com/apache/beam/pull/30777 >>> >>> I think with the total loss of function, and a trivial fix, it is worth >>> creating a patch release of Beam 2.55 to include this fix. >>> >>> - Jeff >>> >>>
