[ https://issues.apache.org/jira/browse/CASSANDRA-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1488: -------------------------------------- Fix Version/s: 0.7 beta 2 It would be nice to automate it but it's more difficult than picking a reasonable memtable size since the key size, count, and key:row ratio all affect expected memory use. > Allow index sampling ratio to be configured in storage-conf > ----------------------------------------------------------- > > Key: CASSANDRA-1488 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1488 > Project: Cassandra > Issue Type: New Feature > Components: Core > Reporter: Jonathan Ellis > Assignee: Jon Hermes > Priority: Minor > Fix For: 0.6.6, 0.7 beta 2 > > Attachments: 1488.txt > > > Cassandra keeps a sample of row keys in memory to look up the right block of > index entries, to look up row data with. This is kept in the > SSTableReader.indexSummary field. (See Google's BigTable paper for a > high-level description of how this index works; cassandra's is slightly > different in the details but the idea is the same.) > We'd like to make IndexSummary.INDEX_INTERVAL configurable in > storage-conf.xml, i.e., in the DatabaseDescriptor class. For 0.6, a global > setting is fine. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.