Gunther Hagleitner updated PIG-627:

    Attachment: streaming-fix.patch

Some fixes in the patch "streaming-fix.patch":

   * The split operator wasn't always playing nicely with the way we run the 
pipeline one extra time in the mapper's or reducer's close function if there's 
a stream operator present
   * Moved the MR optimizer that sets "stream in map" and "stream in reduce" to 
the end of the queue.
   * PhyPlanVisitor forgets to pop some walkers it pushed on the stack. That 
can result in the NoopFilterRemoval stage failing, because it's looking in the 
wrong plan.
   * Setting the jobname by default to the scriptname came in through the last 
merge, but didn't work anymore

> PERFORMANCE: multi-query optimization
> -------------------------------------
>                 Key: PIG-627
>                 URL: https://issues.apache.org/jira/browse/PIG-627
>             Project: Pig
>          Issue Type: Improvement
>    Affects Versions: 0.2.0
>            Reporter: Olga Natkovich
>         Attachments: file_cmds-0305.patch, fix_store_prob.patch, 
> merge_741727_HEAD__0324.patch, merge_741727_HEAD__0324_2.patch, 
> merge_trunk_to_branch.patch, multi-store-0303.patch, multi-store-0304.patch, 
> multiquery-phase2_0313.patch, multiquery-phase2_0323.patch, 
> multiquery_0223.patch, multiquery_0224.patch, multiquery_0306.patch, 
> multiquery_explain_fix.patch, non_reversible_store_load_dependencies.patch, 
> non_reversible_store_load_dependencies_2.patch, 
> noop_filter_absolute_path_flag.patch, 
> noop_filter_absolute_path_flag_0401.patch, streaming-fix.patch
> Currently, if your Pig script contains multiple stores and some shared 
> computation, Pig will execute several independent queries. For instance:
> A = load 'data' as (a, b, c);
> B = filter A by a > 5;
> store B into 'output1';
> C = group B by b;
> store C into 'output2';
> This script will result in map-only job that generated output1 followed by a 
> map-reduce job that generated output2. As the resuld data is read, parsed and 
> filetered twice which is unnecessary and costly. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to