On Wed, May 2, 2012 at 8:07 PM, Ted Dunning <[email protected]> wrote:
> Making a pig module for mahout is a fine idea. The twitter guys may have > something better, though, so we should explore that as well. Andy's > comments make that possibility very interesting. > What I'd want to suggest is that anyone who wants to move rapidly on pig/mahout integration should start a github repo which doesn't directly inject itself into mahout, but stands separately for now, but then the maven dependency DAG rears its ugly head: pig-vector depends on mahout-core so if we *do* want to start writing cool stuff *in mahout* which depends on it, we're circularly dependently self-destruct. Now, if we had a proper mahout-writables maven module (*ahem*!), which had all the stuff pig-vector needed, and mahout-core depended on this, then mahout-core (or mahout-examples) could still depend on pig-vector (or something like it, like the elephant-bird-loaders slim dep) at some point. > > On Wed, May 2, 2012 at 5:20 PM, Timothy Potter <[email protected]> > wrote: > > > Thanks Ted! Removing the elephant-bird dependency / build problems > > sounds like a good task we should include in our plans for the hackday > > ... what are your thoughts on adding pig-vector to Mahout as a contrib > > module? Do you want to keep it separate or eventually make its way > > into the project? > > > -- -jake
