[
https://issues.apache.org/jira/browse/HIVE-8313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193707#comment-14193707
]
Mithun Radhakrishnan commented on HIVE-8313:
--------------------------------------------
@[~gopalv]: Yes, I'd like this to be included in 0.14, if possible. There's
tangible gains in performance with this fix.
Pinging [~hagleitn]. I hope I haven't missed the boat with this one.
> Optimize evaluation for ExprNodeConstantEvaluator and ExprNodeNullEvaluator
> ---------------------------------------------------------------------------
>
> Key: HIVE-8313
> URL: https://issues.apache.org/jira/browse/HIVE-8313
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.12.0, 0.13.0, 0.14.0
> Reporter: Mithun Radhakrishnan
> Assignee: Mithun Radhakrishnan
> Labels: Performance
> Fix For: 0.14.0
>
> Attachments: HIVE-8313.1.patch, HIVE-8313.2.patch
>
>
> Consider the following query:
> {code:sql}
> SELECT foo, bar, goo, id
> FROM myTable
> WHERE id IN ( 'A', 'B', 'C', 'D', ... , 'ZZZZZZ' );
> {code}
> One finds that when the IN clause has several thousand elements (and the
> table has several million rows), the query above takes orders-of-magnitude
> longer to run on Hive 0.12 than say Hive 0.10.
> I have a possibly incomplete fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
