Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 462CD200D15 for ; Thu, 21 Sep 2017 05:23:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4507D1609E4; Thu, 21 Sep 2017 03:23:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8A20A1609E2 for ; Thu, 21 Sep 2017 05:23:03 +0200 (CEST) Received: (qmail 74384 invoked by uid 500); 21 Sep 2017 03:23:02 -0000 Mailing-List: contact issues-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 issues@hive.apache.org Received: (qmail 74375 invoked by uid 99); 21 Sep 2017 03:23:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Sep 2017 03:23:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E92EB18C050 for ; Thu, 21 Sep 2017 03:23:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id tU2ew-iPDJOs for ; Thu, 21 Sep 2017 03:23:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F34E65FCF4 for ; Thu, 21 Sep 2017 03:23:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8EFE0E099A for ; Thu, 21 Sep 2017 03:23:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 41AED218F2 for ; Thu, 21 Sep 2017 03:23:00 +0000 (UTC) Date: Thu, 21 Sep 2017 03:23:00 +0000 (UTC) From: "Lefty Leverenz (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-17308) Improvement in join cardinality estimation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 21 Sep 2017 03:23:04 -0000 [ https://issues.apache.org/jira/browse/HIVE-17308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174202#comment-16174202 ] Lefty Leverenz commented on HIVE-17308: --------------------------------------- Doc note: This changes the default value of *hive.stats.correlated.multi.key.joins* to true. No TODOC3.0 label is needed because it will be documented for HIVE-16298, which created *hive.stats.correlated.multi.key.joins* in the same release (3.0.0). > Improvement in join cardinality estimation > ------------------------------------------ > > Key: HIVE-17308 > URL: https://issues.apache.org/jira/browse/HIVE-17308 > Project: Hive > Issue Type: Improvement > Components: Query Planning > Reporter: Vineet Garg > Assignee: Vineet Garg > Attachments: HIVE-17308.1.patch, HIVE-17308.2.patch, HIVE-17308.3.patch, HIVE-17308.4.patch, HIVE-17308.5.patch, HIVE-17308.6.patch, HIVE-17308.7.patch, HIVE-17308.8.patch > > > Currently during logical planning join cardinality is estimated assuming no correlation among join keys (This estimation is done using exponential backoff). Physical planning on the other hand consider correlation for multi keys and uses different estimation. We should consider correlation during logical planning as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)