hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liyin Tang (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4585) Avoid seek operation when current kv is deleted
Date Tue, 18 Oct 2011 05:40:10 GMT

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

Liyin Tang commented on HBASE-4585:
-----------------------------------

I have run all the unit tests. The following unit tests failed with and without the patch
of this jira.
TestAvroServer and TestDistributedLogSplitting

                
> Avoid seek operation when current kv is deleted
> -----------------------------------------------
>
>                 Key: HBASE-4585
>                 URL: https://issues.apache.org/jira/browse/HBASE-4585
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>             Fix For: 0.94.0
>
>         Attachments: hbase-4585-89.patch, hbase-4585-apache-trunk.patch
>
>
> When the current kv is deleted during the matching in the ScanQueryMatcher, currently
the matcher will return skip and continue to seek.
> Actually, if the current kv is deleted because of family deleted or column deleted, the
matcher should seek to next col.
> If the current kv is deleted because of version deleted, the matcher should just return
skip.

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