Alexey Serbin has posted comments on this change.

Change subject: new range partitioning features blog post
......................................................................


Patch Set 2:

(1 comment)

http://gerrit.cloudera.org:8080/#/c/4012/2/_posts/2016-08-18-new-range-partitioning-features.md
File _posts/2016-08-18-new-range-partitioning-features.md:

Line 63: unoccupied space. Dropping a range partition will result in unoccupied 
space
Just wanted to clarify on some imaginary example.

Dropping partition involves dropping the real data which 'bucketed' into the 
partition, doesn't it?  If so, what would be the right procedure for 
'sub-partitioning': suppose I have a table with timestamp column and the 
original partitioning was range-based on that column with one tablet per month 
partitioning.  Later on, when data began to accumulate, it became clear there 
should have been one tablet per day partitioning instead.  Is it possible to 
re-partition the table not dropping already accumulated data for the last 
month, so that the data would use the new tablet-per-day partitioning for data 
coming tomorrow and in the future?


-- 
To view, visit http://gerrit.cloudera.org:8080/4012
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I53504d849c2aca9ff613b11e67d1533536283931
Gerrit-PatchSet: 2
Gerrit-Project: kudu
Gerrit-Branch: gh-pages
Gerrit-Owner: Dan Burkert <d...@cloudera.com>
Gerrit-Reviewer: Adar Dembo <a...@cloudera.com>
Gerrit-Reviewer: Alexey Serbin <aser...@cloudera.com>
Gerrit-Reviewer: Dan Burkert <d...@cloudera.com>
Gerrit-Reviewer: Misty Stanley-Jones <mi...@apache.org>
Gerrit-Reviewer: Todd Lipcon <t...@apache.org>
Gerrit-HasComments: Yes

Reply via email to