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

Cheng-Kai, Zhang commented on KAFKA-13361:
------------------------------------------

[~mimaison]  much thanks for providing me with more detail. :)
I would start by studying the changes in your 
[PR|https://github.com/apache/kafka/pull/15516] and figure out how to further 
add in features of KIP-780

> Support fine-grained compression options
> ----------------------------------------
>
>                 Key: KAFKA-13361
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13361
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients, core
>            Reporter: Dongjin Lee
>            Assignee: Dongjin Lee
>            Priority: Major
>              Labels: needs-kip
>
> Adds the following options into the Producer, Broker, and Topic 
> configurations:
>  * compression.gzip.buffer: the buffer size that feeds raw input into the 
> Deflator or is fed by the uncompressed output from the Deflator. (available: 
> [512, ), default: 8192(=8kb).)
>  * compression.snappy.block: the block size that snappy uses. (available: 
> [1024, ), default: 32768(=32kb).)
>  * compression.lz4.block: the block size that lz4 uses. (available: [4, 7], 
> (means 64kb, 256kb, 1mb, 4mb respectively), default: 4.)
>  * compression.zstd.window: enables long mode; the log of the window size 
> that zstd uses to memorize the compressing data. (available: [10, 22], 
> default: 0 (disables long mode.))
> All of the above are different but somewhat in common from the point of 
> compression process in that it impacts the memorize size during the process.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to