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

Enis Soztutar commented on HBASE-8185:
--------------------------------------

Related, one idea I was entertaining is to be able to scan from snapshot's 
directly and do the client side scanning from mapreduce jobs. Snapshots will 
also be a good initial target to introduce this, since we would not have to 
deal with memstore updates. Snapshot will also naturally be read only. 
Full table scans from mapreduce jobs then become, 1. take a lightweight 
snapshot, 2. scan from MR using local scanners without touching the hbase 
daemons. 
                
> 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: 168h
>  Remaining Estimate: 168h
>
> The motivation of this was to enable the client to be able to open the region 
> scanner(and in turn open StoreScanners) and perform the merge on the client 
> side. This will lower the cpu ops that are consumed by the RegionServer since 
> the data is pulled directly from the datanode. 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 ClientSideScan(ClientSideMerge) would give a very high 
> throughput as compared to using the ClientScanner in HTable.

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

Reply via email to