Skip to main content

Configure Formats for Aerospike Connect for Elasticsearch

The format section of the aerospike-elasticsearch-outbound.yaml file specifies the serialization format of the data output.

Aerospike record metadata

Every Aerospike record has a metadata associated with it. Below is the list of metadata fields that XDR sends to connector with every record:

MetadataTypeDescriptionPresent in
msgstringWrite/Delete operation.Delete and Write
namespacestringNamespace of the Aerospike record.Delete and Write
setstringSet of the Aerospike record.Write
userKeylong, double, bytes or stringThe user key of the Aerospike record.Write (only if user key is stored on server)
digestbytesThe digest of the Aerospike record.Delete and Write
genintThe generation of the Aerospike record.Write
lutintThe last update time of the Aerospike record.Write
expintThe expiry of the Aerospike record.Write
durablebooleanWhether the delete is durable.Delete
  • HyperLogLog bins are forwarded as is, as bytes or (for string-based formats) as Base64-encoded strings.

Elasticsearch has strict checks for data-types of all the documents of an index. All Aerospike record bins should be converted to Elasticsearch document fields as per the index's mapping/schema. The connector will report Elasticsearch's mapper_parsing_exception in case of mapping violation.

The only supported format is custom. The payload-format of this custom format can either be JSON or FlatJSON.


mode: custom
mode: flat-json
batch-formatter-class: com.aerospike.connect.outbound.transformer.examples.elasticsearch.ElasticsearchCustomJsonBatchFormatter