(For others, the jira under discussion is AVRO-1901 https://issues.apache.org/jira/browse/AVRO-1901)
On Tue, Oct 4, 2016 at 8:28 AM, Sean Busbey <bus...@cloudera.com> wrote: > yes, it looks like the jira landed in 1.9, though there isn't a fix > version set. I don't see anything in the patch that would prevent a > backport to 1.7. > > On Mon, Oct 3, 2016 at 2:28 PM, radai <radai.rosenbl...@gmail.com> wrote: >> Hi, >> >> I've recently encountered a bug in avro code generation, for which I >> submitted a fix ( >> https://github.com/apache/avro/commit/be33922c03bd229b885fb9d664b55ce308f6ffaf >> ). >> >> The issue was discovered while trying to migrate a sizable codebase from >> avro 1.4 to 1.7 >> >> Would it be possible to back-port this fix to 1.7? bumping 1.7 to latest >> would be a lot easier than trying to upgrade 1.4 and now 1.7 code to 1.9 >> (which is where this will will end up in, when its released?) >> >> I can just open a PR porting the fix to the 1.7 branch (maybe 1.8 branch as >> well, for consistency), if thats the procedure. >> >> Thanks in advance, >> >> >> Radai. > > > > -- > busbey -- busbey
