On Sun, Apr 18, 2010 at 3:37 PM, Jake Mannix <jake.man...@gmail.com> wrote:
> > > 4) VectorWritable acts still just as it is now, basically > > > > Yes, made it more general so we don't have to modify it to handle each > > new Vector impl too. > > > > The trick is to make the writing part efficient without knowing the > internals of the vector impl. I think it is just better to know some of the internals... at least to the extent of putting a few facilitory methods onto various vectors that initialize it efficient. The VectorWritable would know about these methods and they would be chosen to make VectorWritable very efficient, but not for general use. > ... > Ok, I'm convinced that this should be good for now, until we > get to the happy Avro-future. Yes.
