incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rana Aich <aichr...@gmail.com>
Subject Re: Consequences of Cassandra key NOT unique
Date Thu, 29 Jul 2010 06:23:12 GMT
Thanks for your reply! I thought in that case a new row would be inserted
with a new timestamp and cassandra will report the new row. But how this
will affect my range query?

On Wed, Jul 28, 2010 at 7:03 PM, Benjamin Black <b@b3k.us> wrote:

> If you write new data with a key that is already present, the existing
> columns are overwritten or new columns are added.  There is no way to
> cause a duplicate key to be inserted.
>
> On Wed, Jul 28, 2010 at 6:16 PM, Rana Aich <aichrana@gmail.com> wrote:
> > Hello,
> > I was wondering what may the pitfalls in Cassandra when the Key value is
> not
> > UNIQUE?
> > Will it affect the range query performance?
> > Thanks and regards,
> > raich
> >
> >
>

Mime
View raw message