I am building my avro fork (https://github.com/zolyfarkas/avro <https://github.com/zolyfarkas/avro> ) and publishing it to bintray: https://bintray.com/zolyfarkas/core/avro/1.8.1.25p <https://bintray.com/zolyfarkas/core/avro/1.8.1.25p> … it is one option you have that is not difficult to implement (took me about 1h)...
I am doing this approach with most open source libraries… Depending on open source project, the turnaround for a defect/enhancement can be between 1 week -> 1 year, and my deadlines are not that generous... hope it helps... —Z > On Nov 30, 2018, at 6:20 PM, David Carlton <carl...@sumologic.com> wrote: > > I'm running into https://issues.apache.org/jira/browse/AVRO-1723 > <https://issues.apache.org/jira/browse/AVRO-1723> (forward declarations in > Avro IDL), and I'm wondering what the timing is for a release that contains > that fix? I see https://issues.apache.org/jira/browse/AVRO-2163 > <https://issues.apache.org/jira/browse/AVRO-2163> for releasing 1.8.3, but > it's not clear from that Jira what the timeline is for 1.8.3 and whether it > will contain a fix for AVRO-1723. So I'm trying to figure out if I should > generate my own local build of Avro containing the patch for AVRO-1723, or if > I should just write that protocol in JSON instead of IDL and then switch it > over to IDL once 1.8.3 is released. > > Thanks for any advice you have, > David Carlton > carl...@sumologic.com <mailto:carl...@sumologic.com>
