Return-Path: X-Original-To: apmail-hive-user-archive@www.apache.org Delivered-To: apmail-hive-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E44FE10BD3 for ; Wed, 21 Aug 2013 02:19:23 +0000 (UTC) Received: (qmail 72597 invoked by uid 500); 21 Aug 2013 02:19:22 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 72541 invoked by uid 500); 21 Aug 2013 02:19:22 -0000 Mailing-List: contact user-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hive.apache.org Delivered-To: mailing list user@hive.apache.org Received: (qmail 72533 invoked by uid 99); 21 Aug 2013 02:19:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 02:19:22 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ricky@cloudera.com designates 209.85.219.51 as permitted sender) Received: from [209.85.219.51] (HELO mail-oa0-f51.google.com) (209.85.219.51) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 02:19:14 +0000 Received: by mail-oa0-f51.google.com with SMTP id h1so2489014oag.10 for ; Tue, 20 Aug 2013 19:18:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ho1B+jNpa2wmnecIEEWzNrcN7rJI9+EA24Xpoe6oRT0=; b=O5KZPyqNeSbFVapRt3oydGUz6tXrSySLAgezYmndd0wf5A0wT2A9nWCEyXSMUXVPSz i2wJpkLMgWKj5c4cpK1oStl4oGMmIbr+xF1Sc/DUF/DkBS6EpZPviseGN6pqpuC92C8b zV4r6vEZfZVZuT/6Lpcpz6FHGo8UqchaljtpRvI5Qfnsww63s32vyO6kcn7SjPUvjkxX rlY6dDqyo0auj6MtGPQM/vX0+Ezcm3LnJbSTCM33ckdUYsqjAG/gJKoeGeakqgc5dq9r GtX3EFtz2u2Xs4Tfnk1WgJJO7dv7RYblsuSDQ+jjNaQMk59y8gwvdad73MFRnAMXcEOV xFVw== X-Gm-Message-State: ALoCoQlp8L/HJiNkNUPU1PBL19qKBjUBbbavWUw52R2bDkAgH5/Lb7BI1LgXZtiDDFHh1ZYlXqbn MIME-Version: 1.0 X-Received: by 10.60.79.5 with SMTP id f5mr1489915oex.59.1377051533965; Tue, 20 Aug 2013 19:18:53 -0700 (PDT) Received: by 10.182.192.66 with HTTP; Tue, 20 Aug 2013 19:18:53 -0700 (PDT) Received: by 10.182.192.66 with HTTP; Tue, 20 Aug 2013 19:18:53 -0700 (PDT) In-Reply-To: References: Date: Tue, 20 Aug 2013 22:18:53 -0400 Message-ID: Subject: Re: Any Scenarios in which Views impose performance penalties From: Ricky Saltzer To: user@hive.apache.org Content-Type: multipart/alternative; boundary=089e01227e6c850f2504e46bcb22 X-Virus-Checked: Checked by ClamAV on apache.org --089e01227e6c850f2504e46bcb22 Content-Type: text/plain; charset=ISO-8859-1 Since this bug was in Impala's query planner, I'm sure Hive is unaffected. On Aug 20, 2013 10:15 PM, "Stephen Boesch" wrote: > > Thanks v much Ricky. Is this fixed in hive 0.11 - or going to be later > i.e. 0.12? > > > 2013/8/20 Ricky Saltzer > >> Although this is already fixed in the next and upcoming impala release, >> you might want to be aware of the following view limitation. >> >> https://issues.cloudera.org/browse/IMPALA-495 >> On Aug 20, 2013 7:16 PM, "Stephen Boesch" wrote: >> >>> Views should theoretically not incur performance penalties: they simply >>> represent queries. Are there situtions that things are "not that simple" - >>> i.e. views may actually result in different exeucution plans than the >>> underlying sql? >>> >>> Additionally, are there views-related bugs that we should be aware of >>> that would limit the occasions that we could use them? >>> >>> Thanks for the pointers. >>> >>> >>> > --089e01227e6c850f2504e46bcb22 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Since this bug was in Impala's query planner, I'm su= re Hive is unaffected.

On Aug 20, 2013 10:15 PM, "Stephen Boesch&q= uot; <javadba@gmail.com> wro= te:

Thanks v much Ricky. =A0Is this fixed in hive 0.1= 1 - or going to be later i.e. 0.12?
<= br>
2013/8/20 Ricky Saltzer <ricky@cloudera= .com>

Although this is already fixe= d in the next and upcoming impala release, you might want to be aware of th= e following view limitation.

https://issues.cloudera.org/browse/IMPALA-495

<= div>
On Aug 20, 2013 7:16 PM, "Stephen Boesch&qu= ot; <javadba@gmai= l.com> wrote:
Views should theoretically not incur performance penalties= : they simply represent queries. Are there situtions that things are "= not that simple" - i.e. views may actually result in different exeucut= ion plans than the underlying sql? =A0

Additionally, are there views-related bugs that we should be= aware of that would limit the occasions that we could use them?
=
Thanks for the pointers.



--089e01227e6c850f2504e46bcb22--