You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/05/30 14:29:04 UTC

[jira] [Resolved] (KAFKA-4907) compacted topic shouldn't reject messages with old timestamp

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

Ismael Juma resolved KAFKA-4907.
--------------------------------
    Resolution: Won't Fix

We decided to change the default of `message.timestamp.difference.max.ms` back to Long.MaxValue as the additional complexity makes it harder to reason about the behaviour.

> compacted topic shouldn't reject messages with old timestamp
> ------------------------------------------------------------
>
>                 Key: KAFKA-4907
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4907
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.10.1.0
>            Reporter: Jun Rao
>            Assignee: Jiangjie Qin
>
> In LogValidator.validateTimestamp(), we check the validity of the timestamp in the message without checking whether the topic is compacted or not. This can cause messages to a compacted topic to be rejected when it shouldn't.



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