You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/08 07:10:27 UTC
[jira] [Commented] (KAFKA-2621) nextOffsetMetadata should be
changed after rolling a new log segment
[ https://issues.apache.org/jira/browse/KAFKA-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948083#comment-14948083 ]
ASF GitHub Bot commented on KAFKA-2621:
---------------------------------------
GitHub user lindong28 opened a pull request:
https://github.com/apache/kafka/pull/286
KAFKA-2621; nextOffsetMetadata should be changed after rolling a new log segment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lindong28/kafka KAFKA-2621
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/286.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 #286
----
commit 609c17536001042edb91576f4fd288d160e9938a
Author: Dong Lin <li...@gmail.com>
Date: 2015-10-08T05:09:09Z
KAFKA-2621; nextOffsetMetadata should be changed after rolling a new log segment
----
> nextOffsetMetadata should be changed after rolling a new log segment
> --------------------------------------------------------------------
>
> Key: KAFKA-2621
> URL: https://issues.apache.org/jira/browse/KAFKA-2621
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.2.1
> Reporter: Jun Rao
> Assignee: Jiangjie Qin
> Fix For: 0.9.0.0
>
>
> When we roll a new log segment (Log.roll()), even though the next offset doesn't change, the associated metadata (segment base offset and relative position) will change. So, we need to update nextOffsetMetadata when rolling a new log segment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)