Detailed Description

Batch delete operation.

All fields must be allocated on the heap (or global) when an async batch remove is run under a transaction. The reason is transactions require an extra async call to add write keys to the transaction monitor record and this extra call causes stack variables to fall out of scope before the async batch is executed.

Definition at line 233 of file aerospike_batch.h.

#include "aerospike_batch.h"

Collaboration diagram for as_batch_remove_record:

Data Fields
bool	has_write

bool	in_doubt

as_key	key

const as_policy_batch_remove *	policy

as_record	record

as_status	result

as_batch_type	type

Field Documentation

◆ has_write

bool as_batch_remove_record::has_write

Definition at line 238 of file aerospike_batch.h.

◆ in_doubt

bool as_batch_remove_record::in_doubt

Definition at line 239 of file aerospike_batch.h.

◆ key

as_key as_batch_remove_record::key

Definition at line 234 of file aerospike_batch.h.

◆ policy

const as_policy_batch_remove* as_batch_remove_record::policy

Optional remove policy.

Definition at line 244 of file aerospike_batch.h.

◆ record

as_record as_batch_remove_record::record

Definition at line 235 of file aerospike_batch.h.

◆ result

as_status as_batch_remove_record::result

Definition at line 236 of file aerospike_batch.h.

◆ type

as_batch_type as_batch_remove_record::type

Definition at line 237 of file aerospike_batch.h.

The documentation for this struct was generated from the following file:

aerospike_batch.h