Package com.mchange.v1.cachedstore
Interface WritableCachedStore
- All Superinterfaces:
CachedStore
-
Nested Class Summary
Nested Classes -
Method Summary
Modifier and TypeMethodDescriptionvoidClears any pending (unflushed or failed) writes and removes.voidflushes writes to back end, IN NO PARTICULAR ORDER! (If you write a key twice, the second write reliably supercedes the first, however.) If this method fails, you can use getFailedWrites() to see what keys could not be written.voidvoidreset()Clears (WITHOUT WRITING) any pending (unflushed or failed) writes and removes, and any cached reads.voidsync()flushes writes and then clears cached reads.voidMethods inherited from interface com.mchange.v1.cachedstore.CachedStore
find
-
Method Details
-
write
- Throws:
CachedStoreException
-
remove
- Throws:
CachedStoreException
-
flushWrites
flushes writes to back end, IN NO PARTICULAR ORDER! (If you write a key twice, the second write reliably supercedes the first, however.) If this method fails, you can use getFailedWrites() to see what keys could not be written. Values that failed to write are still "pending": they will attempt to write on the next flush, and will still be read from the cache. Use clearPendingWrites() to avoid seeing or writing these values again.- Throws:
CacheFlushException
-
getFailedWrites
- Returns:
- null if all attempts to write to backend storage have succeeded, an unmodifiable Set of keys otherwise. failedWrites includes keys for whom a call to write or remove initially succeeded, but an attempt to flush the write to storage failed. A failed write may be any of an attempted first write, overwrite, or remove.
- Throws:
CachedStoreException
-
clearPendingWrites
Clears any pending (unflushed or failed) writes and removes.- Throws:
CachedStoreException
-
reset
Clears (WITHOUT WRITING) any pending (unflushed or failed) writes and removes, and any cached reads.- Specified by:
resetin interfaceCachedStore- Throws:
CachedStoreException
-
sync
flushes writes and then clears cached reads. On successful completion, the cache and the back-end store will be in sync with one another.- Throws:
CachedStoreException
-