Re: The future of MapReduce

2014-07-16 Thread Peyman Mohajerian
@hadoop.apache.org *Subject:* Re: The future of MapReduce It depends... It seems most are evolving from needing lots of data crunched, to lots of data crunched right now. Most are looking for *real-time* fraud detection or recommendations, for example, which MapReduce is not ideal for. Marco

Re: The future of MapReduce

2014-07-02 Thread Shahab Yunus
wrote: Heard about Google dataflow from last week On Jul 1, 2014 4:42 PM, Marco Shaw marco.s...@gmail.com wrote: Interesting timing: http://java.dzone.com/articles/there-future-mapreduce Google declared last week that MapReduce was dead more or less, but there are very few that process

The future of MapReduce

2014-07-01 Thread Adaryl Bob Wakefield, MBA
“The Mahout community decided to move its codebase onto modern data processing systems that offer a richer programming model and more efficient execution than Hadoop MapReduce.” Does this mean that learning MapReduce is a waste of time? Is Storm the future or are both technologies necessary?

Re: The future of MapReduce

2014-07-01 Thread Marco Shaw
It depends... It seems most are evolving from needing lots of data crunched, to lots of data crunched right now. Most are looking for *real-time* fraud detection or recommendations, for example, which MapReduce is not ideal for. Marco On Tue, Jul 1, 2014 at 12:00 PM, Adaryl Bob Wakefield, MBA

Re: The future of MapReduce

2014-07-01 Thread Adaryl Bob Wakefield, MBA
From your answer, it sounds like you need to be able to do both. From: Marco Shaw Sent: Tuesday, July 01, 2014 10:24 AM To: user Subject: Re: The future of MapReduce It depends... It seems most are evolving from needing lots of data crunched, to lots of data crunched right now. Most

Re: The future of MapReduce

2014-07-01 Thread kartik saxena
*Subject:* Re: The future of MapReduce It depends... It seems most are evolving from needing lots of data crunched, to lots of data crunched right now. Most are looking for *real-time* fraud detection or recommendations, for example, which MapReduce is not ideal for. Marco On Tue, Jul 1, 2014

Re: The future of MapReduce

2014-07-01 Thread Marco Shaw
Wakefield, MBA adaryl.wakefi...@hotmail.com wrote: From your answer, it sounds like you need to be able to do both. *From:* Marco Shaw marco.s...@gmail.com *Sent:* Tuesday, July 01, 2014 10:24 AM *To:* user user@hadoop.apache.org *Subject:* Re: The future of MapReduce It depends

Re: The future of MapReduce

2014-07-01 Thread Adaryl Bob Wakefield, MBA
not want to spend hours learning how to write MapReduce jobs. B. From: Marco Shaw Sent: Tuesday, July 01, 2014 3:50 PM To: user Subject: Re: The future of MapReduce Sorry, not sure if that's a question. Hadoop v1=HDFS+MapReduce Hadoop v2=HDFS+YARN (+ MapReduce part of the core, but now considered

Re: The future of MapReduce

2014-07-01 Thread Marco Shaw
Interesting timing: http://java.dzone.com/articles/there-future-mapreduce Google declared last week that MapReduce was dead more or less, but there are very few that process data at Google's level. Makes me wonder what Yahoo has for a tech mix these days... On Tue, Jul 1, 2014 at 6:01 PM

Re: The future of MapReduce

2014-07-01 Thread snehil wakchaure
Heard about Google dataflow from last week On Jul 1, 2014 4:42 PM, Marco Shaw marco.s...@gmail.com wrote: Interesting timing: http://java.dzone.com/articles/there-future-mapreduce Google declared last week that MapReduce was dead more or less, but there are very few that process data