[
https://issues.apache.org/jira/browse/HBASE-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649476#comment-14649476
]
Michael Segel commented on HBASE-12853:
----------------------------------------
Andrew,
As you point out, it was a trivial solution and that was the point I was trying
to make, that you took the time to work on it.
As I've said repeatedly, I can't provide patches because the risks outweigh the
benefits. (Lets leave it at that.)
I guess at the time I wrote this enhancement request, I could have raised this
issue with a certain vendor's support team, then suggested that a certain
person call a certain person to ask that this get done... but that would have
been a waste of calling in a favor.
Again, either the committers or community sees the benefits and merits in
doing this... or you don't. It was a five minute thought that wasn't worth the
effort of diagramming out on a white board that solved a problem.
> distributed write pattern to replace ad hoc 'salting'
> -----------------------------------------------------
>
> Key: HBASE-12853
> URL: https://issues.apache.org/jira/browse/HBASE-12853
> Project: HBase
> Issue Type: New Feature
> Reporter: Michael Segel
> Fix For: 2.0.0
>
>
> In reviewing HBASE-11682 (Description of Hot Spotting), one of the issues is
> that while 'salting' alleviated regional hot spotting, it increased the
> complexity required to utilize the data.
> Through the use of coprocessors, it should be possible to offer a method
> which distributes the data on write across the cluster and then manages
> reading the data returning a sort ordered result set, abstracting the
> underlying process.
> On table creation, a flag is set to indicate that this is a parallel table.
> On insert in to the table, if the flag is set to true then a prefix is added
> to the key. e.g. <region server#>- or <region server #|| where the region
> server # is an integer between 1 and the number of region servers defined.
> On read (scan) for each region server defined, a separate scan is created
> adding the prefix. Since each scan will be in sort order, its possible to
> strip the prefix and return the lowest value key from each of the subsets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
