[ 
https://issues.apache.org/jira/browse/HIVE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741553#action_12741553
 ] 

Namit Jain commented on HIVE-578:
---------------------------------

atching file ql/src/java/org/apache/hadoop/hive/ql/parse/PartitionPruner.java
(Stripping trailing CRs from patch.)
can't find file to patch at input line 27070
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: ql/src/java/org/apache/hadoop/hive/ql/parse/ASTPartitionPruner.java
|===================================================================
|--- ql/src/java/org/apache/hadoop/hive/ql/parse/ASTPartitionPruner.java        
(revision 801363)
|+++ ql/src/java/org/apache/hadoop/hive/ql/parse/ASTPartitionPruner.java        
(working copy)
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
(Stripping trailing CRs from patch.)
patching file 
ql/src/java/org/apache/hadoop/hive/ql/parse/TypeCheckProcFactory.java
(Stripping trailing CRs from patch.)
patching file ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java
(Stripping trailing CRs from patch.)
patching file ql/src/java/org/apache/hadoop/hive/ql/parse/ParseContext.java
(Stripping trailing CRs from patch.)
patching file 
ql/src/java/org/apache/hadoop/hive/ql/parse/PrunedPartitionList.java


Problems in applying the patch - can you generate the patch again ?

> Refactor partition pruning code as an optimizer transformation
> --------------------------------------------------------------
>
>                 Key: HIVE-578
>                 URL: https://issues.apache.org/jira/browse/HIVE-578
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.3.0
>            Reporter: Ashish Thusoo
>            Assignee: Ashish Thusoo
>         Attachments: patch-578.txt, patch-578_1.txt, patch-578_2.txt, 
> patch-578_3.txt
>
>
> Some bugs with partition pruning have been reported and the correct fix for 
> many of them is to rewrite the partition pruning code as an optimizer 
> transformation which gets kicked in after the predicate pushdown code. This 
> refactor also uses the graph walker framework so that the partition pruning 
> code gets consolidated well with the frameworks and does not work on the 
> query block but rather works on the operator tree.

-- 
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