+1. I think Jeff's patch for the file system commands (PIG-891) also
deserve some advertisement. Those commands are really handy to the end
users.
Daniel
Alan Gates wrote:
+1. In addition to the new features we've added, our change to use
Hadoop's LineRecordReader brought Pig to parity with
Hi, Dmitriy,
I just did a fresh build, and run test-commit, didn't see the problem.
Besides, org.apache.pig.experimental.logical.optimizer.PlanPrinter is in
the trunk. Can you double check?
Daniel
Dmitriy Ryaboy wrote:
Hi guys,
Trunk has been broken for a while. A bunch of tests in the test-
+1 for removing. This interface does not bring us any value when we
decide to move closer to hadoop. Writing a backend is almost writing
half of Pig. I don't think this interface is attractive to most
developers. Instead, I +1 for Milind's idea to make intermediate
artifacts available, or provi
I am still reading but one interesting question is why you decide to put
CBO in physical layer?
Dmitriy Ryaboy wrote:
Whoops :-)
Here's the Google doc:
http://docs.google.com/Doc?docid=0Adqb7pZsloe6ZGM4Z3o1OG1fMjFrZjViZ21jdA&hl=en
-Dmitriy
On Tue, Sep 1, 2009 at 12:51 PM, Santhosh Srinivasan
run time; we are not
discounting that possibility (haven't gotten quite that far in the
design, to be honest). But we feel that the implementations have to
be execution mode specific.
-Dmitriy
On Tue, Sep 1, 2009 at 6:26 PM, Jianyong Dai wrote:
I am still reading but one interesting question i
I removed ~/pigtest/conf/hadoop-site.xml and build piggybank again, all
pass. For some reason MiniCluster do not regenerate hadoop-site.xml and
reuse the old one, which happens to be wrong
Olga Natkovich wrote:
Hi,
The new version is available in
http://people.apache.org/~olga/pig-0.4.0-candi
