Hi Michael,
It sound like a bug but I could not reproduced it on 3.9 or on the current
3.11 branch (which will become 3.10).
Now, that does not mean that there are not problem. Something might be
different in your environement.
Do you still see that problem when you start from a clean environment with
a single node?
Benjamin
On Mon, Jan 30, 2017 at 10:19 AM, Micha <mich...@fantasymail.de> wrote:
> Hi,
>
> I have a second index on a static column and I don't
> understand the answer I get from my select.
>
> Maybe someone who understands the inner working of the second index can
> give me a hint on this (cassandra 3.9)
>
> A cut down version of the table is:
>
> create table demo (id text, id2 bigint static, added timestamp, source
> text static, dest text, primary key (id, added));
>
> create index on demo (id2);
>
> id and id2 match one to one.
>
> I make one insert:
> insert into demo (id, id2, added, source, dest) values ('id1', 22,
> '2017-01-28', 'src1', 'dst1');
>
>
> The "select from demo;" gives the expected answer of the one inserted row.
>
> But "select from demo where id2=22" gives 70 rows as result (all the same).
>
> Why? I have read
> https://www.datastax.com/dev/blog/cassandra-native-
> secondary-index-deep-dive
>
> but I don't get it...
>
> thanks for helping
> Michael
>
>
