Aerospike Connect for Kafka - Inbound Release Notes

• ATTENTION: In future releases, Aerospike Kafka Inbound Connector will be renamed to aerospike-sink-connector.

Security

• [CONNECTOR-982] Fix Improper Input Validation.
• [CONNECTOR-983] Fix Infinite loop.
• [CONNECTOR-984] Fix Uncontrolled Resource Consumption.
• [CONNECTOR-1022] Fix Out-of-bounds write vulnerabilities.
• [CONNECTOR-1023] Fix Out-of-bounds write vulnerabilities.
• [CONNECTOR-1024] Fix Out-of-bounds write vulnerabilities.
• [CONNECTOR-1025] Fix Out-of-bounds write vulnerabilities.
• [CONNECTOR-1026] Fix Out-of-bounds write vulnerabilities.

• ATTENTION: In future releases, Aerospike Kafka Inbound Connector will be renamed to aerospike-sink-connector.

Improvements

• Upgraded a few dependencies.

• ATTENTION: In future releases, Aerospike Kafka Inbound Connector will be renamed to aerospike-sink-connector.

Security

• [CONNECTOR-888] - Update Transitive dependency in Kafka inbound to fix CVE-2023-43642.

• Breaking change - Custom transformers will not be able to write Java runtime serialized objects as bins to target Aerospike cluster.
• ATTENTION: In future releases, Aerospike Kafka Inbound Connector will be renamed to aerospike-sink-connector.

Security

• [CONNECTOR-775] - Address CVE-2023-36480 - upgrade to aerospike-java-client version 7.0.0.
• [CONNECTOR-780] - Remove process-as-aerospike-records option from Kafka Inbound.

• ATTENTION: In future releases, Aerospike Kafka Inbound Connector will be renamed to aerospike-sink-connector.

Security

• [CONNECTOR-716] - Upgrade vulnerable dependencies.

• ATTENTION: In future releases, Aerospike Kafka Inbound Connector will be renamed to aerospike-sink-connector.

Improvements

• [CONNECTOR-679] - Upgrade vulnerable dependencies.

• ATTENTION: In future releases, Aerospike Kafka Inbound Connector will be renamed to aerospike-sink-connector.

Improvements

• [CONNECTOR-445] Fix CVE-2022-34917 in Kafka Connectors.
  • Upgraded Kafka client from 2.3.0 to 3.3.1.
  • Upgraded a few dependencies.

New Features

• [CONNECTOR-353] - Maintain order of writes to Aerospike for the same Kafka key.

Improvements

• [CONNECTOR-354] - Limit the records queued up at the connector with max-queued-records configuration parameter.
• [CONNECTOR-355] - Add configuration parameter to control the number of threads used for converting Kafka records to Aerospike operations.

New Features

• [CONNECTOR-185] - Add Boolean particle type support introduced in server 5.6.
• [CONNECTOR-280] - Add support for PKI authentication introduced in server 5.7.
• [CONNECTOR-302] - Add a new ignore-error-codes configuration to specify the set of Aerospike client write/delete errors to be ignored and considered as successfully processed.

Improvements

• Support handling of MessagePack format breaking changes introduced in Aerospike Kafka Outbound version 4.0.0, when consuming messages from Kafka written by Aerospike Kafka outbound in MessagePack format.
• [CONNECTOR-301] - feature-key-file config deprecated, validate feature key directly from the Aerospike server.

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.