You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Damien Carol (JIRA)" <ji...@apache.org> on 2014/10/01 09:33:34 UTC
[jira] [Updated] (HIVE-8313) Optimize evaluation for
ExprNodeConstantEvaluator and ExprNodeNullEvaluator
[ https://issues.apache.org/jira/browse/HIVE-8313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damien Carol updated HIVE-8313:
-------------------------------
Description:
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.
was:
Consider the following query:
{code}
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.
> 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
> Attachments: HIVE-8313.1.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)