[
https://issues.apache.org/jira/browse/HBASE-11682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102867#comment-14102867
]
Nick Dimiduk commented on HBASE-11682:
--------------------------------------
Very well articulated example, I like it! [~jmhsieh] you're right in that I
don't think of using random data for a prefix because the nondeterminism makes
gets ineffective. It is, however, a valid approach.
{noformat}
+ <para>Suppose you have the following list of row keys:</para>
{noformat}
This example assumes the table is split in a way such that f* would be in a
single region but a-, b-, c-, d- are in different regions. Be explicit about
the region splits, include a sentence like "assume your table is split by
letter, so the rowkey prefix {{a}} is on one region, {{b}} is on a second,
{{c}} on a 3rd, &c." In that topology, then all the foo rows would be in the
same region, and the prefixed rows are in different regions.
{noformat}
+ <title>Hashing</title>
{noformat}
For this bit, you can add something like "using a deterministic hash allows the
client to reconstruct the complete rowkey and use a get operation to retrieve
that row as normal." The current text alludes to this, but maybe we can some
out and say it explicitly.
For references, you could also link off to Phoenix's "Salted Tables"
description http://phoenix.apache.org/salted.html
> Explain hotspotting
> -------------------
>
> Key: HBASE-11682
> URL: https://issues.apache.org/jira/browse/HBASE-11682
> Project: HBase
> Issue Type: Task
> Components: documentation
> Reporter: Misty Stanley-Jones
> Assignee: Misty Stanley-Jones
> Attachments: HBASE-11682-1.patch, HBASE-11682.patch,
> HBASE-11682.patch, HBASE-11682.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
