You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Shook (JIRA)" <ji...@apache.org> on 2016/03/23 01:23:25 UTC
[jira] [Updated] (CASSANDRA-11408) simple compaction defaults for
common scenarios
[ https://issues.apache.org/jira/browse/CASSANDRA-11408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Shook updated CASSANDRA-11408:
---------------------------------------
Description:
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.
was:
As compaction strategies get more flexible over time, some users might prefer to have a simple named profile for their settings.
For example,
alter table foo.bar with compaction = 'timeseries-hourly-for-a-week';
or, with slightly different syntax:
alter table foo.bar with compaction = { 'profile' : 'key-value-balanced-ops' };
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.
> 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)