cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11408) simple compaction defaults for common scenarios
Date Wed, 23 Mar 2016 04:16:25 GMT


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 WITH profile = 'timeseries-hourly-for-a-week';

> simple compaction defaults for common scenarios
> -----------------------------------------------
>                 Key: CASSANDRA-11408
>                 URL:
>             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 with compaction = 'timeseries-hourly-for-a-week';
> {code}
> {code:title=example, syntax variant |borderStyle=solid}
> alter table 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

View raw message