I meant to mention that we must use Avro 1.9.x as we rely on some schema resolution fixes not present in 1.8.x - so am indeed blocked.
On Wed, Jan 15, 2020 at 8:50 PM Aaron Dixon <atdi...@gmail.com> wrote: > It looks like Avro version dependency from Beam has come up in the past > [1, 2]. > > I'm currently on Beam 2.16.0, which has been compatible with my usage of > Avro 1.9.x. > > But upgrading to Beam 2.17.0 is not possible for us now that 2.17.0 has > some dependencies on Avro classes only available in 1.8.x. > > Wondering if anyone else is similar blocked and what it would take to > prioritize Beam upgrading to 1.9.x or better using a shaded version so that > clients can use their own Avro version for their own coding purposes. (Eg, > I parse Avro messages from a KafkaIO source and need 1.9.x for this but am > perfectly happy if Beam's Avro coding facilities used a shaded other > version.) > > I've made a comment on BEAM-8388 [1] to this effect. But polling community > for discussion. > > [1] https://issues.apache.org/jira/browse/BEAM-8388 > [2] https://github.com/apache/beam/pull/9779 > >
