Yeah I guess that is what I mean - clone() ought to be implemented in some way that doesn't involve serializing and deserializing in memory, just because that is typically going to be much slower. For some classes, maybe doesn't matter, but probably is quite important for key abstractions like Vector and Matrix.
On Jun 20, 2009 8:57 PM, "Ted Dunning" <[email protected]> wrote: clone is definitely independent of the Hadoop stuff, but if you have a Writable, then one of the easiest ways to implement clone is just write to a byte array and then pull it back. That makes round trip tests a bit easier as well. On Sat, Jun 20, 2009 at 10:18 AM, Sean Owen <[email protected]> wrote: > I may be misunderstanding ...
