On Oct 1, 2009, at 12:17 AM, Jake Mannix wrote:
On Wed, Sep 30, 2009 at 8:26 PM, Ted Dunning <[email protected]>
wrote:
So why do we really need vectors to be Writable? I see the appeal,
it's
nice and makes the code nicely integrated, but the way I ended up
going,
so that you could use decomposer either with or without Hadoop was to
use a decorator - just have VectorWritable be an implementation of
Vector
which encapsulates the Writable methods, and delegates to a Hadoop -
agnostic Vector member instance.
This way all the algorithms which use the Vectors don't need to care
about
Hadoop unless they really do.
That sounds reasonable, just going to take a little refactoring.
