hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8362) Possible MultiGet optimization
Date Thu, 18 Apr 2013 01:19:16 GMT

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

Varun Sharma commented on HBASE-8362:

Actually, I think we could support running multi get where all gets have the same filter.
Like say retrieve multi rows but then columns with a certain prefix for all those rows. That
might be doable (if we can have this new filter play nice with the Column* filters).

Right now, it seems that we initialize our scanners with a predefined set of filters which
can't be changed throughout their lifetime. If that behaviour was easy to change 1) We could
seek across rows using a MultiRowFilter 2) Seek within rows using the specific Get filters
to each Get. It seems doable at the surface but I am the sure the devil is in the details...

> 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

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

View raw message