mahout-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From scott cote <scottcc...@gmail.com>
Subject Re: Removing MAHOUT_LOCAL option
Date Mon, 21 Mar 2016 15:38:13 GMT
one more comment - I understand that it only works for the legacy code.  Kill it when the legacy
code is no longer deprecated, but gone ….

Otherwise - you will shut out people who buy the older mahout books (such as MIA) which are
still good reads, even though the tech is dated.

SCott

> On Mar 21, 2016, at 2:24 AM, David Starina <david.starina@gmail.com> wrote:
> 
> Anyhow, I'm +1 for removing MAHOUT_LOCAL, but I believe the deprecated
> MapReduce-based code still makes sense if it is running well on Ignite.
> 
> On Mon, Mar 21, 2016 at 8:20 AM, David Starina <david.starina@gmail.com>
> wrote:
> 
>> Has anyone tried to run the deprecated MapReduce code on Ignite? Is the
>> performance improvement good enough to reconsider leaving those algorithms
>> in Mahout?
>> 
>> On Mon, Mar 21, 2016 at 12:45 AM, Andrew Musselman <
>> andrew.musselman@gmail.com> wrote:
>> 
>>> Yes I agree; will leave the question open a couple days.
>>> 
>>> On Sunday, March 20, 2016, Pat Ferrel <pat@occamsmachete.com> wrote:
>>> 
>>>> 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.musselman@gmail.com
>>>> <javascript:;>> 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.musselman@gmail.com <javascript:;>> wrote:
>>>> 
>>>>> Yes as I understand it.
>>>>> 
>>>>> 
>>>>> On Sunday, March 20, 2016, Pat Ferrel <pat@occamsmachete.com
>>>> <javascript:;>> 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 <tannaalok@gmail.com
>>>> <javascript:;>> 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.dascalu@cs.pub.ro
>>>> <javascript:;>>
>>>>>> 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.marthi@gmail.com
>>>> <javascript:;>>
>>>>>> wrote:
>>>>>>>> 
>>>>>>>> +1 to remove this
>>>>>>>> 
>>>>>>>> Sent from my iPhone
>>>>>>>> 
>>>>>>>>> On Mar 20, 2016, at 12:01 AM, Andrew Musselman <
>>>>>> andrew.musselman@gmail.com <javascript:;>> 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!
>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 


Mime
View raw message