Comments on: Goodbye MapReduce, Hello Cascading

By: Abstracting Map Reduce – Hello Cascading | Brandon Werner

Abstracting Map Reduce – Hello Cascading | Brandon Werner — Fri, 30 Dec 2011 18:01:23 +0000

[...] An interesting post from Nathan Marz regarding an abstraction layer from Chris Wensel called Cascading: We have been doing a lot of batch processing with Hadoop MapReduce lately, and we quickly realized how painful it can be to write MapReduce jobs by hand. Some parts of our workflow require up to TEN MapReduce jobs to execute in sequence, requiring a lot of hand-coordination of intermediate data and execution order. Additionally, anyone who has done really complex MapReduce workflows knows how hard it is to keep “thinking” in MapReduce. Luckily, we discovered a great new open source product called Cascading which has alleviated a ton of our pain. Cascading is the brainchild and work of Chris Wensel, and he’s done a great job developing an API which solves many of our problems. Cascading abstracts away MapReduce into a more natural logical model and provides a workflow management layer to handle things like intermediate data and data staleness. [...]

By: Goodbye Map Reduce – Hello Cascading | Brandon Werner

Goodbye Map Reduce – Hello Cascading | Brandon Werner — Mon, 17 Oct 2011 10:18:29 +0000

[...] interesting post from Nathan Marz regarding an abstraction layer from Chris Wensel called Cascading: We have been [...]

By: יד שניה

יד שניה — Fri, 16 Sep 2011 13:29:09 +0000

thanks for all the great updates

By: engineering leveling

engineering leveling — Mon, 02 May 2011 01:49:25 +0000

“You should take a look at Yahoo!’s language for MapReduce, Pig. ”

I disagree. TO me its a little confusing. This way is better.

By: engineering leveling

engineering leveling — Mon, 02 May 2011 01:48:45 +0000

“You should take a look at Yahoo!’s language for MapReduce, Pig. It has the same features for collapsing complexity as Cascading and is also pretty easy to work with.”

I disagree. TO me its a little confusing. This way is better.

By: Goodbye Hacking Map Reduce – Hello Cascading « Brandon Werner

Goodbye Hacking Map Reduce – Hello Cascading « Brandon Werner — Sat, 01 Jan 2011 11:31:36 +0000

[...] interesting post from Nathan Marz regarding an abstraction layer from Chris Wensel called Cascading: We have been [...]

By: Fuad Efendi

Fuad Efendi — Tue, 13 Oct 2009 19:33:26 +0000

Thanks for very clear introduction; MapReduce is easy “to count words”, but develop and maintain complex apps is painful… I like this feature “plug in custom Hadoop input and output formats”… I am not familiar with Pig, but after reading your post I feel that Cascading is very natural and simple to understand; and to work with Business Domain Model instead of “thinking in MapReduce” (similar comparison: plain SQL vs. Hibernate/EJB)

By: MapReduce Variants Continue to Proliferate

MapReduce Variants Continue to Proliferate — Mon, 10 Nov 2008 23:32:55 +0000

[...] the guys at Concurrent and Scale Unlimited. For an interesting user perspective on Cascading, see Goodbye MapReduce, Hello Cascading. See also Chris Wensel’s comparison of Cascading and [...]

By: Steve Hochschild

Steve Hochschild — Mon, 13 Oct 2008 14:14:02 +0000

There are many data-intensive, long running processes in business. A chain of retail stores generates 800 GB of cash register data a week, a media company wants to de-dupe their email, USPS mail, and customer registration master data list, a large oil refinery wants to continually analyze oil pressure & temp used to cool a pump.

By: Brandon Werner » Blog Archive » Goodbye Map Reduce - Hello Cascading

Brandon Werner » Blog Archive » Goodbye Map Reduce - Hello Cascading — Wed, 24 Sep 2008 03:32:30 +0000

[...] interesting post from Nathan Marz regarding an abstraction layer from Chris Wensel called Cascading: We have been [...]