[
https://issues.apache.org/jira/browse/KAFKA-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028063#comment-16028063
]
ASF GitHub Bot commented on KAFKA-5344:
---------------------------------------
GitHub user becketqin opened a pull request:
https://github.com/apache/kafka/pull/3163
KAFKA-5344: set message.timestamp.difference.max.ms back to Long.MaxValue
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/becketqin/kafka KAFKA-5344
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3163.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3163
----
----
> Change message.timestamp.difference.max.ms back to Long.MaxValue
> ----------------------------------------------------------------
>
> Key: KAFKA-5344
> URL: https://issues.apache.org/jira/browse/KAFKA-5344
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Fix For: 0.11.0.0
>
>
> Per discussion in KAFKA-4340 and PR-2705
> (https://github.com/apache/kafka/pull/2705), we agreed it is easier to just
> set the default value of message.timestamp.difference.max.ms back to
> Long.MaxValue. User can override it to avoid frequent rolling if needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
