[ https://issues.apache.org/jira/browse/CASSANDRA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504441#comment-13504441 ]
Jonathan Ellis commented on CASSANDRA-4478: ------------------------------------------- What if instead we make index_interval be CQL3 rows instead of partitions? > Make index_interval be measured in kb (instead of number of keys) > ----------------------------------------------------------------- > > Key: CASSANDRA-4478 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4478 > Project: Cassandra > Issue Type: Improvement > Reporter: Sylvain Lebresne > Priority: Minor > Fix For: 1.3 > > Attachments: 4478-incomplete.txt > > > Currently, index_interval is measured in number of keys: how may keys before > adding an entry to the index summary. After CASSANDRA-2319, each index entry > also contains the columns index for the row, so index entry can be a bit > bigger and of differing sizes. Measuring in number of keys is thus > sub-optimal and difficult to tune, since you might want a different setting > depending of whether your rows are big or small, but the setting is global. > So we should move to measuring the interval in bytes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira