Seems like a good reason to release legacy, if only to get hadoop 2 Doesn’t seem like a good idea to drop legacy stuff unless it’s no longer used enough to support. The recommender stuff is still actively being used from Stack Overflow and the user list questions—even the in core code. I answer questions as best I can and try to steer them to newer stuff but it’s not time to retire that yet IMO.
On Mar 6, 2015, at 11:42 AM, Suneel Marthi <[email protected]> wrote: What's the timeline for the BigTop 0.9 Release ? Mahout 0.9 had no support for Hadoop 2x and hence the issue u had reported, but we have it now (and its all legacy to be removed in a future release). On Fri, Mar 6, 2015 at 2:31 PM, jay vyas <[email protected]> wrote: > Hi Mahout. We are prepping for 0.9 Release of bigtop. > > Is anyone in the mahout community interested in collaborating with us > around selecting a mahout version, and confirming it works? We can do the > testing on our end, possibly just fire up a google hangout and do it over > screen share to resolve any issues. > > In bigtop 0.8, we released a version of mahout which didnt work properly on > yarn (https://issues.apache.org/jira/browse/BIGTOP-1470), so we are really > pushing hard to find collaborators in the communities which we package, > rather than doing it all on our own :). > > jay vyas > > PS IMO I think if mahout and bigtop collaborate on releases, its a big win > for both projects (I feel this way also about other partners in the hadoop > ecosystem). If the packaging of mahout inside of bigtop isn't of interest > to anyone in this list, I'm happy to stop sending bigtop related > information, just let me know. >
