You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/09/23 04:49:04 UTC

[jira] [Updated] (KAFKA-3252) compression type for a topic should be used during log compaction

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

Guozhang Wang updated KAFKA-3252:
---------------------------------

*Reminder to the contributor / reviewer of the PR*: please note that the code deadline for 1.0.0 is less than 2 weeks away (Oct. 4th). Please re-evaluate your JIRA and see if it still makes sense to be merged into 1.0.0 or it could be pushed out to 1.1.0, or be closed directly if the JIRA itself is not valid any more, or re-assign yourself as contributor / committer if you are no longer working on the JIRA.

> compression type for a topic should be used during log compaction 
> ------------------------------------------------------------------
>
>                 Key: KAFKA-3252
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3252
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.9.0.0
>            Reporter: Jun Rao
>            Assignee: Ashish Singh
>             Fix For: 1.0.0
>
>
> Currently, the broker uses the specified compression type in a topic for newly published messages. However, during log compaction, it still uses the compression codec in the original message. To be consistent, it seems that we should use the compression type in a topic when copying the messages to new log segments.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)