On Tue, Aug 20, 2013 at 5:57 PM, Kanwar Sangha 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 with the secon
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 Index Question
>
>Yup, there are other types of indexing like that in PlayOrm whi
>
>
>-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 n
:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Secondary Index Question
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 t
e.org>"
mailto:user@cassandra.apache.org>>
Subject: Secondary Index Question
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 with
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 with the secondary index filter, will
the co-ordinator node send the requests to nodes one b
On Mon, Jan 14, 2013 at 11:55 PM, aaron morton wrote:
> Sylvain,
> Out of interest if the select is…
>
> select * from test where interval = 7 and severity = 3 order by id desc
> ;
>
> Would the the ordering be a no-op or would it still run ?
>
Yes, as Shahryar said this is currently rejected b
Aaron
If you have order buy whit a column with a secondary index in a where
clause it fails with:
Bad Request: ORDER BY with 2ndary indexes is not supported.
Best Regards
Shahryar
On Mon, Jan 14, 2013 at 5:55 PM, aaron morton wrote:
> Sylvain,
> Out of interest if the select is…
>
> select
Sylvain,
Out of interest if the select is…
select * from test where interval = 7 and severity = 3 order by id desc ;
Would the the ordering be a no-op or would it still run ?
Or more generally does including an ORDER BY clause that matches the CLUSTERING
ORDER BY DDL clause incur ove
On Mon, Jan 14, 2013 at 5:04 PM, Shahryar Sedghi wrote:
> Can I always count on this order, or it may change in the future?
>
I would personally rely on it. I don't see any reason why we would change
that internally and besides I suspect you won't be the only one to rely on
it so we won't take
CQL 3 in Cassandra 1.2 does not allow order by when it is a wide row and
a column with secondary index is used in a where clause which makes
sense. So the question is:
I have a test table like this:
CREATE TABLE test(
interval int,
id uuid,
severity int,
PRIMARY KEY (interval
"user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
>mailto:user@cassandra.apache.org>>
>Date: Tuesday, December 11, 2012 3:45 PM
>To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
>mailto:user@cassandra.apache.org>>
&
ot;
mailto:user@cassandra.apache.org>>
Subject: RE: Primary/secondary index question / best practices?
Dean, thank you for your response. To the second half of the query, I’m a
little concerned about the secondary index approach since the indexes that I
want to create are columns with high
imary/secondary index question / best practices?
Hard to help out on a design without specifics but here is some advice based on
the limited information
Primary key : yes, must be cluster unique. TimeUUID or UUIDPlayOrm has
very unique TimeUUID like keys as in this one 7AL2S8Y.b1 (b1 i
gt;"
>mailto:stephen.m.thomp...@wellsfargo.co
>m>>
>Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
>mailto:user@cassandra.apache.org>>
>Date: Tuesday, December 11, 2012 2:49 PM
>To: "user@cassandra.apache.org<mailto:user
gt;
Date: Tuesday, December 11, 2012 2:49 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Primary/secondary index question / best practices?
m my reading, it seems like I need a UUID column that will be my primary i
Hi folks - I'm doing an informal proof-of-concept with Cassandra and I've been
getting some conflicting information about how my data layout should go.
Perhaps somebody could point me in the right direction.
I have a column family that will have billions of rows of data. The data do
not have
17 matches
Mail list logo
