[
https://issues.apache.org/jira/browse/KAFKA-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179009#comment-15179009
]
ASF GitHub Bot commented on KAFKA-3252:
---------------------------------------
GitHub user SinghAsDev opened a pull request:
https://github.com/apache/kafka/pull/1010
KAFKA-3252: Compression type from broker config should be used during log
compaction.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SinghAsDev/kafka KAFKA-3252
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1010.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 #1010
----
commit 3f447c28104a2b96b4dd2dad1709f7e04f0088ff
Author: Ashish Singh <[email protected]>
Date: 2016-03-02T23:52:54Z
KAFKA-3252: Compression type from broker config should be used during log
compaction.
commit 97a436028a519e143fb70700943c08ef2a714708
Author: Ashish Singh <[email protected]>
Date: 2016-03-02T23:56:36Z
Fix using of convertedMessage
commit 94041c2247a234f0069f7b0426948ad203b79572
Author: Ashish Singh <[email protected]>
Date: 2016-03-04T00:25:05Z
Add UT
----
> 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)
