Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 13 Nov 2015 02:38:11 +0000 (UTC)
From: "Gopal V (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12855369.1439330852000.57994.1447382291080@Atlassian.JIRA>
In-Reply-To: <JIRA.12855369.1439330852000@Atlassian.JIRA>
References: <JIRA.12855369.1439330852000@Atlassian.JIRA>
 <JIRA.12855369.1439330852466@arcas>
Subject: [jira] [Updated] (HIVE-11525) Bucket pruning
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HIVE-11525?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gopal V updated HIVE-11525:
---------------------------
    Labels: TODOC2.0  (was: )

> Bucket pruning
> --------------
>
>                 Key: HIVE-11525
>                 URL: https://issues.apache.org/jira/browse/HIVE-11525
>             Project: Hive
>          Issue Type: Improvement
>          Components: Logical Optimizer
>    Affects Versions: 0.13.0, 0.14.0, 0.13.1, 1.0.0, 1.2.0, 1.1.0, 1.3.0, =
2.0.0
>            Reporter: Maciek Kocon
>            Assignee: Gopal V
>              Labels: TODOC2.0
>             Fix For: 2.0.0
>
>         Attachments: HIVE-11525.1.patch, HIVE-11525.2.patch, HIVE-11525.3=
.patch, HIVE-11525.WIP.patch
>
>
> Logically and functionally bucketing and partitioning are quite similar -=
 both provide mechanism to segregate and separate the table's data based on=
 its content. Thanks to that significant further optimisations like [partit=
ion] PRUNING or [bucket] MAP JOIN are possible.
> The difference seems to be imposed by design where the PARTITIONing is op=
en/explicit while BUCKETing is discrete/implicit.
> Partitioning seems to be very common if not a standard feature in all cur=
rent RDBMS while BUCKETING seems to be HIVE specific only.
> In a way BUCKETING could be also called by "hashing" or simply "IMPLICIT =
PARTITIONING".
> Regardless of the fact that these two are recognised as two separate feat=
ures available in Hive there should be nothing to prevent leveraging same e=
xisting query/join optimisations across the two.
> BUCKET pruning
> Enable partition PRUNING equivalent optimisation for queries on BUCKETED =
tables
> Simplest example is for queries like:
> "SELECT =E2=80=A6 FROM x WHERE colA=3D123123"
> to read only the relevant bucket file rather than all file-buckets that b=
elong to a table.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)