On Apr 22, 2010, at 4:38 PM, Richard Ding wrote:
Yes.
The abstraction layer I was referring to is
src/org/apache/pig/backend/executionengine and
src/org/apache/pig/backend/datastorage.
Thanks for the clarification. +1
Arun
Thanks,
-Richard
-----Original Message-----
From: Arun C Murthy [mailto:[email protected]]
Sent: Thursday, April 22, 2010 4:14 PM
To: [email protected]
Subject: Re: Consider cleaning up backend code
I read it as getting rid of concepts parallel to hadoop in src/org/
apache/pig/backend/hadoop/datastorage.
Is that true?
thanks,
Arun
On Apr 22, 2010, at 1:34 PM, Dmitriy Ryaboy wrote:
I kind of dig the concept of being able to plug in a different
backend,
though I definitely thing we should get rid of the dead localmode
code. Can
you give an example of how this will simplify the codebase? Is it
more than
just GenericClass foo = new SpecificClass(), and the associated
extra files?
-D
On Thu, Apr 22, 2010 at 1:25 PM, Arun C Murthy <[email protected]>
wrote:
+1
Arun
On Apr 22, 2010, at 11:35 AM, Richard Ding wrote:
Pig has an abstraction layer (interfaces and abstract classes) to
support multiple execution engines. After PIG-1053, Hadoop is the
only
execution engine supported by Pig. I wonder if we should remove
this
layer of code, and make Hadoop THE execution engine for Pig. This
will
simplify a lot the backend code.
Thanks,
-Richard
