[
https://issues.apache.org/jira/browse/HBASE-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384111#comment-14384111
]
Michael Segel commented on HBASE-12853:
----------------------------------------
To add to my comment in response to Anoop,
I wanted to abstract the concept of a scan from the application. Normally
you'd do this on the server side of the client/server split, however... w.r.t
HBase, this becomes a bit more difficult.
Ok...
So if I understand this.
Client passes scanner object to instance of table in the table.scan(scanner)
call.
So still on the client side, the client's table object will then connect with
the HMaster and determine which region and region server is required to start
the table scan, and then the client connects directly to the region and starts
the scan?
What do you call the scanner object that's running on the region?
> 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
> Priority: Minor
>
> 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)
