[
https://issues.apache.org/jira/browse/CASSANDRA-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14745573#comment-14745573
]
Pavel Baranov commented on CASSANDRA-8530:
--
Tom, we decided to restructure our tables and not
[
https://issues.apache.org/jira/browse/CASSANDRA-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255884#comment-14255884
]
Pavel Baranov commented on CASSANDRA-8530:
--
Providing a self-contained script
[
https://issues.apache.org/jira/browse/CASSANDRA-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255898#comment-14255898
]
Pavel Baranov commented on CASSANDRA-8530:
--
What I get from this is that the
Pavel Baranov created CASSANDRA-8530:
Summary: Query on a secondary index creates huge CPU spike +
unable to trace
Key: CASSANDRA-8530
URL: https://issues.apache.org/jira/browse/CASSANDRA-8530
Pavel Baranov created CASSANDRA-8526:
Summary: Query on a secondary index stopped working
Key: CASSANDRA-8526
URL: https://issues.apache.org/jira/browse/CASSANDRA-8526
Project: Cassandra
[
https://issues.apache.org/jira/browse/CASSANDRA-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Baranov updated CASSANDRA-8526:
-
Description:
After upgrading from cassandra 2.0.10 to 2.1.2 this type of query (using
[
https://issues.apache.org/jira/browse/CASSANDRA-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254171#comment-14254171
]
Pavel Baranov commented on CASSANDRA-8526:
--
It looks like I found a solution
[
https://issues.apache.org/jira/browse/CASSANDRA-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254171#comment-14254171
]
Pavel Baranov edited comment on CASSANDRA-8526 at 12/19/14 10:52 PM:
