hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5512) Add support for INCLUDE_AND_SEEK_USING_HINT
Date Mon, 05 Mar 2012 12:08:57 GMT

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

Anoop Sam John commented on HBASE-5512:
---------------------------------------

@Lars
      As u said under HBASE_2038 I dont think we can use this way to do the IHBase work :(
 Mainly how the filter can return INCLUDE_AND_SEEK..   WHat we wanted ideally is at the row
level say include this row and seek to next row. But any way at row level the filter contains
boolean return either include the row or not.

I feel making an attempt to support the seek() reseek() at the region scanner level..
                
> Add support for INCLUDE_AND_SEEK_USING_HINT
> -------------------------------------------
>
>                 Key: HBASE-5512
>                 URL: https://issues.apache.org/jira/browse/HBASE-5512
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Zhihong Yu
>            Assignee: Lars Hofhansl
>         Attachments: 5512-v2.txt, 5512.txt
>
>
> This came up from HBASE-2038
> From Anoop:
> - What we wanted from the filter is include a row and then seek to the next row which
we are interested in. I cant see such a facility with our Filter right now. Correct me if
I am wrong. So suppose we already seeked to one row and this need to be included in the result,
then the Filter should return INCLUDE. Then when the next next() call happens, then only we
can return a SEEK_USING_HINT. So one extra row reading is needed. This might create even one
unwanted HFileBlock fetch (who knows).
> Can we add reseek() at higher level?
> From Lars:
> Yep, for that we'd need to add INCLUDE_AND_SEEK_USING_HINT (similar to the INCLUDE_AND_SEEK_NEXT_ROW
that we already have). Shouldn't be hard to add, I'm happy to do that, if that's the route
we want to go with this.

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

        

Mime
View raw message