maheshrajus opened a new pull request, #6916:
URL: https://github.com/apache/hive/pull/6916

   
   
   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
     2. Ensure that you have created an issue on the Hive project JIRA: 
https://issues.apache.org/jira/projects/HIVE/summary
     3. Ensure you have added or run the appropriate tests for your PR: 
     4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP]HIVE-XXXXX:  Your PR title ...'.
     5. Be sure to keep the PR description updated to reflect all changes.
     6. Please write your PR title to summarize what this PR proposes.
     7. If possible, provide a concise example to reproduce the issue for a 
faster review.
   
   -->
   
   ### What changes were proposed in this pull request?
    - SharedWorkOptimizer: added removalLeavesWorkWithoutSink(...) and call it 
from validPreConditions(). A merge 
     is skipped if deleting the duplicate's operators would leave a work with 
no ReduceSink/FileSink.            
     - The check covers a deleted ReduceSink and also a deleted chain that ends 
in one (e.g. SEL -> RS). 
   
   
   ### Why are the changes needed?
     When two identical table scans are merged, the operators that only fed the 
duplicate scan are deleted.      
     Sometimes one of them is the only ReduceSink of a reducer, and all that 
reducer has left is a dynamic       
     partition pruning (DPP) event branch. GenTezWork only starts a new vertex 
at a sink, so that reducer never  
     gets its own vertex. Its mergepartial GroupBy ends up inside the upstream 
Map vertex, and the query fails at
     runtime with:   **cannot find field key from [0:_col0, 1:_col1, 2:_col2]** 
   
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   ### How was this patch tested?
   Newly added UT & qtests
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to