Package voldemort.store

The Store interface is the primary interface for Voldemort.

See:
Description

Interface Summary

StorageConfiguration	An abstraction that represents the shared resources of a persistence engine.
StorageEngine<K,V>	A base storage class which is actually responsible for data persistence.
Store<K,V>	The basic interface used for storage and storage decorators.

Class Summary

DelegatingStore<K,V>	A Store template that delegates all operations to an inner store.
ErrorCodeMapper	Map error codes to exceptions and vice versa
StoreDefinition	The configuration information for a store.
StoreDefinitionBuilder	A simple builder class to avoid having 10k constructor parameters in store definitions
StoreUtils	Check that the given key is valid

Enum Summary

StoreCapabilityType

Exception Summary

InsufficientOperationalNodesException	Thrown if an operation fails due to too few reachable nodes.
InvalidMetadataException	Store should throw this Exception to indicate that the metadata (Cluster configuration/ Stores Configuration) at client is not in sync with this store metadata.
NoSuchCapabilityException	Exception thrown if the user attempts to retrieve a capability that the store does not provide.
PersistenceFailureException	Thrown by the StorageEngine if storage fails
StorageInitializationException	This exception indicates that the server was unable to initialize on or more storage services or stores within a service.
StoreOperationFailureException	Thrown to indicate the failure of some store operation (put, get, delete)
UnknownFailure	When we don't know what the hell happened, call it one of these.
UnreachableStoreException	Indicates that the given store cannot be reached (say, due to network failure).

Package voldemort.store Description

The Store interface is the primary interface for Voldemort. Stores provide functionality by implementing put, get, and delete from scratch or by decorating existing stores with additional capabilities. Implementations of this interface provide the network i/o layer, the various persistence layers, layers that deal with version conflicts, layers for logging and performance monitoring, etc.