Return-Path: Delivered-To: apmail-hadoop-common-commits-archive@www.apache.org Received: (qmail 9589 invoked from network); 9 Feb 2011 23:28:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Feb 2011 23:28:39 -0000 Received: (qmail 38081 invoked by uid 500); 9 Feb 2011 23:28:38 -0000 Delivered-To: apmail-hadoop-common-commits-archive@hadoop.apache.org Received: (qmail 38012 invoked by uid 500); 9 Feb 2011 23:28:38 -0000 Mailing-List: contact common-commits-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-commits@hadoop.apache.org Received: (qmail 38005 invoked by uid 500); 9 Feb 2011 23:28:38 -0000 Delivered-To: apmail-hadoop-core-commits@hadoop.apache.org Received: (qmail 38002 invoked by uid 99); 9 Feb 2011 23:28:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Feb 2011 23:28:38 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.131] (HELO eos.apache.org) (140.211.11.131) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Feb 2011 23:28:37 +0000 Received: from eosnew.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id EFC4A885; Wed, 9 Feb 2011 23:28:09 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: Apache Wiki To: Apache Wiki Date: Wed, 09 Feb 2011 23:28:09 -0000 Message-ID: <20110209232809.99046.96183@eosnew.apache.org> Subject: =?utf-8?q?=5BHadoop_Wiki=5D_Update_of_=22Hive/PartitionedViews=22_by_John?= =?utf-8?q?Sichi?= Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for ch= ange notification. The "Hive/PartitionedViews" page has been changed by JohnSichi. http://wiki.apache.org/hadoop/Hive/PartitionedViews?action=3Ddiff&rev1=3D11= &rev2=3D12 -------------------------------------------------- = =3D Use Cases =3D = - 1. An administrator wants to create a set of views as a table/column ren= aming layer on top of an existing set of base tables, without disturbing th= e ETL processes which load those tables. To read-only users, the views sho= uld behave exactly the same as the underlying tables in every way. Among o= ther things, this means users should be able to browse available partitions. + 1. An administrator wants to create a set of views as a table/column ren= aming layer on top of an existing set of base tables, without breaking any = existing dependencies on those tables. To read-only users, the views shoul= d behave exactly the same as the underlying tables in every way. Among oth= er things, this means users should be able to browse available partitions. 1. A base table is partitioned on columns (ds,hr) for date and hour. Be= sides this fine-grained partitioning, users would also like to see a virtua= l table of coarse-grained (date-only) partitioning in which the partition f= or a given date only appears after all of the hour-level partitions of that= day have been fully loaded. 1. A view is defined on a complex join+union+aggregation of a number of = underlying base tables and other views, all of which are themselves partiti= oned. The top-level view should also be partitioned accordingly, with a ne= w partition not appearing until corresponding partitions have been loaded f= or all of the underlying tables. =20