Just an after thought
Shouldn't false be given as a parameter by default.
Should this be corrected ?
Regards
Rohan
Rohan Rai wrote:
Actually I think the evaluation is correct
Overriding the method to pass FALSE as parameter, enhances the experiences
Secondly as in
org.apache.pig.Main
grunt.ex
Actually I think the evaluation is correct
Overriding the method to pass FALSE as parameter, enhances the experiences
Secondly as in
org.apache.pig.Main
grunt.exec(); is called
which in turn calls
parser.parseStopOnError();
which calls
parseStopOnError(false);
Regards
Rohan
Dmitriy Ryaboy wrote
This stuff is a bit convoluted, isn't it?
I think you may be right (I never use registerScript). Try an experiment?
On Thu, Mar 4, 2010 at 11:20 AM, Rohan Rai wrote:
> In addition
>
> Even
> org.apache.pig.tools.pigscript.parser.PigScriptParser (.jj)
> seems to tell that its not running in batch
In addition
Even
org.apache.pig.tools.pigscript.parser.PigScriptParser (.jj)
seems to tell that its not running in batch mode .
Is the interpretation incorrect
Regards
Rohan
Rohan Rai wrote:
Thats what makes it confusing
If you see the the parameter getting passed is true which is sameBatch
o
Thats what makes it confusing
If you see the the parameter getting passed is true which is sameBatch
on which it should ideally not call setBatchOn
if (!mInteractive && !sameBatch) {
setBatchOn();
}
Dmitriy Ryaboy wrote:
Looks like it's on automatically.
Code below is from
Looks like it's on automatically.
Code below is from trunk, but I don't think this changed recently. I got rid
of exception handling for conciseness.
In PigServer:
public void registerScript(String fileName) throws IOException {
GruntParser grunt = new GruntParser(new FileReader(
Thanks Dmitriy
Just a question more
registerScript allows to register a pig script in the embedded mode
So the confusion was does it internally tries to optimize it.
or setBatchOn has to be explicitly called
Regards
Rohan
Dmitriy Ryaboy wrote:
1) Automatically, if you call it right. Look for
1) Automatically, if you call it right. Look for the setBatchOn and
executeBatch methods (I may be slightly off on the method names, going off
memory)
2) The optimizer moves stuff around and may be executing things in a
slightly different order then what you tell it. This can mean pushing up
proj
In addendum
How can I play with Logical Plan?
Rohan Rai wrote:
On using embedded Pig Server and registering a pig script for execution
1) Does Multi Query Optimization happens automatically, or has to
explicitly told so.
2) Logical Plan. What one can infer out of it.
3) Does the Block Size (d
On using embedded Pig Server and registering a pig script for execution
1) Does Multi Query Optimization happens automatically, or has to
explicitly told so.
2) Logical Plan. What one can infer out of it.
3) Does the Block Size (defined in hadoop) has an effect on performance
or the number of m
10 matches
Mail list logo
