[
https://issues.apache.org/jira/browse/KAFKA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332452#comment-14332452
]
Jay Kreps commented on KAFKA-1865:
----------------------------------
Uploaded a new patch that tracks all incomplete RecordBatch's in the
RecordAccumulator and uses these to block on for flush.
I was having trouble with test hangs, but I'm not sure if they are related to
this patch or not so I haven't yet validated the tests.
I also improved the producer javadoc while in there since I was adding docs for
flush.
> 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,
> KAFKA-1865_2015-02-22_16:26:46.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)
