[
https://issues.apache.org/jira/browse/CASSANDRA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236627#comment-13236627
]
Jiri Eichler commented on CASSANDRA-3961:
-----------------------------------------
If there are column families of very different sizes, such option will save a
lot of memory and since it's not any technical limitation of the Cassandra's
design, this option should be available.
> Make index_interval configurable per column family
> --------------------------------------------------
>
> Key: CASSANDRA-3961
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3961
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.0.7
> Environment: Cassandra 1.0.7/unix
> Reporter: Radim Kolar
> Priority: Minor
>
> After various experiments with mixing OLTP a OLAP workload running on single
> cassandra cluster i discovered that lot of memory is wasted on holding index
> samples for CF which are rarely accessed or index is not much used for CF
> access because slices over keys are used.
> There is per column family setting for configuring bloom filters -
> bloom_filter_fp_chance. Please add setting index_interval configurable per CF
> as well. If this setting is not set or it is zero, default from
> cassandra.yaml will be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
