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 E9D3DE77B for ; Fri, 22 Feb 2013 00:50:13 +0000 (UTC) Received: (qmail 25951 invoked by uid 500); 22 Feb 2013 00:50:13 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 25862 invoked by uid 500); 22 Feb 2013 00:50:13 -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 25832 invoked by uid 500); 22 Feb 2013 00:50:13 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 25783 invoked by uid 99); 22 Feb 2013 00:50:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2013 00:50:13 +0000 Date: Fri, 22 Feb 2013 00:50:13 +0000 (UTC) From: "Kevin Wilfong (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-3968) Enhance logging in TableAccessInfo 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-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-3968: -------------------------------- Attachment: HIVE-3968.4.patch.txt > Enhance logging in TableAccessInfo > ---------------------------------- > > Key: HIVE-3968 > URL: https://issues.apache.org/jira/browse/HIVE-3968 > Project: Hive > Issue Type: Improvement > Components: Query Processor > Reporter: Kevin Wilfong > Assignee: Kevin Wilfong > Attachments: HIVE-3968.1.patch.txt, HIVE-3968.2.patch.txt, HIVE-3968.3.patch.txt, HIVE-3968.4.patch.txt > > > Based on what is currently available in the TableAccessInfo we can infer when it would be a good idea to add bucketing/sorting metadata for tables. However, we can't easily tell if we're already getting the benefits of bucketing/sorting. > This information can be improved by > a) storing the input table/partition objects so that we can tell if the tables/partitions are already bucketed/sorted > b) running the TableAccessAnalyzer after the logical optimizer, so that we can tell from the operators whether or not we are already getting benefits (bucketed/sort merge map joins or map group bys) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira