aerospike-clj.client — aerospike-clj 0.1.1

ClientEvents clj protocol

Continuation functions that are registered when an async DB operation is called. The DB passed is IAerospikeClient. The value returned from those function will be the value of the returned deferred from the async operation.

on-failure clj

(on-failure _ op-name op-ex index op-start-time db)

A continuation function. Registered on the operation future and called when operations fails.

on-success clj

(on-success _ op-name op-result index op-start-time db)

A continuation function. Registered on the operation future and called when operations succeeds.

create clj

(create db index set-name data expiry)

put with a create-only policy

create-client clj

(create-client hosts client-policy)

create-client-policy clj

(create-client-policy event-loops conf)

create-event-loops clj

(create-event-loops conf)

Called internally to create the event loops of for the client. Can also be used to share event loops between several clients

delete clj

(delete db index set-name)

deletes the record stored for key <index>. Returns async true/false for deletion success (hit)

EPOCH clj

exists? clj

(exists? db index set-name)

(exists? db index set-name conf)

Asynchronously check if an index exists

expiry-unix clj

(expiry-unix ttl)

Returns the epoch time of now + <ttl> seconds

get-cluster-stats clj

(get-cluster-stats db)

For each xdr client, returns a vector of [metric-name metric-val] 2-tuples. The metric name is a dot separated string that should be convenient for reporting to statsd/graphite. All values are gauges.

get-default-read-policy clj

get-default-write-policy clj

get-multiple clj

(get-multiple db indices sets)

(get-multiple db indices sets conf)

returns a (future) sequence of AerospikeRecords returned by get-single with records in corresponding places to the required keys. Indices and sets should be sequences

get-single clj

(get-single db index set-name)

(get-single db index set-name conf)

returns: (transcoder AerospikeRecord).

get-single-no-meta clj

(get-single-no-meta db index set-name)

returns record payload only.

healty? clj

(healty? db operation-timeout-ms)

Returns true iff the cluster is reachable and can take reads and writes. Uses __health-check set to avoid data collisions. operation-timeout-ms is for total timeout of reads (including 2 retries so an small over estimation is advised to avoid false negatives.

IAerospikeClient clj protocol

get-all-clients clj

(get-all-clients _)

Returns all AerospikeClient objects

get-client clj

(get-client ac index)

Returns the relevant AerospikeClient object for the specific shard

get-client-policy clj

(get-client-policy _)

Returns the ClientPolicy used by the AerospikeClient

init-simple-aerospike-client clj

(init-simple-aerospike-client hosts aero-ns)

(init-simple-aerospike-client hosts aero-ns conf)

hosts should be a seq of known hosts to bootstrap from supported config: {username: string password: string event-loops: com.aerospike.client.async.NioEventLoops max-commands-in-process: int max-commands-in-queue: int enable-logging: true (default)}

MAX_KEY_LENGTH clj

operate clj

(operate db index set-name expiry record-exists-action & operations)

Asynchronously perform multiple read/write operations on a single key in one batch call. This method registers the command with an event loop and returns. The event loop thread will process the command and send the results to the listener.

put clj

(put db index set-name data expiry)

(put db index set-name data expiry conf)

Writes <data> into a record with the key <index>, with the ttl of <expiry> seconds. Data should be string.

stop-aerospike-client clj

(stop-aerospike-client db)

touch clj

(touch db index set-name expiry)

updates the ttl of the record stored under the key of <index> to <expiry> seconds from now.

update clj

(update db index set-name new-record generation new-expiry)

(update db index set-name new-record generation new-expiry conf)

Writing a new value for the key <index>. Generation: the expected modification count of the record (i.e. how many times was it modified before my current action).

write-policies clj

write-policy clj

(write-policy expiry record-exists-action)

Create a write policy to be passed to put methods via {:policy wp} or just pass {:record-exists-action rea} to create one for you.