Dan Burkert has posted comments on this change.

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


Patch Set 3:

(18 comments)

updated rendering: 
http://danburkert.github.io/kudu/2016/08/18/new-range-partitioning-features.html

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:

PS2, Line 8: workloads,
> workloads?
Done


PS2, Line 43: divide a
> maybe 'divide'?
Done


PS2, Line 47: incre
> increases in value
Done


PS2, Line 49: nt
> typo: a strayed 'is'
Done


PS2, Line 49: 10 it has
> typo: an extra 'difficult'
Done


Line 63: unoccupied space. Dropping a range partition will result in unoccupied 
space
> Just wanted to clarify on some imaginary example.
No, that would be the range split feature described earlier.  What you can do 
is make narrower partitions going forward.


PS2, Line 66: in t
> into --> in ?
Done


PS2, Line 97: 
            : 
> Not sure I buy this example -- wouldn't different devices likely generate d
K, I've removed this section.  If you think I should rewrite it to be something 
like geographic areas I can do that.


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

PS3, Line 28: the split is not a clean break in the middle of the tablet.
> Can you explain this a little more? I think it's confusing to someone newer
Good idea, I've tried to make this better.  Let me know what you think.


PS3, Line 37: should not
> does not -- we're sure it doesn't preclude it, the question is just whether
Done


PS3, Line 44: the first and last
            : partition
> 'the first and last partitions', or 'the first partition and the last parti
Done


PS3, Line 46: range partitioned
> nit: range-partitioned
Done


PS3, Line 48: any other
> s/any other/in any other
Done


PS3, Line 48: Unbalanced partitions are commonly
            : referred to as hotspotting
> Hmm this sounds off to me. I think it needs to be 'unbalanced partitions ar
Done


PS3, Line 50: timeseries
> s/timeseries/time series (consistent with elsewhere)
Done


PS3, Line 66: lazily adding range partitions on the
            : fly
> 'lazily' + 'on the fly' is paradoxically redundant...I'm split over which I
Done


PS3, Line 80: a
> s/a/one
Done


PS3, Line 94: uesers
> typo: users
Done


-- 
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: 3
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-Reviewer: Will Berkeley <wdberke...@gmail.com>
Gerrit-HasComments: Yes

Reply via email to