[
https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5353:
-------------------------------
Description:
This makes the case where we build the records from scratch consistent
with the case where update the batch header "in place".
The reason our tests don’t catch this is that we rely on the maxTimestamp
to compute the record level timestamps if log append time is used.
was:We currently don't update baseTimestamp in this case (just maxTimestamp),
which is inconsistent with what we do if there is broker recompression.
> baseTimestamp should always have a create timestamp
> ---------------------------------------------------
>
> Key: KAFKA-5353
> URL: https://issues.apache.org/jira/browse/KAFKA-5353
> Project: Kafka
> Issue Type: Bug
> Reporter: Ismael Juma
> Assignee: Ismael Juma
> Priority: Blocker
> Fix For: 0.11.0.0
>
>
> This makes the case where we build the records from scratch consistent
> with the case where update the batch header "in place".
> The reason our tests don’t catch this is that we rely on the maxTimestamp
> to compute the record level timestamps if log append time is used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
