[jira] [Assigned] (KAFKA-3026) KIP-32 (part 2): Changes in broker to over-write timestamp or reject message

["Jiangjie Qin (JIRA)" <ji...@apache.org>]

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

Jiangjie Qin reassigned KAFKA-3026:
-----------------------------------

    Assignee: Jiangjie Qin  (was: Anna Povzner)

> KIP-32 (part 2): Changes in broker to over-write timestamp or reject message
> ----------------------------------------------------------------------------
>
>                 Key: KAFKA-3026
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3026
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Anna Povzner
>            Assignee: Jiangjie Qin
>
> The decision about this JIRA assignment is still under discussion with [~becket_qin]. Not going to implement without his agreement.
> This JIRA includes:
> When the broker receives a message, it checks the configs:
> 1. If message.timestamp.type=LogAppendTime, the server over-writes the timestamp with its current local time
> Message could be compressed or not compressed. In either case, the timestamp is always over-written to broker's current time
> 2. If message.timestamp.type=CreateTime, the server calculated the difference between the current time on broker and Timestamp in the message:
> If difference is within max.message.time.difference.ms, the server will accept it and append it to the log. For compressed message, server will update the timestamp in compressed message to -1: this means that CreateTime is used and the timestamp is in each individual inner message.
> If difference is higher than max.message.time.difference.ms, the server will reject the entire batch with TimestampExceededThresholdException.
> (Actually adding the timestamp to the message and adding configs are covered by KAFKA-3025).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)