[
https://issues.apache.org/jira/browse/NIFI-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989589#comment-14989589
]
Mark Payne commented on NIFI-1097:
----------------------------------
I re-ran my test for the new PutKafka and saw the same numbers this time as the
old Processor, pushing about 6300 messages/sec. The previous test was run last
night for the new Processor, and it's possible that I was just having problems
with my wifi/network connection. All looks good with this patch now. I did
change the patch a bit to account for fixing the "Details" of the SEND
provenance event that is published, so I uploaded a new patch anyway.
> PutKafka should be changed to use the new 0.8.2 Producer API
> ------------------------------------------------------------
>
> Key: NIFI-1097
> URL: https://issues.apache.org/jira/browse/NIFI-1097
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 0.4.0
>
> Attachments:
> 0001-NIFI-1097-Rewrite-PutKafka-to-use-the-new-producer-a.patch
>
>
> Currently, PutKafka uses the old Producer API, which provides several
> limitations. The most critical of these limitations is that the asynchronous
> send does not provide an indication of its success. As a result, when
> PutKafka is configured to send asynchronously, it will always route the
> FlowFIle to 'success' even if it does not send the data to Kafka.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
