Re: Duplicated key with an IN statement

On Thu, Feb 4, 2016 at 9:57 AM, Jack Krupansky wrote: > there's a bug in CHANGES.TXT for this issue. It says: "Duplicate rows > returned when in clause has repeated values (CASSANDRA-6707)", but the > issue number is really 6706. > Thanks, I've fixed this. -- Tyler Hobbs DataStax

Re: Duplicated key with an IN statement

fine a tuple >> being unique for a specific key, this is a real problem to be able to have >> a result set having multiple time the same key, which should be unique. >> This is why on every SQL implementation, this is not happening >> >> >> >> I think this is a

RE: Duplicated key with an IN statement

Thanks :) De : Robert Wille [mailto:rwi...@fold3.com] Envoyé : Thursday, February 04, 2016 4:37 PM À : user@cassandra.apache.org Objet : Re: Duplicated key with an IN statement You shouldn't be using IN anyway. It is better to issue multiple queries, each for a single key, and issue th

Re: Duplicated key with an IN statement

mail.com>] Envoyé : Thursday, February 04, 2016 11:55 AM À : Edouard COLE Cc : user@cassandra.apache.org<mailto:user@cassandra.apache.org> Objet : Re: Duplicated key with an IN statement Hi, This is interesting. It seems rational that if you are looking at 2 keys and both exist (which is

Re: Duplicated key with an IN statement

be unique. > This is why on every SQL implementation, this is not happening > > > > I think this is a bug > > > > Edouard COLE > > > > > > *De :* Alain RODRIGUEZ [mailto:arodr...@gmail.com] > *Envoyé :* Thursday, February 04, 2016 11:55 AM > *À :* Edou

RE: Duplicated key with an IN statement

ard COLE De : Alain RODRIGUEZ [mailto:arodr...@gmail.com] Envoyé : Thursday, February 04, 2016 11:55 AM À : Edouard COLE Cc : user@cassandra.apache.org Objet : Re: Duplicated key with an IN statement Hi, This is interesting. It seems rational that if you are looking at 2 keys and both exist (which

Re: Duplicated key with an IN statement

Hi, This is interesting. It seems rational that if you are looking at 2 keys and both exist (which is the case) it returns you 2 keys, it. Yet, I just checked this kind of command on MySQL and it gives a one line result. So here CQL differs from SQL (at least MySQL). I know we are trying to fit a

Duplicated key with an IN statement

Hello, I just discovered this, and I think this is weird: ed@debian:~$ cqlsh 192.168.10.8 Connected to _CLUSTER_ at 192.168.10.8:9160. [cqlsh 4.0.1 | Cassandra 2.0.14.459 | CQL spec 3.1.1 | Thrift protocol 19.39.0] Use HELP for help. cqlsh> USE ks-test ; cqlsh:ks-test> CREATE TABLE t (