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/08/16 17:47:22 UTC

[jira] [Commented] (KUDU-1458) truncate table support for kudu tables

    [ https://issues.apache.org/jira/browse/KUDU-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423146#comment-15423146 ] 

Dan Burkert commented on KUDU-1458:
-----------------------------------

A lot of the heavy lifting for this feature has recently been done as part of KUDU-1311 / KUDU-1421.  We now allow tablets to be dropped and added from running tables.  Doing a table truncate isn't quite as simple as dropping all of the range partitions and adding them back in one big alter step, because tables aren't necessarily range partitioned.  It would be sufficient to drop all tablets and add them back with the same partition key bounds, and the code should look very similar to the add/drop range partition code path.

> truncate table support for kudu tables
> --------------------------------------
>
>                 Key: KUDU-1458
>                 URL: https://issues.apache.org/jira/browse/KUDU-1458
>             Project: Kudu
>          Issue Type: New Feature
>          Components: impala, master
>            Reporter: nick
>
> truncate will come in handy to quickly erase the table. current delete statement takes long time when the record count is high.



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