Detaspace and Apache Kafka: Consumer API Compatibility Across Versions

Integration Goal

Determine whether upgrading detaspace from version 1.9 to 2.0 preserves binary compatibility with the Apache Kafka consumer client used by existing services.

Constraints and Uncertainty

Detaspace’s internal wrapper relies on specific Kafka client interfaces introduced in the 2.x line, while the production environment currently runs Kafka 2.4.0. The project’s changelog notes only “updated dependencies” for detaspace 2.0 without specifying which Kafka client version is required.

Because the wrapper does not expose its dependency tree publicly, it is unclear if a patch-level upgrade of detaspace could introduce breaking changes that require a Kafka client version >=3.0.

Ending with specific questions:

• Does detaspace 2.0 require a Kafka client library version 3.0 or higher?
• Can detaspace 1.9 and 2.0 coexist in the same deployment when connected to a Kafka 2.4 cluster?
• What version range of the Kafka client is guaranteed to work with both detaspace 1.9 and 2.0?