[ https://issues.apache.org/jira/browse/PIG-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673074#action_12673074 ]
Olga Natkovich commented on PIG-574: ------------------------------------ I tested patch and all is good. I have made one small change - moving parameters in front of the pig script to be consistent with pig cmd syntax. New patch is attached > 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: PIG-574.patch, run_command.patch, > run_command_params.patch, run_command_params_021109.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.