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

["Anoop Sam John (JIRA)" <ji...@apache.org>]

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

Anoop Sam John edited comment on HBASE-12853 at 7/29/15 5:45 PM:
-----------------------------------------------------------------

As per the discussion in the Jira comments, we can not do this as a server side feature. This will be a client side thing.  Priority can be marked minor or major that is not the main thing IMHO.  What matters is a small doc abt the approach and patch. Many of us will be happy to review that when it comes. As far as a feature is value added for the team,we all are open for those.   Are you going to work on this and give patch?   If not there is no point in keeping jira open.  We can see any one else willing to take this up. If none better close it as later/wont implement.  


was (Author: anoop.hbase):
As per the discussion in the Jira comments, we can not do this as a server side feature. This will be a client side thing.  Priority can be marked minor or major that is not the main thing IMHO.  What matters is the a small doc abt the approach and patch. Many of us will be happy to review that when it comes. As far as some feature are value added for the team,we all are open for those.   Are you going to work on this?   If not there is no point in keeping it open.  We can see any one else willing to take this up. If none better close it as later/wont implement.  

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