1. Home
  2. Kafka Connectors

Changelog

Version 2.0.0

  • Added Kerberos Authentication which includes the following configuration changes:
    • cassandra.security.enabled (which was either true or false) was replaced with cassandra.security which can have one of the following values:
      • NONE
      • PASSWORD (plain text username or password)
      • KERBEROS
    • Introduced connect.cassandra.principal, connect.cassandra.keytab, which are the corresponding Kerberos principal and keytab (path to keytab) to be used by the connector.
    • Introduced cassandra.kerberos.sasl.protocol which is the protocol used to create the SASL client for kerberos and should match the service portion of the Cassandra service principal (for example, if set to cassandra, the Cassandra service principal must be someuser/cassandra@realm).
  • Introduced cassandra.local.datacenter which is a required configuration, with no default. See Upgrading to Version 2.0.x for details on how to configure this value.
  • cassandra.contact.points no longer has a default configuration–which used to be localhost.
  • cassandra.ssl.provider is no longer supported. This configuration property was used to define the underlying SSL implementation (JDK, OPENSSL, OPENSSL_REFCNT) for the connector. The connector now only supports the JDK SSL implementation.
  • Upgraded cassandra.table.create.caching to include an additional option N_ROWS, which you can combine with the new config cassandra.table.create.caching.rows.per.partition to define the number of rows to cache in a created table.

Version 1.2.2

  • MINOR: Pin Guava and Netty versions

Version 1.2.1

  • Update dependencies to resolve fixed CVE issues

Version 1.2.0

No changes

Version 1.1.4

  • Add support to store offsets in Kafka
  • Add TTL support for insert query

Version 1.1.3

  • Added type codecs for converting String values in Kafka record fields to uuid and timeuuid columns on existing tables. Connect doesn’t have a UUID logical type, so UUIDs are represented as string values, requiring these custom codecs when tables with such columns already exists. The Cassandra sink connector never creates tables with these column types, since Kafka record structs never contain fields with a discernable UUID type.

Version 1.1.2

  • Re-released previous change to correct improper tagging.

Version 1.1.1

  • Corrected the connector’s version as reported to Connect.

Version 1.1.0

  • Fixed an issue where the sink connector was not properly handling Connect logical types such as DECIMAL, TIME, TIMESTAMP, and DATE.

Version 1.0.3

  • Corrected the connector’s version as reported to Connect.

Version 1.0.2

Initial version