Starting with version 2.2.1, Aerospike Kafka Sink Connector maintains the order of writes to Aerospike for the same Kafka key. That is for Kafka records with the same Kafka key, the connector will process and write records to Aerospike database in the order it received the corresponding Kafka records. We recommend having a one-to-one correspondence between Kafka keys and Aerospike Keys if you desire ordering guarantees.
There are no ordering guarantees for writes to Aerospike across Kafka records with different Kafka keys or missing Kafka keys.
To use this feature, the corresponding Kafka topic should be partitioned and should use a Kafka key-based partitioner that assigns the same partition to records with the same Kafka key. See Kafka partitioning to learn more.