You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2019/02/17 18:50:00 UTC

[jira] [Commented] (KAFKA-7061) Enhanced log compaction

    [ https://issues.apache.org/jira/browse/KAFKA-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770502#comment-16770502 ] 

Matthias J. Sax commented on KAFKA-7061:
----------------------------------------

Moving all major/minor/trivial tickets that are not merged yet out of 2.2 release.

> Enhanced log compaction
> -----------------------
>
>                 Key: KAFKA-7061
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7061
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.0.0
>            Reporter: Luis Cabral
>            Priority: Major
>              Labels: kip
>             Fix For: 2.2.0
>
>
> Enhance log compaction to support more than just offset comparison, so the insertion order isn't dictating which records to keep.
> Default behavior is kept as it was, with the enhanced approached having to be purposely activated.
> The enhanced compaction is done either via the record timestamp, by settings the new configuration as "timestamp" or via the record headers by setting this configuration to anything other than the default "offset" or the reserved "timestamp".
> See [KIP-280|https://cwiki.apache.org/confluence/display/KAFKA/KIP-280%3A+Enhanced+log+compaction] for more details.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)