> I don't know. How do I find out? The only mention about query plan in
> Cassandra I found is your article on your site, from 2011 and considering
> version 0.8.
See the help for TRACE in cqlsh
My general approach is to solve problems with the read path by making changes
to the write path. So
Hi,
by the way, some of the issues are summarised here:
https://issues.apache.org/jira/browse/CASSANDRA-6586 and here:
https://issues.apache.org/jira/browse/CASSANDRA-6587.
regards,
ondrej cernos
On Tue, Jan 14, 2014 at 9:48 PM, Ondřej Černoš wrote:
> Hi,
>
> thanks for the answer and sorry
Hi,
thanks for the answer and sorry for the delay. Let me answer inline.
On Wed, Dec 18, 2013 at 4:53 AM, Aaron Morton wrote:
> > * select id from table where token(id) > token(some_value) and
> secondary_index = other_val limit 2 allow filtering;
> >
> > Filtering absolutely kills the performa
> * select id from table where token(id) > token(some_value) and
> secondary_index = other_val limit 2 allow filtering;
>
> Filtering absolutely kills the performance. On a table populated with 130.000
> records, single node Cassandra server (on my i7 notebook, 2GB of JVM heap)
> and secondary
Hi all,
we are reimplementing a legacy interface of an inventory-like service
(currently built on top of mysql) on Cassandra and I thought I would share
some findings with the list. The interface semantics is given and cannot be
changed. We chose Cassandra due to its multiple datacenter capabiliti
