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

Stefan Miklosovic commented on CASSANDRA-12937:
-----------------------------------------------

[~claude] I think it we are half-way there.

This in Config.java

{code}
public SSTableCompressionOptions sstable_compressor;
{code}

should be like this

{code}
public ParameterizedClass sstable_compressor;
{code}

to achieve this:

{code}
sstable_compression:
    - class_name: org.apache.cassandra.io.compress.LZ4Compressor
      parameters:
         - param1: "value1"
{code}

and

{code}
sstable_compression:
    - class_name: my.custom.compressor.Implementation
      parameters:
         - param2: "value2"
{code}

Right now, we need to treat custom implementations like a special case. A user 
has to make a difference between "custom compressor" and "compressor bundled in 
Cassandra". Why do we need such differentiation? We should treat all 
compressors equal when it comes to their configuration. I do not see why we 
would do that otherwise.

I am looking forward to the next iteration of the code!

> Default setting (yaml) for SSTable compression
> ----------------------------------------------
>
>                 Key: CASSANDRA-12937
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12937
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Config
>            Reporter: Michael Semb Wever
>            Assignee: Claude Warren
>            Priority: Low
>              Labels: AdventCalendar2021, lhf
>             Fix For: 5.x
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> In many situations the choice of compression for sstables is more relevant to 
> the disks attached than to the schema and data.
> This issue is to add to cassandra.yaml a default value for sstable 
> compression that new tables will inherit (instead of the defaults found in 
> {{CompressionParams.DEFAULT}}.
> Examples where this can be relevant are filesystems that do on-the-fly 
> compression (btrfs, zfs) or specific disk configurations or even specific C* 
> versions (see CASSANDRA-10995 ).
> +Additional information for newcomers+
> Some new fields need to be added to {{cassandra.yaml}} to allow specifying 
> the field required for defining the default compression parameters. In 
> {{DatabaseDescriptor}} a new {{CompressionParams}} field should be added for 
> the default compression. This field should be initialized in 
> {{DatabaseDescriptor.applySimpleConfig()}}. At the different places where 
> {{CompressionParams.DEFAULT}} was used the code should call 
> {{DatabaseDescriptor#getDefaultCompressionParams}} that should return some 
> copy of configured {{CompressionParams}}.
> Some unit test using {{OverrideConfigurationLoader}} should be used to test 
> that the table schema use the new default when a new table is created (see 
> CreateTest for some example).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to