[jira] [Commented] (KAFKA-595) Decouple producer side compression from server-side compression.

["Manikumar Reddy (JIRA)" <ji...@apache.org>]

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

Manikumar Reddy commented on KAFKA-595:
---------------------------------------

[~nehanarkhede] We have given support for broker-side compression in KAFKA-1499. This issue is similar to KAFKA-1499.      I think we can close this issue.

> Decouple producer side compression from server-side compression.
> ----------------------------------------------------------------
>
>                 Key: KAFKA-595
>                 URL: https://issues.apache.org/jira/browse/KAFKA-595
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 0.8.0
>            Reporter: Neha Narkhede
>              Labels: feature
>
> In 0.7 Kafka always appended messages to the log using whatever compression codec the client used. In 0.8, after the KAFKA-506 patch, the master always recompresses the message before appending to the log to assign ids. Currently the server uses a funky heuristic to choose a compression codec based on the codecs the producer used. This doesn't actually make that much sense. It would be better for the server to have its own compression (a global default and per-topic override) that specified the compression codec, and have the server always recompress with this codec regardless of the original codec.
> Compression currently happens in kafka.log.Log.assignOffsets (perhaps should be renamed if it takes on compression as an official responsibility instead of a side-effect).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)