[
https://issues.apache.org/jira/browse/FLINK-14159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936536#comment-16936536
]
Congxian Qiu(klion26) commented on FLINK-14159:
-----------------------------------------------
[~jackylau] ah, I've misunderstood what you mean, The
{{getCompressionDecorator(executionConfig)}} did not specific the format of sst
files, but the checkpoint, please ref the doc[1] for more information
[1]
[https://ci.apache.org/projects/flink/flink-docs-stable/ops/state/large_state_tuning.html#compression]
> flink rocksdb StreamCompressionDecorator not right
> --------------------------------------------------
>
> Key: FLINK-14159
> URL: https://issues.apache.org/jira/browse/FLINK-14159
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
> Affects Versions: 1.9.0
> Reporter: jackylau
> Priority: Major
> Fix For: 1.10.0
>
>
> I think the current flink rocksdb StreamCompressionDecorator is not right
> when calling method
> getCompressionDecorator(executionConfig) ,which defalut value is false.That
> is to say, current compression is none.But I find rocksdb using
> {{options.compression}} to specify the compression to use. By default it is
> Snappy, which you can see here
> [https://github.com/facebook/rocksdb/wiki/RocksDB-Tuning-Guide]. And I use
> rocksdb tool sstdump to find it is indeed snappy compression.
> So I think it should be return SnappyStreamCompressionDecorator.INSTANCE
> rather than getCompressionDecorator( executionConfig)
> Coud i commit a PR?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
