[jira] [Commented] (HBASE-12853) distributed write pattern to replace ad hoc 'salting'

["Ian Michael Gumby (JIRA)" <ji...@apache.org>]

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

Ian Michael Gumby commented on HBASE-12853:
-------------------------------------------

Wow, 

Rather than try to stay focused on the issue of the Jira, you talk about contributing to open source. 

I can tell you the answer, I can even explain it to you, but you still wouldn't get it. 



> 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)