[
https://issues.apache.org/jira/browse/HIVE-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927691#action_12927691
]
Siying Dong commented on HIVE-1750:
-----------------------------------
Mostly the codes can share are walking rule settings and finding out filter
operator following table scans. Kind of framework-like codes, instead of util
functions. Need some efforts if we want to share them.
By the way, Operator.removeChild() doesn't do the same thing as what we want
to. We want to append children of the deleted filter operator to its parent but
Operator.removeChild() is just a simple removing. I'll write another function
in Operator to do the job.
> Remove Partition Filtering Conditions when Possible
> ---------------------------------------------------
>
> Key: HIVE-1750
> URL: https://issues.apache.org/jira/browse/HIVE-1750
> Project: Hive
> Issue Type: Improvement
> Reporter: Siying Dong
> Assignee: Siying Dong
> Attachments: HIVE-1750.1.patch, HIVE-1750.2.patch
>
>
> For some simple queries, partition filtering constraints take 8% of CPU time
> (now 16% since we filter twice) even if the result is always true. When
> possible, we should remove these constraints to save CPU times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
