Aerospike Connect for Kafka - Inbound Release Notes

New Features

• User can implement a message transformer to transform the Kafka message into an Aerospike operation.
• Convert and write Aerospike Kafka Outbound Connector messages (in MessagePack format) to Aerospike.

Improvements

• Extract Aerospike record digest from the Kafka message.

Bug Fixes

• Close all resources on Sink task close.

• Confluent certified Aerospike Kafka Inbound connector.

• Shaded jar dependencies, like Netty, to avoid version conflicts when running within the Confluent platform.

• Guarantees on Kafka record consumption.
• Support Aerospike TLS.
• Support for delete operation.
• Multiple options to pick values from key, value of Kafka record.
• Aerospike record key not limited to Kafka record key, can be in Kafka record value as well.
• Config option to specify task behavior on Kafka record parsing or conversion to Aerospike record errors.
• Retry on any Aerospike errors on write.

• Aerospike Kafka Connector (Inbound)
  • Added configurations for the Aerospike client.
    • New configurations:
      • policy.max_connections_per_node
      • policy.max_commands_in_queue
    • Allows tuning if encountering certain OOM issues https://stackoverflow.com/questions/55374695/how-to-fix-problem-with-max-connections-exceed .

• Inbound connector
  • Ability to specify an aerospike user/password with the config variables aerospike.username and aerospike.password.

• Initial GA release.