Aerospike Connect for Pulsar - Outbound Release Notes

  • 2.1.0
    Release Date: July 14, 2021

    Improvements

    • Upgrade external dependencies.

  • 2.0.0
    Release Date: May 24, 2021
    • If you are using Aerospike Database Enterprise Edition version 5.6 or later, ensure that you use this version of the Pulsar outbound connector or a later one.
    • ATTENTION: HTTP connectors renamed from aerospike-pulsar-outbound-legacy to aerospike-pulsar-outbound-http. Refer to documentation for installation and starting instructions.
    • ATTENTION: Outbound format breaking changes.
      • For Aerospike Server versions <= 4.9 that do not ship generation, expiry, and lut (last update time)
        • these fields are omitted from the payload in Json, FlatJson, and Avro-Map format.
        • these fields are shipped as nil in MessagePack format.
        • these fields are shipped as null in Avro-Record format.
      • Last update time - lut has been upscaled to a Long from Int. Avro-Record schemas specified in the config should change lut type from int to long.

    New Features

    • Prometheus integration support.
    • Pre-packaged Grafana dashboards.
    • PEM file format support in TLS configuration.
    • Support for Boolean particle type introduced in Aerospike Server version 5.6.
    • Official container image available on Docker Hub.

    Bug Fixes

    • Handling of new particle types introduced by the Aerospike Server not recognized by the connector.
    • Possible incorrect handling of byte array and extension types in lists and maps in rare cases.
    • Multiple connector instances with the same producer name for a topic crashes the connector instances.

  • 1.0.0
    Release Date: December 14, 2020
    • ATTENTION Upgrade to aerospike-pulsar-outbound 2.0.0 or later when using Aerospike Server 5.6 or later.
    • Initial General Availability release for Aerospike Server Enterprise Edition version 5.0 and above.
    • Legacy support for versions of the Aerospike Server Enterprise Edition version 4.9 and below.
      • If using Aerospike Server version 4.9 or below the Legacy connector must be used.
      • WARNING: A serious flaw has been discovered for http v2 in the library used by Aerospike Server Enterprise < 5.0 change notification. http-version MUST be set to v1 to prevent XDR and Change Notification from being blocked.

    Known Issues

    • JDK-8 connector crashes when consuming records from Aerospike Server 5.6 or later.
    • JDK-11 connector errors on every record consumed from Aerospike Server 5.6 or later.