[
https://issues.apache.org/jira/browse/HBASE-17081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702000#comment-15702000
]
Anoop Sam John commented on HBASE-17081:
----------------------------------------
IMO also having an extension of ImmutableSegment, like
COmpositeImmutableSegment is ideal and perfect.. But then it has to act like
a Segment. But we dont. At usage places, we rely on getter to retrieve all
individual ImmutableSegments.. So what I was wondering is
List<ImmutableSegment> way will be better than this.. Am not saying List is
good.. But better :-)
getCellSet() ideally why an ImmutableSegment has to expose this? May be after
some other clean up we will be able to do this Composite way.
So I will leave it to you all.. If all others feel it is ok, am not opposing
it.. I can work on that later to make the CompositeImmutableSegment to be a
real Segment.. (Or Ram or any of you if you wish)
> Flush the entire CompactingMemStore content to disk
> ---------------------------------------------------
>
> Key: HBASE-17081
> URL: https://issues.apache.org/jira/browse/HBASE-17081
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anastasia Braginsky
> Assignee: Anastasia Braginsky
> Attachments: HBASE-17081-V01.patch, HBASE-17081-V02.patch,
> HBASE-17081-V03.patch, Pipelinememstore_fortrunk_3.patch
>
>
> Part of CompactingMemStore's memory is held by an active segment, and another
> part is divided between immutable segments in the compacting pipeline. Upon
> flush-to-disk request we want to flush all of it to disk, in contrast to
> flushing only tail of the compacting pipeline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
