[
https://issues.apache.org/jira/browse/KAFKA-17296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877358#comment-17877358
]
Viktor Somogyi-Vass commented on KAFKA-17296:
---------------------------------------------
This change affects the binary protocol of Kafka, so has to go through the KIP
process, so please create one.
Also it may be a better approach to generalize it and say producer_or_broker
where in the latter case we take the setting on the broker which could be any
of the supported types. Also this functionality somewhat overlaps with the
Kafka Proxy that some Kafka providers have already implemented in some form.
But all this should be discussed in a KIP, so I absolutely encourage you to
create one.
> Add a new compression option on the broker side
> -----------------------------------------------
>
> Key: KAFKA-17296
> URL: https://issues.apache.org/jira/browse/KAFKA-17296
> Project: Kafka
> Issue Type: New Feature
> Components: compression, config
> Affects Versions: 3.8.0
> Reporter: xiaochen.zhou
> Priority: Minor
> Labels: kip
> Fix For: 4.0.0
>
>
> Compressing data can reduce the bandwidth required for network transmission
> and decrease disk storage usage. If the compression types of the client and
> broker are inconsistent, it may lead to increased resource usage on the
> broker, such as higher CPU usage. Currently, the default compression type on
> the Kafka broker side is "PRODUCER". As I understand it, if the client does
> not use compression, the broker will not use compression either.
> Can we add a new compression option on the broker side, such as
> "PRODUCER_OR_LZ4". With this option, if the client uses a compression type
> (like Snappy), the broker would follow the client's compression type
> (Snappy). If the client does not use compression, the broker would default to
> using LZ4.
> If this suggestion makes sense, I would be happy to implement it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
