You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Manukranth Kolloju (JIRA)" <ji...@apache.org> on 2013/03/23 02:02:10 UTC
[jira] [Commented] (HBASE-8185) Feature to enable Client Side
Scanning(Client side merging) in HBase.
[ https://issues.apache.org/jira/browse/HBASE-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611496#comment-13611496 ]
Manukranth Kolloju commented on HBASE-8185:
-------------------------------------------
The motivation of this was to enable the client to be able to open the region scanner and perform the merge on the client side. This will lower the cpu ops that are consumed by the RegionServer. In cases where the user is interested to perform a large scan on hbase data check-pointed at a point of time, we think that this would give a very high throughput as compared to using the ClientScanner in HTable.
One idea was to create a ReadOnlyHRegion, but that idea seemed to be too HeavyWeight though it require lesser code change.
The other way was to create an abstraction of a ReadOnlyStore, and open these read only stores in the client side. This list of stores is used to open a RegionScanner and then used to serve the user through a ResultScanner directly.
> Feature to enable Client Side Scanning(Client side merging) in HBase.
> ---------------------------------------------------------------------
>
> Key: HBASE-8185
> URL: https://issues.apache.org/jira/browse/HBASE-8185
> Project: HBase
> Issue Type: New Feature
> Components: regionserver
> Affects Versions: 0.89-fb
> Reporter: Manukranth Kolloju
> Fix For: 0.89-fb
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In order to reuse the RegionScanner class without instantiating the HRegion class, we will have to bring RegionScanner class outside HRegion. This is a preliminary diff to another feature called Client Side Scanning.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira