hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16013) In-memory Compaction process can be improved for a default case
Date Wed, 22 Jun 2016 09:25:58 GMT

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

Ted Yu commented on HBASE-16013:
--------------------------------

{code}
354	  // TODO : Handle backward scanner
355	  public static class MemStoreIterator implements Iterator<Cell> {
{code}
The class can be of package scope, right ?
When would the backward scan be supported ?
{code}
372	      } catch (IOException e) {
373	        // throw error out? ideally no error should be thrown here
{code}
I think the error should be thrown out.

> In-memory Compaction process can be improved for a default case
> ---------------------------------------------------------------
>
>                 Key: HBASE-16013
>                 URL: https://issues.apache.org/jira/browse/HBASE-16013
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16013.patch, HBASE-16013_1.patch
>
>
> There is an ongoing discussion on how to handle the default case (no duplicates/deletes)
and how to use the new CompactingMemstore in such a case.
> One improvement is to avoid the StoreScanner and go with a simple MemstoreScanner. This
avoids lot of comparisons that the StoreScanner does. Just raising this sub-task as part of
some analysis going on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message