[
https://issues.apache.org/jira/browse/KAFKA-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179373#comment-15179373
]
Manikumar Reddy edited comment on KAFKA-3252 at 3/4/16 5:45 AM:
----------------------------------------------------------------
@ [~singhashish], [~junrao]
This issue is related to KAFKA-2213. long back, I submitted a patch. My patch
may be obsolete now.
@ [~singhashish]
kafka.tools.TestLogCleaning can be used to stress test your patch.
cc [~jjkoshy]
was (Author: omkreddy):
@ [~singhashish], [~junrao]
This issue is related to KAFKA-2213. long back, I have submitted a patch. My
patch may be obsolete now.
@ [~singhashish]
kafka.tools.TestLogCleaning can be used to stress test your patch.
cc [~jjkoshy]
> 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 K Singh
>
> 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.3.4#6332)
