Github user david-streamlio commented on the issue:
https://github.com/apache/nifi/pull/2702
> Also, something to think about is whether Pulsar's client will work well
across different broker versions. For example, when Pulsar 2.x comes out, will
the 1.x client work well against a 2.x broker? or vice versa?
Pulsar API compatibility vs binary protocol compatibility guidelines:
* Protocol compatibility will be always ensured (unless major reasons)
* API can be broken across major releases
The problem is that Kafka broke protocol compatibility at every release,
which necessitated the 0.9, .0.10, 0.11, and 1.0 versions.
FYI, the 2.0 release is under voting, and should be officially available in
maven central next week, but I have downloaded the code an built the jar
locally and am in the process of replacing the deprecated classes with 2.0+ API
changes.
---
