Skip to main content
Loading

The format section of aerospike-jms-outbound.yml

The format section of the /etc/aerospike-jms-outbound/aerospike-jms-outbound.yml specifies the serialization format of the data output. The supported formats are:

Aerospike record metadata

The Aerospike record metadata has the following fields

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

WARNING

  • HyperLogLog bins are forwarded as is, as bytes or (for string-based formats) as Base64-encoded strings.

Avro

Specifies that the data be serialized as Avro format. The Avro schema can be a map or a record. In the case of a map, just specifying the type of the map values is sufficient. In the case of a record, the exact field names and types need to be specified.

OptionRequiredDefaultExpected valueDescription
modeyesavroSelects avro format.
schemanoThe schema of the data.
schema-filenoThe file containing the schema of the data.
stringify-map-keysnotrueWhether the numeric keys in CDT maps should be converted to strings. See stringify map keys in avro

Either schema or schema-file has to be specified.

For more information about serializing data in the Avro format, see Avro Format.

Flat JSON

Specifies that the data be serialized to Flat JSON format. The type information of bins is not part of the output.

OptionRequiredDefaultExpected valueDescription
modeyesflat-jsonSelects Flat JSON format.
metadata-keyyesThe Aerospike record metadata will be inserted into this top level key.
stringify-map-keysnotrueWhether the numeric keys in CDT maps should be converted to strings. See stringify map keys

Example

format:
mode: flat-json
metadata-key: metadata

For more information about serializing data in the Flat JSON format, see Flat JSON Format.

JSON

Specifies that the data be serialized to JSON format with the type information of bins.

OptionRequiredDefaultExpected valueDescription
modeyesjsonSelects JSON format.
stringify-map-keysnotrueWhether the numeric keys in CDT maps should be converted to strings. See stringify map keys

Stringify Map Keys

Aerospike allows many data types as keys in collection data types (CDTs) Maps, but JSON only allows strings as keys in objects. As of now the JMS connector only permits for conversion of numeric types to string keys when converting Aerospike CDT maps.

An Aerospike CDT map with any other data type as the key will fail to be parsed in the JMS connector. Also, an Aerospike CDT map with numeric key, but stringify-map-keys set to false will fail to be parsed in the JMS connector.

Example

format:
mode: json

For more information about serializing data in the JSON format, see JSON Format.

MessagePack

Specifies that the data be serialized to MessagePack format with the type information about bins.

OptionRequiredExpected valueDescription
modeyesmessage-packSelects message pack format.

Example

format:
mode: message-pack

For more information about serializing data in the MessagePack format, see MessagePack Format.

Custom

Specifies that the data be serialized with user provided custom code. See Format Transform.

Example

format:
mode: custom
class: com.aerospike.connect.outbound.example.Formatter