Maybe a better user question is: How many people are still using the deprecated Hadoop code?
If the number is small +1 for removal. On Mar 20, 2016, at 11:04 AM, Andrew Musselman <andrew.mussel...@gmail.com> wrote: To clarify, the MAHOUT_LOCAL option only works for legacy Hadoop MapReduce-based jobs which officially became deprecated in 0.10.0. On Sun, Mar 20, 2016 at 10:25 AM, Andrew Musselman < andrew.mussel...@gmail.com> wrote: > Yes as I understand it. > > > On Sunday, March 20, 2016, Pat Ferrel <p...@occamsmachete.com> wrote: > >> Are we just talking about Hadoop Mapreduce? I thought is was ignored when >> using Spark. >> >> On Mar 20, 2016, at 8:20 AM, alok tanna <tannaa...@gmail.com> wrote: >> >> -1 MAHOUT_LOCAL is very useful for quick POC . >> >> Thanks, >> Alok Tanna >> Sent from my iPhone >> >>> On Mar 20, 2016, at 5:01 AM, Mihai Dascalu <mihai.dasc...@cs.pub.ro> >> wrote: >>> >>> -1 I still use it for fast deployment and it’s really helpful for small >> local processing >>> >>> Have a great weekend! >>> Mihai >>> >>>> On 20 Mar 2016, at 06:13, Suneel Marthi <suneel.mar...@gmail.com> >> wrote: >>>> >>>> +1 to remove this >>>> >>>> Sent from my iPhone >>>> >>>>> On Mar 20, 2016, at 12:01 AM, Andrew Musselman < >> andrew.mussel...@gmail.com> wrote: >>>>> >>>>> We're discussing removing the MAHOUT_LOCAL option in order to trim >> artifact >>>>> sizes. >>>>> >>>>> If you think keeping the option to use MAHOUT_LOCAL for testing with >> the >>>>> single-node mode of Hadoop is important please let us know. It can be >> handy >>>>> for trying things out but it would be nice to ditch the effort >> required to >>>>> maintain it. >>>>> >>>>> See https://issues.apache.org/jira/browse/MAHOUT-1705 for more >> context. >>>>> >>>>> Thanks! >>> >> >>
