kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5353) Set baseTimestamp correctly if log append time and no broker recompression
Date Wed, 31 May 2017 12:52:04 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ismael Juma updated KAFKA-5353:
-------------------------------
    Description: We currently don't update baseTimestamp in this case (just maxTimestamp),
which is inconsistent with what we do if there is broker recompression.  (was: We currently
don't update baseSequence in this case, which is inconsistent with what we do if there is
broker recompression.)

> Set baseTimestamp correctly if log append time and no broker recompression 
> ---------------------------------------------------------------------------
>
>                 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
>
>
> We currently don't update baseTimestamp in this case (just maxTimestamp), which is inconsistent
with what we do if there is broker recompression.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message