That makes sense. Without a reproducible case for AVRO-792 from the bug reporter, we may not make any more progress.
Thanks Thiru! On 4/27/11 4:28 AM, "Thiruvalluvan M G" <[email protected]> wrote: >I have fixed AVRO-793 today. > >I'm not sure if AVRO-792 is a resolver issue. I'm saying this because we >didn't change anything in the resolver between 1.4 and 1.5. The resolver >is >complaining because it reads a union index which is not valid for the >given >schema. I guess this is because mismatch between the resolver's state and >the stream. But I don't have an explanation why. > >Since we are getting any closer to a solution, I think we should go ahead >with 1.5.1 with this known issue. > >Thiru > >-----Original Message----- >From: Scott Carey [mailto:[email protected]] >Sent: Tuesday, April 26, 2011 11:54 PM >To: [email protected] >Subject: Re: Release Avro 1.5.1 soon? > >No objections. > > >AVRO-792 and AVRO-793 both appear to be bugs in the java resolver that >will likely require a 1.5.2 if they are not included however. > >-Scott > >On 4/26/11 9:14 AM, "Doug Cutting" <[email protected]> wrote: > >>I'd like to commit AVRO-791 and roll a 1.5.1 release candidate. >> >>Any objections? >> >>Doug >> >>On 04/19/2011 02:51 PM, Doug Cutting wrote: >>> I'd like to try to release Avro 1.5.1 soon. >>> >>> The list of unresolved issues designated for this release is at: >>> >>> http://tinyurl.com/3ejyfka >>> >>> Currently there's only one blocker. If there are others that you >>>intend >>> to work on soon and feel should block this release, can you please mark >>> them as blockers by end of the week? Thanks! >>> >>> Doug >
