I think it is a great idea to be able to plug-in a different back-ends.
But the way to do that, IMHO, is to make the intermediate artifacts public
(akin to making byte-code specs public).
That way, independent projects can spring up that take the translated pig
script, and provide a new interpret
+1.
- milind
On 4/22/10 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
Oh, sorry about that, then. Thanks for the info.
- milind
On 9/22/09 10:29 AM, "Alan Gates" wrote:
> private is the pmc list. Releases need pmc votes, hence we send to
> private.
>
> Alan.
>
> On Sep 21, 2009, at 7:46 PM, Milind A Bhandarkar wrote:
>
>
Unrelated to the message content:
why is there a priv...@hadoop.apache.org on the cc here? Is this even
a valid alias? An open source project needs to conduct it's
discussions in public, so an email address (even) named "private"
makes me very nervous about the development process.
- Milind
On S
It's Friday evening, so I have some time to discuss philosophy ;-)
Before we discuss any question about revisiting pig philosophy, the
first question that needs to be answered is "what is pig" ? (this
corresponds to the Hindu philosophy's basic argument, that any deep
personal philosophical
project should not influence that decision.
>
> Is there an alternative to creating a branch? Would you prefer we commit
> new features to a line that is being used by users?
>
> Raghu.
>
> Milind A Bhandarkar wrote:
>> IANAC, but my (non-binding) vote is also -1. I think
IANAC, but my (non-binding) vote is also -1. I think all the improvements
and feature addition to zebra should be available through pig trunk. The
codebase is not big enough to justify creating a branch. If the reason is
Pig's dependence on a checked in hadoop jar, the shims proposal by Dmitry
shou
