IAsyncClient Methods

The policy specifies the transaction timeout, record expiration and how the transaction is handled when the record already exists.

The policy specifies the transaction timeout, record expiration and how the transaction is handled when the record already exists. This call only works for integer values.

The policy specifies the transaction timeout, record expiration and how the transaction is handled when the record already exists. This call only works for string values.

The policy specifies the transaction timeout, record expiration and how the transaction is handled when the record already exists. This call only works for string values.

Requires server version 6.0+

The policy specifies the transaction timeout.

If a key is not found, the corresponding result resultCode will be KEY_NOT_FOUND_ERROR.

Requires server version 6.0+

Each record result is returned in separate OnRecord() calls. If a key is not found, the corresponding result resultCode will be KEY_NOT_FOUND_ERROR.

Requires server version 6.0+

Requires server version 6.0+

udf file = <server udf dir>/<package name>.lua

udf file = <server udf dir>/<package name>.lua

Requires server version 6.0+

udf file = <server udf dir>/<package name>.lua

This method schedules the execute command with a channel selector and returns. Another thread will process the command and send the results to the listener.

The package name is used to locate the udf file location:

udf file = <server udf dir>/<package name>.lua

Requires server version 6.0+

The package name is used to locate the udf file location:

udf file = <server udf dir>/<package name>.lua

Requires server version 6.0+

Requires server version 6.0+

This method schedules the get command with a channel selector and returns. Another thread will process the command and send the results to the listener in a single call.

This method schedules the get command with a channel selector and returns. Another thread will process the command and send the results to the listener in a single call.

If a key is not found, the record will be null.

If a key is not found, the record will be null.

If a key is not found, the record will be null.

Create listener, call asynchronous batch get and return task monitor.

The returned records are in positional order with the original key array order. If a key is not found, the positional record will be null.

If a key is not found, the record will be null.

Each record result is returned in separate OnRecord() calls. If a key is not found, the record will be null.

If a key is not found, the record will be null.

If a key is not found, the record will be null.

If a key is not found, the record will be null.

If a key is not found, the record will be null.

If a key is not found, the record will be null.

If a key is not found, the record will be null.

BatchRecord can be BatchRead, BatchWrite, BatchDelete or BatchUDF.

Requires server version 6.0+

This method allows different namespaces/bins to be requested for each key in the batch. The returned records are located in the same list.

BatchRecord can be BatchRead, BatchWrite, BatchDelete or BatchUDF.

Requires server version 6.0+

This method allows different namespaces/bins to be requested for each key in the batch. Each record result is returned in separate OnRecord() calls. The returned records are located in the same list.

BatchRecord can be BatchRead, BatchWrite, BatchDelete or BatchUDF.

Requires server version 6.0+

Requires server version 6.0+

The server executes operations in the same order as the operations array. Both scalar bin operations (Operation) and CDT bin operations (ListOperation, MapOperation) can be performed in same call.

Requires server version 6.0+

An example would be to add an integer value to an existing record and then read the result, all in one database call.

An example would be to add an integer value to an existing record and then read the result, all in one database call.

The server executes operations in the same order as the operations array. Both scalar bin operations (Operation) and CDT bin operations (ListOperation, MapOperation) can be performed in same call.

If a key is not found, the corresponding result resultCode will be KEY_NOT_FOUND_ERROR.

Requires server version 6.0+

Each record result is returned in separate OnRecord() calls. If a key is not found, the corresponding result resultCode will be KEY_NOT_FOUND_ERROR.

Requires server version 6.0+

Requires server version 6.0+

The policy specifies the transaction timeout, record expiration and how the transaction is handled when the record already exists. This call works only for string values.

The policy specifies the transaction timeout, record expiration and how the transaction is handled when the record already exists. This call works only for string values.

The policy specifies the transaction timeout, record expiration and how the transaction is handled when the record already exists.

The policy specifies the transaction timeout, record expiration and how the transaction is handled when the record already exists.

If maxConcurrentNodes is not 1, the supplied listener must handle shared data in a thread-safe manner, because the listener will be called by multiple query threads (one thread per node) in parallel.

Requires server version 6.0+ if using a secondary index query.

maxConcurrentNodes

This method schedules the node's query commands with channel selectors and returns. Selector threads will process the commands and send the results to the listener.

Requires server version 6.0+ if using a secondary index query.

If maxConcurrentNodes is not 1, the supplied listener must handle shared data in a thread-safe manner, because the listener will be called by multiple query threads (one thread per node) in parallel.

The completion status of all partitions is stored in the partitionFilter when the query terminates. This partitionFilter can then be used to resume an incomplete query at a later time. This is the preferred method for query terminate/resume functionality.

Requires server version 6.0+ if using a secondary index query.

The query executor puts results on a queue in separate threads. The calling thread concurrently pops results off the queue through the ResultSet iterator. The aggregation function is called on both server and client (final reduce). Therefore, the Lua script file must also reside on both server and client.

The query executor puts results on a queue in separate threads. The calling thread concurrently pops results off the queue through the ResultSet iterator. The aggregation function is called on both server and client (final reduce). Therefore, the Lua script file must also reside on both server and client.

Requires server version 6.0+ if using a secondary index query.

maxConcurrentNodes

This method schedules the node's query commands with channel selectors and returns. Selector threads will process the commands and send the results to the listener.

Each record result is returned in separate OnRecord() calls.

Requires server version 6.0+ if using a secondary index query.

 String code = @"
 local function reducer(val1,val2)
      return val1 + val2
 end

 function sum_single_bin(stream,name)
   local function mapper(rec)
     return rec[name]
   end
   return stream : map(mapper) : reduce(reducer)
 end
";

    client.RegisterUdfString(null, code, "mysum.lua", Language.LUA);

This asynchronous server call will return before command is complete. The user can optionally wait for command completion by using the returned RegisterTask instance.

This call will block until the scan is complete - callbacks are made within the scope of this call.

This method schedules the scan command with a channel selector and returns. Another thread will process the command and send the results to the listener.

This call will block until the scan is complete - callbacks are made within the scope of this call.

This call will block until the scan is complete - callbacks are made within the scope of this call.

This call will block until the scan is complete - callbacks are made within the scope of this call.

This method schedules the scan command with a channel selector and returns. Another thread will process the command and send the results to the listener.

See https://www.aerospike.com/docs/reference/info#truncate

This asynchronous server call may return before the truncation is complete. The user can still write new records after the server returns because new records will have last update times greater than the truncate cutoff (set at the time of truncate call).