Package com.bigdata.bfs

This package provides a scale-out content repository (aka distributed file system) suitable as the backend for a REST-ful service using the bigdata architecture.

See:
Description

Interface Summary

BigdataFileSystem.Options	Configuration options.
Document	Document model interface for operations on the IContentRepository.
DocumentHeader	Document header interface for Documents stored in the IContentRepository.
IContentRepository	Document-centric interface for the BigdataFileSystem.

Class Summary

AtomicBlockAppendProc	Atomic append of a single block to a file version.
AtomicBlockWriteProc	Atomic write of a single block for a file version.
BigdataFileSystem	A distributed file system with extensible metadata and atomic append implemented using the bigdata scale-out architecture.
BlobOverflowHandler	Copies blocks onto the target store during overflow handling.
BlockIdentifierIterator	Extracts the block identifier from the key.
DocumentHeaderImpl	Flyweight DocumentHeader implementation.
DocumentImpl	Flyweight document implementation.
FileMetadataSchema	The schema for metadata about file versions stored in the BigdataFileSystem.
FileVersionDeleter	A procedure that performs a key range scan, marking all non-deleted versions within the key range as deleted (by storing a null property value for the FileMetadataSchema.VERSION).
FileVersionInputStream	Reads from blocks visited by a range scan for a file and version.
FileVersionOutputStream	Class buffers up to a block of data at a time and flushes blocks using an atomic append operation on the identifier file version.
GlobalFileSystemHelper	Helper class.
RepositoryDocumentImpl	A read-only view of a Document that has been read from a BigdataFileSystem.

Exception Summary

ExistsException	Thrown when the identified document already exists.
NotFoundException	Thrown when the identified document was not found.

Package com.bigdata.bfs Description

This package provides a scale-out content repository (aka distributed file system) suitable as the backend for a REST-ful service using the bigdata architecture. Content is arbitrary byte[]s broken down into chunks of up to 64M each. Basic and extensible metadata may be stored for any given item of content. Atomic operations on chunks are provided for reading, writing, deleting, etc. The architecture is designed for interoperation with map / reduce style processing.