Detailed Description

Batch key and read/write operations with write policy.

All fields must be allocated on the heap (or global) when an async batch write 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 159 of file aerospike_batch.h.

#include "aerospike_batch.h"

Collaboration diagram for as_batch_write_record:

Data Fields
bool	has_write

bool	in_doubt

as_key	key

as_operations *	ops

const as_policy_batch_write *	policy

as_record	record

as_status	result

as_batch_type	type

Field Documentation

◆ has_write

bool as_batch_write_record::has_write

Definition at line 164 of file aerospike_batch.h.

◆ in_doubt

bool as_batch_write_record::in_doubt

Definition at line 165 of file aerospike_batch.h.

◆ key

as_key as_batch_write_record::key

Definition at line 160 of file aerospike_batch.h.

◆ ops

as_operations* as_batch_write_record::ops

Required read/write operations for this key. The user must call as_operations_destroy() when done with the batch.

Definition at line 176 of file aerospike_batch.h.

◆ policy

const as_policy_batch_write* as_batch_write_record::policy

Optional write policy.

Definition at line 170 of file aerospike_batch.h.

◆ record

as_record as_batch_write_record::record

Definition at line 161 of file aerospike_batch.h.

◆ result

as_status as_batch_write_record::result

Definition at line 162 of file aerospike_batch.h.

◆ type

as_batch_type as_batch_write_record::type

Definition at line 163 of file aerospike_batch.h.

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

aerospike_batch.h