You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/11/03 11:18:27 UTC
[jira] [Commented] (NIFI-1097) PutKafka should be changed to use
the new 0.8.2 Producer API
[ https://issues.apache.org/jira/browse/NIFI-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987024#comment-14987024 ]
Joseph Witt commented on NIFI-1097:
-----------------------------------
Mark Payne tells me that this requires a rewrite to use the new producer API. Given the potential impact this should be considered critical and we should really evaluate whether this should be included in 0.4.0 or a very short thereafter 0.4.1. By tackling this too we should be able to support what was requested in NIFI-1095
Thanks
Joe
> 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
>
>
> 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)