Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B817717DA0 for ; Wed, 1 Oct 2014 07:33:34 +0000 (UTC) Received: (qmail 37737 invoked by uid 500); 1 Oct 2014 07:33:34 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 37657 invoked by uid 500); 1 Oct 2014 07:33:34 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 37642 invoked by uid 500); 1 Oct 2014 07:33:34 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 37639 invoked by uid 99); 1 Oct 2014 07:33:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Oct 2014 07:33:34 +0000 Date: Wed, 1 Oct 2014 07:33:34 +0000 (UTC) From: "Damien Carol (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-8313) Optimize evaluation for ExprNodeConstantEvaluator and ExprNodeNullEvaluator MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)