Class BerkeleyKVTransaction
- All Implemented Interfaces:
KVStore
,KVTransaction
,Closeable
,AutoCloseable
KVTransaction
implementation.-
Nested Class Summary
Modifier and TypeClassDescriptionfinal class
Iterator
implementation used byBerkeleyKVTransaction.getRange()
. -
Method Summary
Modifier and TypeMethodDescriptionvoid
close()
void
commit()
Commit this transaction.protected void
finalize()
byte[]
get
(byte[] key) Get the value associated with the given key, if any.getAtLeast
(byte[] minKey, byte[] maxKey) Get the key/value pair having the smallest key greater than or equal to the given minimum, if any.getAtMost
(byte[] maxKey, byte[] minKey) Get the key/value pair having the largest key strictly less than the given maximum, if any.Get theKVDatabase
with which this instance is associated.getRange
(byte[] minKey, byte[] maxKey, boolean reverse) Iterate the key/value pairs in the specified range.com.sleepycat.je.Transaction
Get the underlyingTransaction
associated with this instance.boolean
Determine whether this transaction is read-only.void
put
(byte[] key, byte[] value) Set the value associated with the given key.Create a read-only snapshot of the database content represented by this transaction.void
remove
(byte[] key) Remove the key/value pair with the given key, if it exists.void
rollback()
Cancel this transaction, if not already canceled.void
setReadOnly
(boolean readOnly) Enable or disable read-only mode.void
setTimeout
(long timeout) Change the timeout for this transaction from its default value (optional operation).watchKey
(byte[] key) Watch a key to monitor for changes in its value.wrapException
(com.sleepycat.je.DatabaseException e) Wrap the givenDatabaseException
in the appropriateKVTransactionException
.Methods inherited from class io.permazen.kv.AbstractKVStore
adjustCounter, decodeCounter, encodeCounter, removeRange
Methods inherited from class java.lang.Object
clone, equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
Methods inherited from interface io.permazen.kv.KVStore
adjustCounter, apply, decodeCounter, encodeCounter, getRange, getRange, removeRange, removeRange
Methods inherited from interface io.permazen.kv.KVTransaction
withWeakConsistency
-
Method Details
-
getKVDatabase
Description copied from interface:KVTransaction
Get theKVDatabase
with which this instance is associated.- Specified by:
getKVDatabase
in interfaceKVTransaction
- Returns:
- associated database
-
getTransaction
public com.sleepycat.je.Transaction getTransaction()Get the underlyingTransaction
associated with this instance.- Returns:
- the associated transaction
-
setTimeout
public void setTimeout(long timeout) Description copied from interface:KVTransaction
Change the timeout for this transaction from its default value (optional operation).- Specified by:
setTimeout
in interfaceKVTransaction
- Parameters:
timeout
- transaction timeout in milliseconds, or zero for unlimited
-
watchKey
Watch a key to monitor for changes in its value.Oracle Berkeley DB Java Edition does not support key watches; the implementation in
BerkeleyKVDatabase
always throwsUnsupportedOperationException
.- Specified by:
watchKey
in interfaceKVTransaction
- Parameters:
key
- the key to watch- Returns:
- a
Future
that returnskey
when the value associated withkey
is modified - Throws:
UnsupportedOperationException
- always- See Also:
-
get
public byte[] get(byte[] key) Description copied from interface:KVStore
Get the value associated with the given key, if any.Modifications to the returned
byte[]
array do not affect this instance.- Specified by:
get
in interfaceKVStore
- Overrides:
get
in classAbstractKVStore
- Parameters:
key
- key- Returns:
- value associated with key, or null if not found
-
getAtLeast
Description copied from interface:KVStore
Get the key/value pair having the smallest key greater than or equal to the given minimum, if any.An optional (exclusive) maximum key may also be specified; if
maxKey
is null, there is no upper bound; ifmaxKey <= minKey
, null is always returned.If keys starting with
0xff
are not supported by this instance, andminKey
starts with0xff
, then this method returns null.Modifications to the returned
byte[]
arrays do not affect this instance.- Specified by:
getAtLeast
in interfaceKVStore
- Overrides:
getAtLeast
in classAbstractKVStore
- Parameters:
minKey
- minimum key (inclusive), or null for no minimum (get the smallest key)maxKey
- maximum key (exclusive), or null for no maximum (no upper bound)- Returns:
- smallest key/value pair with
key >= minKey
andkey < maxKey
, or null if none exists
-
getAtMost
Description copied from interface:KVStore
Get the key/value pair having the largest key strictly less than the given maximum, if any.An optional (inclusive) minimum key may also be specified; if
minKey
is null, there is no lower bound (equivalent to a lower bound of the empty byte array); ifminKey >= maxKey
, null is always returned.If keys starting with
0xff
are not supported by this instance, andmaxKey
starts with0xff
, then this method behaves as ifmaxKey
were null.Modifications to the returned
byte[]
arrays do not affect this instance.- Specified by:
getAtMost
in interfaceKVStore
- Overrides:
getAtMost
in classAbstractKVStore
- Parameters:
maxKey
- maximum key (exclusive), or null for no maximum (get the largest key)minKey
- minimum key (inclusive), or null for no minimum (no lower bound)- Returns:
- largest key/value pair with
key < maxKey
andkey >= minKey
, or null if none exists
-
getRange
Description copied from interface:KVStore
Iterate the key/value pairs in the specified range. The returnedCloseableIterator
'sremove()
method must be supported and should have the same effect as invokingremove()
on the corresponding key.If keys starting with
0xff
are not supported by this instance, andminKey
starts with0xff
, then this method returns an empty iteration.If keys starting with
0xff
are not supported by this instance, andmaxKey
starts with0xff
, then this method behaves as ifmaxKey
were null.The returned
CloseableIterator
is weakly consistent (seejava.util.concurrent
). In short, the returnedCloseableIterator
must not throwConcurrentModificationException
; however, whether or not a "live"CloseableIterator
reflects any modifications made after its creation is implementation dependent. Implementations that do make post-creation updates visible in theCloseableIterator
, even if the update occurs after some delay, must preserve the order in which the modifications actually occurred.The returned
CloseableIterator
itself is not guaranteed to be thread safe; is should only be used in the thread that created it.Invokers of this method are encouraged to
close()
the returned iterators, though this is not required for correct behavior.Modifications to the returned
KVPair
key and valuebyte[]
arrays do not affect this instance.- Specified by:
getRange
in interfaceKVStore
- Parameters:
minKey
- minimum key (inclusive), or null for no minimum (start at the smallest key)maxKey
- maximum key (exclusive), or null for no maximum (end at the largest key)reverse
- true to return key/value pairs in reverse order (i.e., keys descending)- Returns:
- iteration of key/value pairs in the range
minKey
(inclusive) tomaxKey
(exclusive)
-
put
public void put(byte[] key, byte[] value) Description copied from interface:KVStore
Set the value associated with the given key.- Specified by:
put
in interfaceKVStore
- Overrides:
put
in classAbstractKVStore
- Parameters:
key
- keyvalue
- value
-
remove
public void remove(byte[] key) Description copied from interface:KVStore
Remove the key/value pair with the given key, if it exists.- Specified by:
remove
in interfaceKVStore
- Overrides:
remove
in classAbstractKVStore
- Parameters:
key
- key
-
isReadOnly
public boolean isReadOnly()Description copied from interface:KVTransaction
Determine whether this transaction is read-only.Default is false.
- Specified by:
isReadOnly
in interfaceKVTransaction
- Returns:
- true if this instance is read-only
-
setReadOnly
public void setReadOnly(boolean readOnly) Description copied from interface:KVTransaction
Enable or disable read-only mode.Read-only transactions allow mutations, but all changes are discarded on
KVTransaction.commit()
.Some implementations may impose one or more of the following restrictions on this method:
setReadOnly()
may only be invoked prior to accessing data;setReadOnly()
may only be invoked prior to mutating data; and/or- Once set to read-only, a transaction may not be set back to read-write
IllegalStateException
is thrown.Note: for some implementations, the data read from a transaction that is never
KVTransaction.commit()
'ed is not guaranteed to be up to date, even if that transaction is read-only.Default is false.
- Specified by:
setReadOnly
in interfaceKVTransaction
- Parameters:
readOnly
- read-only setting
-
commit
public void commit()Description copied from interface:KVTransaction
Commit this transaction.Note that if this method throws a
RetryKVTransactionException
, the transaction was either successfully committed or rolled back. In either case, this instance is no longer usable.Note also for some implementations, even read-only transactions must be
KVTransaction.commit()
'ed in order for the data accessed during the transaction to be guaranteed to be up to date.- Specified by:
commit
in interfaceKVTransaction
-
rollback
public void rollback()Description copied from interface:KVTransaction
Cancel this transaction, if not already canceled.After this method returns, this instance is no longer usable.
Note: for some implementations, rolling back a transaction invalidates guarantees about the the data read during the transaction being up to date, even if the transaction was
setReadOnly()
.This method may be invoked at any time, even after a previous invocation of
KVTransaction.commit()
orKVTransaction.rollback()
, in which case the invocation will be ignored. In particular, this method must not throwStaleKVTransactionException
.- Specified by:
rollback
in interfaceKVTransaction
-
readOnlySnapshot
Description copied from interface:KVTransaction
Create a read-only snapshot of the database content represented by this transaction.The returned
CloseableKVStore
should be treated as read-only. It may not actually be read-only, but if it's not, then any changes should have no effect on this instance. The returnedCloseableKVStore
must be completely independent from this transaction (subsequent changes to either one do not affect the other).Note: as with any other information extracted from a
KVTransaction
, the returned content should not be considered valid until this transaction has been successfully committed.The returned
CloseableKVStore
should be promplyclose()
'd when no longer needed to release any underlying resources. In particular, the caller must ensure that theCloseableKVStore
isclose()
'd even if this transaction's commit fails. This may require adding a transaction synchronization callback, etc.This is an optional method; only some underlying key/value store technologies can efficiently support it. Implementations should throw
UnsupportedOperationException
if not supported.- Specified by:
readOnlySnapshot
in interfaceKVTransaction
- Returns:
- independent, read-only copy of this transaction's entire database content
-
close
public void close()- Specified by:
close
in interfaceAutoCloseable
- Specified by:
close
in interfaceCloseable
-
finalize
-
wrapException
Wrap the givenDatabaseException
in the appropriateKVTransactionException
.- Parameters:
e
- Berkeley database exception- Returns:
- appropriate
KVTransactionException
with chained exceptione
- Throws:
NullPointerException
- ife
is null
-