following up on my earlier email. Would anyone be interested in a "compressed" serialization for DenseVector/SparseVector that follows in the vein of hadoop.io.Writable? The space overhead for gson (parsing issues not-withstanding) is pretty high, and it wouldn't be terribly hard to implement a high-performance thing for vectors.
-- David On Tue, Jun 16, 2009 at 1:39 PM, Jeff Eastman<j...@windwardsolutions.com> wrote: > +1, you added name constructors that I didn't have and the equals/equivalent > stuff. Ya, Gson makes it all pretty trivial once you grok it. > > > Grant Ingersoll wrote: >> >> Shall I take that as approval of the approach? >> >> BTW, the Gson stuff seems like a winner for serialization. >> >> On Jun 16, 2009, at 3:56 PM, Jeff Eastman wrote: >> >>> You gonna commit your patch? I agree with shortening the class name in >>> the JsonVectorAdapter and will do it once you commit ur stuff. >>> Jeff >> >> >> >> > >
