Yup, there are other types of indexing like that in PlayOrm which do it
differently so all nodes are not hit so it works better for instance if you are
partitioning your data and you query into just a single partition so it doesn't
put load on all the nodes. (of course, you have to have a
Thanks Dean. Any reason why it is sequential ? It is to avoid loading all the
nodes and see if one node can return the desired results ?
-Original Message-
From: Hiller, Dean [mailto:dean.hil...@nrel.gov]
Sent: 21 August 2013 07:36
To: user@cassandra.apache.org
Subject: Re: Secondary
Message-
From: Hiller, Dean [mailto:dean.hil...@nrel.gov]
Sent: 21 August 2013 07:36
To: user@cassandra.apache.org
Subject: Re: Secondary Index Question
Yup, there are other types of indexing like that in PlayOrm which do it
differently so all nodes are not hit so it works better for instance
results ?
-Original Message-
From: Hiller, Dean [mailto:dean.hil...@nrel.gov]
Sent: 21 August 2013 07:36
To: user@cassandra.apache.org
Subject: Re: Secondary Index Question
Yup, there are other types of indexing like that in PlayOrm which do it
differently so all nodes are not hit so
On Tue, Aug 20, 2013 at 5:57 PM, Kanwar Sangha kan...@mavenir.com wrote:
Hi – I was reading some blogs on implementation of secondary indexes in
Cassandra and they say that “the read requests are sent sequentially to all
the nodes” ?
** **
So if I have a query to fetch ALL records
