The story I've heard is that it was originally selected because pig's
eat anything, and the designers wanted to stress that pig would work
over any type of data (with or without metadata, nested or flat,
structured or unstructured, etc.).
It is not an acronym, and thus should not be PIG but Pig. It has
also turned out to be very convenient, as it is easy to find names
for parts of the project: Pig Latin for the script, grunt for the
shell, PigPen for the development environment, Piggybank for the UDF
repository, ...
Alan.
On Oct 20, 2008, at 8:25 AM, Latha wrote:
Greetings!
Could anyone please let me know how you came up with interesting
name 'PIG'
for the language.
Would like to know its origin as I am going to attend a viva for my
project
where I used Hadoop & Pig as backend.
Thanks & Regards,
Srilatha
