1. Who wants to write a bulky buggy (possibly 100+ lines of code) mapreduce job and at the end the expected answer is wrong and you gotta sit debugging the whole stack, So there comes Pig and Hive and all.
2. Pig is more like an analytical tool and the person who is writing the Pig job doesn't need to know anything about mapreduce jobs or java etc. So leveraging the power of mapreduce and building a easy scalable platform which a developer and an analyst can easily use gets the attention of PIG! These would give you a better understanding. http://www.slideshare.net/DonaldMiner/pig-vs-mapreduce http://stackoverflow.com/questions/17950248/pig-vs-hive-vs-native-map-reduce Thanks Best Regards On Thu, Dec 4, 2014 at 2:44 AM, Mohan Krishna <mohan.25fe...@gmail.com> wrote: > Why PIG came in to picture? > What makes Hadoop to focus on PIG? >
