You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2016/03/07 09:38:41 UTC

[jira] [Resolved] (CASSANDRA-7987) Better defaults for CQL tables with clustering keys

     [ https://issues.apache.org/jira/browse/CASSANDRA-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne resolved CASSANDRA-7987.
-----------------------------------------
    Resolution: Later

I'm skeptical that we can easily find good criterion that guarantees that LCS is a better default. I'm also not sure we currently have the ressources to properly evaluate such criterion even if we had good candidates, and since that issue hasn't been updated in a while, closing as 'Later'.

> Better defaults for CQL tables with clustering keys
> ---------------------------------------------------
>
>                 Key: CASSANDRA-7987
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7987
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Priority: Minor
>              Labels: lhf
>             Fix For: 3.x
>
>
> We currently default to STCS regardless.  If a user creates a table with clustering keys (maybe specifically types with likely high cardinality?)  We should set compaction to LCS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)