[
https://issues.apache.org/jira/browse/HBASE-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634663#comment-13634663
]
Lars Hofhansl commented on HBASE-8362:
--------------------------------------
Then of course every Get can have its own timerange and filter, so the cases
where this can be used is more limited than I had thought. I suppose one could
Gets by timerange and filter, or only do this for Gets without timerange/filter
specified.
Maybe this is dud.
I'll think about this a bit more and then either provide a patch or close as
"Another-nonsense-LarsH-idea".
> Possible MultiGet optimization
> ------------------------------
>
> Key: HBASE-8362
> URL: https://issues.apache.org/jira/browse/HBASE-8362
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
>
> Currently MultiGets are executed on a RegionServer in a single thread in a
> loop that handles each Get separately (opening a scanner, seeking, etc).
> It seems we could optimize this (per region at least) by opening a single
> scanner and issue a reseek for each Get that was requested.
> I have not tested this yet and no patch, but I would like to solicit feedback
> on this idea.
--
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
