You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Dan Burkert (JIRA)" <ji...@apache.org> on 2016/10/07 18:55:20 UTC

[jira] [Updated] (KUDU-1687) Range-partition naming

     [ https://issues.apache.org/jira/browse/KUDU-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Burkert updated KUDU-1687:
------------------------------
    Issue Type: New Feature  (was: Bug)

> Range-partition naming
> ----------------------
>
>                 Key: KUDU-1687
>                 URL: https://issues.apache.org/jira/browse/KUDU-1687
>             Project: Kudu
>          Issue Type: New Feature
>    Affects Versions: 1.0.0
>            Reporter: Dan Burkert
>
> It would be nice if individual range partitions could be named during creation, so that they can be dropped by name later.  For example, it would allow a SQL layer to do the following:
> {code}
> CREATE TABLE t (
>     c INT32 PRIMARY KEY,
> )
> PARTITION BY
>     RANGE (c) (
>         PARTITION first 100 <= VALUES < 200,
>         PARTITION second 300 <= VALUES < 400,
>     );
> ALTER TABLE t DROP RANGE PARTITION first;
> -- would be equivalent to:
> ALTER TABLE t DROP RANGE PARTITION 100 <= VALUES < 200;
> {code}
> Right now there is no state associated with range partitions in the master, so this may have to be approximated by adding per-tablet metadata, and then adding an associated range partition name to that.



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