hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16143) Change MemstoreScanner constructor to accept List<KeyValueScanner>
Date Wed, 29 Jun 2016 09:00:25 GMT

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

Anoop Sam John commented on HBASE-16143:

bq.list.add(pos, getActive().getSegmentScanner(readPt, order+1));
Why use pos based add?  It is ArrayList we know so we will get insert order. It is fine to
just call add(<element>)

Where do u use MemstoreScanner now? Previous it was returning one MemstoreScanner to the StoreScannr
layer.Now it is N  KVScanners?  Intended change?

> Change MemstoreScanner constructor to accept List<KeyValueScanner>
> ------------------------------------------------------------------
>                 Key: HBASE-16143
>                 URL: https://issues.apache.org/jira/browse/HBASE-16143
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Minor
>             Fix For: 2.0.0
>         Attachments: HBASE-16143.patch, HBASE-16143_1.patch
> A minor change that helps in creating a memstore that avoids the compaction process and
just allows to creates a pipeline of segments and on flush directly reads the segments in
the pipeline and flushes it out after creating a snapshot of the pipeline. Based on test results
and updated patch on HBASE-14921 (to be provided) will see how much flattening helps us.

This message was sent by Atlassian JIRA

View raw message