Github user david-streamlio commented on the issue:
https://github.com/apache/nifi/pull/2702
@MikeThomsen
I have updated my code to use the Apache Pulsar 2.0 client API, but cannot
commit the changes yet, as the release vote is still pending, and thus the
client jar file hasn't been released to the maven central repository.
As for testing the processors within a docker environment, you can use the
following steps that I have verified and written down here:
Testing NiFi Processors
1. Launch a docker container running Apache Pulsar 2.0:
docker pull apachepulsar/pulsar:2.0.0-rc1-incubating
docker run -d -i --name pulsar -p 6650:6650 -p 8000:8000
apachepulsar/pulsar:2.0.0-rc1-incubating
2. ssh into the pulsar container and start the Pulsar service
docker exec -it pulsar /bin/bash
root@266e559270ce:/pulsar/bin/pulsar standalone &
Launch a docker container running apache NiFi 1.7.0-SNAPSHOT
docker run -d -i --name nifi --link pulsar -p 8080:8080
apache/nifi:1.7.0-SNAPSHOT
Load the following template to to NiFi, and start the ConsumePulsar
processor FIRST.
Then start the other processors.
Verify that the data is being produced and consumed at the same rate.
Open the Pulsar dashboard at http://localhost:8000 to see the topic was
created and that the messages were generated.
[Pulsar-Test-xml.txt](https://github.com/apache/nifi/files/2051691/Pulsar-Test-xml.txt)
---
