hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Baranau (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-2038) Coprocessors: Region level indexing
Date Mon, 06 Feb 2012 17:58:11 GMT

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

Alex Baranau commented on HBASE-2038:

Hi Anoop,

I think your Q in second paragraph denotes the same concern that was stated in one of my first
comments (a year ago..):

bq. 2) During batch scan (smth which was added in trunk but wasn't supported in previous HBase
versions, and hence current IHBase implementation doesn't take it into account) we need to
return multiple rows from scan's next() method. It looks like if we apply current approach
(from current IHBase implementation) of "fast forwarding" to next value we'll only fastforward
scan to the first value of those to return. Others will be fetched using "usual" scan logic
without using index which isn't efficient. There's not a lot we can do without changing scan
(and deeper) code. Am I right here? Perhaps it's ok to have a lack of support for batch reads
for the first version of CP-based IHBase? Or, it might me that we should change the approach?

I'm reviewing the released 0.92 coprocessors capabilities, will share if I find how this issue
can be solved. But from what I see so far this issue remained in a released version...
> Coprocessors: Region level indexing
> -----------------------------------
>                 Key: HBASE-2038
>                 URL: https://issues.apache.org/jira/browse/HBASE-2038
>             Project: HBase
>          Issue Type: New Feature
>          Components: coprocessors
>            Reporter: Andrew Purtell
>            Priority: Minor
> HBASE-2037 is a good candidate to be done as coprocessor. It also serve as a good goalpost
for coprocessor environment design -- there should be enough of it so region level indexing
can be reimplemented as a coprocessor without any loss of functionality. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message