[
https://issues.apache.org/jira/browse/NIFI-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987280#comment-14987280
]
Mark Payne commented on NIFI-1097:
----------------------------------
[~trixpan] - I believe the priority of this ticket as 'critical' is correct.
There is the potential for data loss as-is when using the Async sender, and
without the user even knowing that they lost data. We should not consider
sending asynchronously to mean that data loss may occur. The API provides
callback mechanisms in order to know whether or not the data safely made it to
Kafka, and we should use these types of mechanisms to ensure that we never lose
the data.
> 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)
