org.mapdb.volume

Package org.mapdb.volume

Types

ByteArrayVol class ByteArrayVol : Volume

Created by jan on 2/29/16.

ByteBufferMemoryVol class ByteBufferMemoryVol : ByteBufferVol

Created by jan on 3/13/16.

ByteBufferMemoryVolSingle class ByteBufferMemoryVolSingle : ByteBufferVolSingle

Created by jan on 3/13/16.

ByteBufferVol abstract class ByteBufferVol : Volume

Abstract Volume over bunch of ByteBuffers It leaves ByteBufferVol details (allocation, disposal) on subclasses. Most methods are final for better performance (JIT compiler can inline those).

ByteBufferVolSingle abstract class ByteBufferVolSingle : Volume

Abstract Volume over single ByteBuffer, maximal size is 2GB (32bit limit). It leaves ByteBufferVol details (allocation, disposal) on subclasses. Most methods are final for better performance (JIT compiler can inline those).

FileChannelVol class FileChannelVol : Volume

Volume which uses FileChannel. Uses global lock and does not use mapped memory.

MappedFileVol class MappedFileVol : ByteBufferVol

Created by jan on 2/29/16.

MappedFileVolSingle class MappedFileVolSingle : ByteBufferVolSingle

Created by jan on 2/29/16.

RandomAccessFileVol class RandomAccessFileVol : Volume

Created by jan on 2/29/16.

ReadOnlyVolume class ReadOnlyVolume : Volume

Created by jan on 2/29/16.

ReadOnlyVolumeFactory class ReadOnlyVolumeFactory : VolumeFactory

Wraps volume factory and returns volume as readonly

SingleByteArrayVol class SingleByteArrayVol : Volume

Volume backed by on-heap byte[] with maximal fixed size 2GB. For thread-safety it can not be grown

Volume abstract class Volume : Closeable

MapDB abstraction over raw storage (file, disk partition, memory etc...).

Implementations needs to be thread safe (especially 'ensureAvailable') operation. However updates do not have to be atomic, it is clients responsibility to ensure two threads are not writing/reading into the same location.

VolumeFactory abstract class VolumeFactory

Created by jan on 2/29/16.