[jira] [Commented] (CASSANDRA-11408) simple compaction defaults for common scenarios

["Jeff Jirsa (JIRA)" <ji...@apache.org>]

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

Jeff Jirsa commented on CASSANDRA-11408:
----------------------------------------

Apologies in advance for bikeshedding, but why limit it to compaction? Why not do named profiles for all metadata? Especially since compaction changes often necessitate bloom filter changes and read repair changes , why not:

{code:title=example, syntax variant |borderStyle=solid}
ALTER TABLE foo.bar WITH profile = 'timeseries-hourly-for-a-week';
{code}




> simple compaction defaults for common scenarios
> -----------------------------------------------
>
>                 Key: CASSANDRA-11408
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11408
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Shook
>
> As compaction strategies get more flexible over time, some users might prefer to have a simple named profile for their settings.
> {code:title=example, syntax variant|borderStyle=solid}
> alter table foo.bar with compaction = 'timeseries-hourly-for-a-week';
> {code}
> {code:title=example, syntax variant |borderStyle=solid}
> alter table foo.bar with compaction = { 'profile' : 'key-value-balanced-ops' };
> {code}
> These would simply be a map into sets of well-tested and documented defaults across any of the core compaction strategies.
> This would simplify setting up compaction for well-understood workloads, but still allow for customization where desired.



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