You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by Prashant Kommireddi <pr...@gmail.com> on 2013/02/10 04:50:29 UTC
registerScript vs executeBatch
Any reason why PigServer.registerScript(..) chooses to only parse and not
execute, vs executing a pig script via command line invokes the same method
and chooses to execute right away. The latter makes sense to me, but not
sure why the behavior of PigServer API is not in sync with that?
The difference in code is GruntParser.parseStopOnError(boolean) is called
with different arguments in the 2 cases.
-Prashant
Re: registerScript vs executeBatch
Posted by Julien Le Dem <ju...@twitter.com>.
yes,
the behavior of registerScript() depends on if you called setBatchOn()
before or not
if batch is on, you need to call executeBatch()
otherwise it just executes when you store something
On Sat, Feb 9, 2013 at 11:03 PM, Bill Graham <bi...@gmail.com> wrote:
> Is this because PigServer supportes isBatchOn and grunt/command line
> doesn't?
>
> On Sat, Feb 9, 2013 at 7:50 PM, Prashant Kommireddi <prash1784@gmail.com
> >wrote:
>
> > Any reason why PigServer.registerScript(..) chooses to only parse and not
> > execute, vs executing a pig script via command line invokes the same
> method
> > and chooses to execute right away. The latter makes sense to me, but not
> > sure why the behavior of PigServer API is not in sync with that?
> >
> > The difference in code is GruntParser.parseStopOnError(boolean) is called
> > with different arguments in the 2 cases.
> >
> > -Prashant
> >
>
>
>
> --
> *Note that I'm no longer using my Yahoo! email address. Please email me at
> billgraham@gmail.com going forward.*
>
Re: registerScript vs executeBatch
Posted by Bill Graham <bi...@gmail.com>.
Is this because PigServer supportes isBatchOn and grunt/command line
doesn't?
On Sat, Feb 9, 2013 at 7:50 PM, Prashant Kommireddi <pr...@gmail.com>wrote:
> Any reason why PigServer.registerScript(..) chooses to only parse and not
> execute, vs executing a pig script via command line invokes the same method
> and chooses to execute right away. The latter makes sense to me, but not
> sure why the behavior of PigServer API is not in sync with that?
>
> The difference in code is GruntParser.parseStopOnError(boolean) is called
> with different arguments in the 2 cases.
>
> -Prashant
>
--
*Note that I'm no longer using my Yahoo! email address. Please email me at
billgraham@gmail.com going forward.*