[
https://issues.apache.org/jira/browse/CASSANDRA-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264977#comment-13264977
]
Jonathan Ellis commented on CASSANDRA-4197:
-------------------------------------------
I think we can do this without having to expose these to be manually tuned
(which IMO is the Wrong Solution):
- If the parent CF has row caching enabled, enable row caching on the 2I CF if
our stats indicate that it is high cardinality; otherwise enable key caching
- If the parent CF has key caching enabled, enable key caching on the 2I CF
- Otherwise leave the 2I CF at Caching.NONE
> Index caching
> -------------
>
> Key: CASSANDRA-4197
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4197
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Priority: Minor
> Fix For: 1.1.1
>
>
> Currently, the "hidden" CFs backing secondary indexes are created with
> Caching.NONE, which can result in slower-than-expected index queries.
--
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
