[
https://issues.apache.org/jira/browse/KUDU-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-819.
------------------------------
Resolution: Duplicate
Fix Version/s: n/a
This got broken out in subtasks of KUDU-1306
> Allow explicit management of tablet creation/deletion
> -----------------------------------------------------
>
> Key: KUDU-819
> URL: https://issues.apache.org/jira/browse/KUDU-819
> Project: Kudu
> Issue Type: New Feature
> Components: api, client, master
> Affects Versions: Private Beta
> Reporter: Todd Lipcon
> Priority: Critical
> Fix For: n/a
>
>
> This is a feature that has been requested by Xiaomi for some time. There are
> a couple parts:
> 1) Allow a table to be created whose tablets don't span the whole key range.
> This probably has an API change involved.
> 2) Teach the client to deal with the case where an operation touches a key
> which falls outside of any tablets. Initially, we can reject such operations.
> 3) Add admin APIs to explicitly create/drop tablets, or convert tablets to
> tables.
> 4) Lower priority: add a facility by which a "catch-all" table can be defined
> which receives inserts/updates which failed to match any tablet in a table.
> Manual partition management is a reasonable way to manage time series
> workloads in particular.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
