Uses of Class
org.apache.hadoop.hbase.regionserver.MutableSegment

Packages that use MutableSegment

Package	Description
org.apache.hadoop.hbase.regionserver

Uses of MutableSegment in org.apache.hadoop.hbase.regionserver

Methods in org.apache.hadoop.hbase.regionserver that return MutableSegment

Modifier and Type	Method and Description
MutableSegment	SegmentFactory.createMutableSegment(org.apache.hadoop.conf.Configuration conf, CellComparator comparator, MemStoreSizing memstoreSizing)

Methods in org.apache.hadoop.hbase.regionserver with parameters of type MutableSegment

Modifier and Type	Method and Description
protected boolean	CompactingMemStore.checkAndAddToActiveSize(MutableSegment currActive, Cell cellToAdd, MemStoreSizing memstoreSizing) Check whether anything need to be done based on the current active set size.
ImmutableSegment	SegmentFactory.createImmutableSegment(MutableSegment segment, MemStoreSizing memstoreSizing)
protected void	AbstractMemStore.doAdd(MutableSegment currentActive, Cell cell, MemStoreSizing memstoreSizing)
protected void	CompactingMemStore.flushInMemory(MutableSegment currActive)
protected void	DefaultMemStore.postUpdate(MutableSegment currentActive)
protected abstract void	AbstractMemStore.postUpdate(MutableSegment currentActive) Issue any post update synchronization and tests
protected void	CompactingMemStore.postUpdate(MutableSegment currentActive)
protected boolean	DefaultMemStore.preUpdate(MutableSegment currentActive, Cell cell, MemStoreSizing memstoreSizing)
protected abstract boolean	AbstractMemStore.preUpdate(MutableSegment currentActive, Cell cell, MemStoreSizing memstoreSizing) Issue any synchronization and test needed before applying the update
protected boolean	CompactingMemStore.preUpdate(MutableSegment currentActive, Cell cell, MemStoreSizing memstoreSizing) Issue any synchronization and test needed before applying the update For compacting memstore this means checking the update can increase the size without overflow
protected void	CompactingMemStore.pushActiveToPipeline(MutableSegment currActive, boolean checkEmpty) NOTE: When CompactingMemStore.flushInMemory(MutableSegment) calls this method, due to concurrent writes and because we first add cell size to currActive.getDataSize and then actually add cell to currActive.cellSet, it is possible that currActive.getDataSize could not accommodate cellToAdd but currActive.cellSet is still empty if pending writes which not yet add cells to currActive.cellSet,so for CompactingMemStore.flushInMemory(MutableSegment),checkEmpty parameter is false.
boolean	CompactionPipeline.pushHead(MutableSegment segment)