public class TTLKCVS extends KCVSProxy
NO_ADDITIONS, NO_DELETIONS
Constructor and Description |
---|
TTLKCVS(KeyColumnValueStore store,
int ttl) |
Modifier and Type | Method and Description |
---|---|
void |
mutate(StaticBuffer key,
List<Entry> additions,
List<StaticBuffer> deletions,
StoreTransaction txh)
Verifies acquisition of locks
txh from previous calls to
KeyColumnValueStore.acquireLock(StaticBuffer, StaticBuffer, StaticBuffer, StoreTransaction)
, then writes supplied additions and/or deletions to
key in the underlying data store. |
public TTLKCVS(KeyColumnValueStore store, int ttl)
public void mutate(StaticBuffer key, List<Entry> additions, List<StaticBuffer> deletions, StoreTransaction txh) throws BackendException
KeyColumnValueStore
txh
from previous calls to
KeyColumnValueStore.acquireLock(StaticBuffer, StaticBuffer, StaticBuffer, StoreTransaction)
, then writes supplied additions
and/or deletions
to
key
in the underlying data store. Deletions are applied strictly
before additions. In other words, if both an addition and deletion are
supplied for the same column, then the column will first be deleted and
then the supplied Entry for the column will be added.
Implementations which don't support locking should skip the initial lock verification step but otherwise behave as described above.
mutate
in interface KeyColumnValueStore
mutate
in class KCVSProxy
key
- the key under which the columns in additions
and
deletions
will be writtenadditions
- the list of Entry instances representing column-value pairs to
create under key
, or null to add no column-value pairsdeletions
- the list of columns to delete from key
, or null to
delete no columnstxh
- the transaction to usePermanentLockingException
- if locking is supported by the implementation and at least
one lock acquisition attempted by
KeyColumnValueStore.acquireLock(StaticBuffer, StaticBuffer, StaticBuffer, StoreTransaction)
has failedBackendException
Copyright © 2012–2024. All rights reserved.