[
https://issues.apache.org/jira/browse/HBASE-16013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345718#comment-15345718
]
ramkrishna.s.vasudevan commented on HBASE-16013:
------------------------------------------------
Thanks Ted.
bq.The class can be of package scope, right ?
Yes. It can be changed.
bq.When would the backward scan be supported ?
I don't think we need to support it yet. Lets see if this iterator is going to
be used in normal backward scans also. Ideally it cannot be used.
bq.I think the error should be thrown out.
Ok. But this whole patch is only for discussion and not for committing. In a
default case we don't need a scanner which uses the matcher. So this is just to
show how easily we can iterate thro the memstore segment scanners.
> 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)
