You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2015/02/22 00:37:12 UTC
[jira] [Commented] (KAFKA-1865) Add a flush() call to the new
producer API
[ https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14331364#comment-14331364 ]
Jay Kreps commented on KAFKA-1865:
----------------------------------
Updated reviewboard https://reviews.apache.org/r/30763/diff/
against branch trunk
> Add a flush() call to the new producer API
> ------------------------------------------
>
> Key: KAFKA-1865
> URL: https://issues.apache.org/jira/browse/KAFKA-1865
> Project: Kafka
> Issue Type: Bug
> Reporter: Jay Kreps
> Assignee: Jay Kreps
> Attachments: KAFKA-1865.patch, KAFKA-1865_2015-02-21_15:36:54.patch
>
>
> The postconditions of this would be that any record enqueued prior to flush() would have completed being sent (either successfully or not).
> An open question is whether you can continue sending new records while this call is executing (on other threads).
> We should only do this if it doesn't add inefficiencies for people who don't use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)