Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2493
yes correct it would be awesome if the client/broker interface could
support a genuinely streaming interface rather than a byte[] as this helps
frameworks that can operate on the streams rather than having objects fully
loaded operate in the most GC/efficient manner possible. It means sending a 1
GB object for example never holds more than some small buffer size in memory.
If you want to suppor the use case you're describing then nifi has to load the
full image/document/etc.. into a byte[] then hand that over to the pulsar
interface. So, larger objects become a problem in terms of
efficiency/parallelism. no biggie for now but does make that use case a bit
less exciting for now :)
---
