[
https://issues.apache.org/jira/browse/KAFKA-10133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183300#comment-17183300
]
Steve Jacobs commented on KAFKA-10133:
--------------------------------------
That is how I was confirming compression as well. The example you gave is the
same as what I said above. It sets the property on the kafka connect worker.
Not in the sourceconnector/checkpointconnector etc.
> Cannot compress messages in destination cluster with MM2
> --------------------------------------------------------
>
> Key: KAFKA-10133
> URL: https://issues.apache.org/jira/browse/KAFKA-10133
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
> Affects Versions: 2.4.0, 2.5.0, 2.4.1
> Environment: kafka 2.5.0 deployed via the strimzi operator 0.18
> Reporter: Steve Jacobs
> Priority: Minor
>
> When configuring mirrormaker2 using kafka connect, it is not possible to
> configure things such that messages are compressed in the destination
> cluster. Dump Log shows that batching is occuring, but no compression. If
> this is possible, then this is a documentation bug, because I can find no
> documentation on how to do this.
> baseOffset: 4208 lastOffset: 4492 count: 285 baseSequence: -1 lastSequence:
> -1 producerId: -1 producerEpoch: -1 partitionLeaderEpoch: 2 isTransactional:
> false isControl: false position: 239371 CreateTime: 1591745894859 size: 16362
> magic: 2 compresscodec: NONE crc: 1811507259 isvalid: true
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
