[
https://issues.apache.org/jira/browse/CASSANDRA-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782184#comment-17782184
]
Branimir Lambov commented on CASSANDRA-18533:
---------------------------------------------
1. Yes, precisely.
2. The key cache is constructed in a completely separate portion of the code,
isn't it? Ignore the key cache settings (except migration), I don't think
changing this is something we can do at the moment.
3. Although it is not at the moment, the row index granularity in particular
should be a table-level property -- there's no real reason to use one setting
for all tables, and there's an advantage to be had by making it configurable.
However, things like the key cache size or index summary capacity are something
to be shared, not just between tables but also potentially between formats; I
don't want to get into a complicated solution for this, I would either ignore
any table-level modification for these (with a warning) or check that the value
is the same among all tables. This, along with format variations (e.g.
"bti-fast"), is also out of scope for this ticket.
> Move format-specific sstable options into the format configuration
> ------------------------------------------------------------------
>
> Key: CASSANDRA-18533
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18533
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Schema, Local/SSTable
> Reporter: Branimir Lambov
> Assignee: Maxwell Guo
> Priority: Normal
> Fix For: 5.x
>
>
> This mainly concerns cassandra yaml settings:
> - {{column_index_size}}, which should also be renamed to
> {{row_index_granularity}}
> - {{column_index_cache_size}}
> - {{index_summary_capacity}}
> - {{index_summary_resize_interval}}
> and possibly
> - {{key_cache_size}}, {{key_cache_keys_to_save}}, {{key_cache_save_period}},
> {{key_cache_migrate_during_compaction}}
> - {{sstable_preemptive_open_interval}}
> Existing settings should be deprecated but still picked up if defined.
> At this point we will not consider table-level options that make better sense
> as format parameters ({{min/max_index_interval}}, {{bloom_filter_fp_chance}},
> {{crc_check_chance}} and possibly {{compression}}), because we do not yet
> support per-table format selection/configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
