[
https://issues.apache.org/jira/browse/HBASE-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113858#comment-13113858
]
Lars Hofhansl commented on HBASE-4439:
--------------------------------------
Hmm... The new ClientScanner still modifies the passed Scan, so somebody using
ClientScanner directly would still get Scan modified. In order to avoid this,
Scan would have to be copied twice (since HTable also needs to copy it, because
it sets its caching on it, at least until we can remove {get|set}ScannerCaching
from HTable).
> Move ClientScanner out of HTable
> --------------------------------
>
> Key: HBASE-4439
> URL: https://issues.apache.org/jira/browse/HBASE-4439
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.94.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Minor
> Fix For: 0.94.0
>
> Attachments: 4439.txt
>
>
> See HBASE-1935 for motivation.
> ClientScanner should be able to exist outside of HTable.
> While we're at it, we can also add an abstract client scanner to easy
> development of new client side scanners (such as parallel scanners, or per
> region scanners).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
