[
https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040468#comment-16040468
]
Ismael Juma commented on KAFKA-5390:
------------------------------------
[~magnus.reftel], I am not sure I understand. By using `flush`, you are doing
it explicitly. That is the third way today. You are suggesting a 4th way. For
this kind of change a KIP would be required. I would suggest sending an email
to the mailing list with what you are trying to achieve, starting from the use
case and goals. There may be a reasonable way to do it already, but it's hard
to tell from this discussion as it started as a bug report. It would also be
good to close this JIRA as it doesn't look like there's a bug.
> First records in batch rejected but others accepted when rolling log
> --------------------------------------------------------------------
>
> Key: KAFKA-5390
> URL: https://issues.apache.org/jira/browse/KAFKA-5390
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.2.1
> Reporter: Magnus Reftel
> Attachments: kafka-sequence-2.tar.gz, kafka-sequence.tar.gz
>
>
> When sending a sequence of records in a batch right when the broker needs to
> roll a new segment, it's possible for the first few records to fail, while
> other records in the batch are accepted. If records have dependencies on
> earlier records, e.g. in the case of a sequence of events in an event-sourced
> system, then a producer cannot use the batching functionality, since it then
> risks consumers receiving a record without first receiving the records it
> depends on.
> See attached testcase (kafka-sequence.tar.gz).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
