[
https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Stein updated KAFKA-1865:
-----------------------------
Fix Version/s: 0.8.3
> 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
> Fix For: 0.8.3
>
> Attachments: KAFKA-1865.patch, KAFKA-1865_2015-02-21_15:36:54.patch,
> KAFKA-1865_2015-02-22_16:26:46.patch, KAFKA-1865_2015-02-23_18:29:16.patch,
> KAFKA-1865_2015-02-25_17:15:26.patch, KAFKA-1865_2015-02-26_10:37:16.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)
