Gunther Hagleitner updated PIG-574:
Thanks for reviewing the patch!
I tried to address the 3 issues you pointed out:
1) You can now specify parameters and param files in both the exec and run
grunt> run myscript.pig using param_file myparams.ppf
grunt> run myscript.pig using param LIMIT=5 param_file myparams.ppf
The syntax mimics what you can do on the command line when executing a script
without the "-"s.
2) The script lines are now added to the command history in interactive mode
3) The double grunt... That's actually harder to fix than it thought, but I
added a newline, so it won't say:
Let's just tell everyone that that's because they have extra newlines in their
scripts. Maybe they won't find out. ;-)
> run command for grunt
> Key: PIG-574
> URL: https://issues.apache.org/jira/browse/PIG-574
> Project: Pig
> Issue Type: New Feature
> Components: grunt
> Reporter: David Ciemiewicz
> Priority: Minor
> Attachments: run_command.patch, run_command_params.patch
> This is a request for a "run file" command in grunt which will read a script
> from the local file system and execute the script interactively while in the
> grunt shell.
> One of the things that slows down iterative development of large, complicated
> Pig scripts that must operate on hadoop fs data is that the edit, run, debug
> cycle is slow because I must wait to allocate a Hadoop-on-Demand (hod)
> cluster for each iteration. I would prefer not to preallocate a cluster of
> nodes (though I could).
> Instead, I'd like to have one window open and edit my Pig script using vim or
> emacs, write it, and then type "run myscript.pig" at the grunt shell until I
> get things right.
> I'm used to doing similar things with Oracle, MySQL, and R.
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.