On Thu, Feb 11, 2010 at 3:40 PM, Jake Mannix <jake.man...@gmail.com> wrote: > Sure, but we're not doing Avro for 0.3, so we should probably at least fix > this in some minimal way before another release.
Agreed. I'm wondering -- and this would probably be pretty obvious if I just looked at the code (sorry!) -- are there contexts where thread safety for vector writable (or lack thereof) in this case is a problem? -- e.g are there places in the code where multiple threads are using VectorWritable to read vectors of different types concurrently? I'm not suggesting we shouldn't fix it, just trying to understand the severity of the bug. Drew
