Re: select query on entire primary key returning more than one row in result

Joel, Id rather thank you for naming 11513 earlier in the mail, I would have been lost in the code for a much longer time otherwise. Repeating what Tianshi mentioned in 11513 - "*Cassandra community is awesome! Should buy you a beer, Joel."* :) On Wed, Jun 15, 2016 at 6:01 AM, Joel Knighton wro

Re: select query on entire primary key returning more than one row in result

Great work, Bhuvan - I sat down after work to look at this more carefully. For a short summary, you are correct. For a longer summary, I initially thought the reproduction you provided would not run into the issue from 3.4/3.5 because it didn't select any static columns, which meant that it would

Re: select query on entire primary key returning more than one row in result

Joel, Thanks for your reply, I have checked and found that the behavior is same in case of CASSANDRA-11513 . I have verified this behavior (for both 11513 & 12003) to occur in case of 3.4 & 3.5. They both don't occur in 3.0.4, 3.6 & 3.7. Plea

Re: select query on entire primary key returning more than one row in result

The important part of that query is that it's selecting a static column (with select *), not whether it is filtering on one. In CASSANDRA-12003 and this thread, it looks like you're only selecting the primary and clustering columns. I'd be cautious about concluding that CASSANDRA-12003 and CASSANDR

Re: select query on entire primary key returning more than one row in result

I have verified this issue to be fixed in 3.6 and 3.7. And the issue mentioned on this thread is fixed as well. On Wed, Jun 15, 2016 at 12:43 AM, Bhuvan Rawal wrote: > Joel, > > If we look at the schema carefully: > > CREATE TABLE test0 ( > pk int, > a int, > b text, > s text sta

Re: select query on entire primary key returning more than one row in result

Joel, If we look at the schema carefully: CREATE TABLE test0 ( pk int, a int, b text, s text static, PRIMARY KEY (*pk, a)* ); and filtering is performed on clustering column a and its not a static column: select * from test0 where pk=0 and a=2; On Wed, Jun 15, 2016 at 12:

Re: select query on entire primary key returning more than one row in result

It doesn't seem to be an exact duplicate - CASSANDRA-11513 relies on you selecting a static column, which you weren't doing in the reported issue. That said, I haven't looked too closely. On Tue, Jun 14, 2016 at 2:07 PM, Bhuvan Rawal wrote: > I can reproduce CASSANDRA-11513 >

Re: select query on entire primary key returning more than one row in result

I can reproduce CASSANDRA-11513 locally on 3.5, possible duplicate. On Wed, Jun 15, 2016 at 12:29 AM, Joel Knighton wrote: > There's some precedent for similar issues with static columns in 3.5 with > https://issues.apache.org/jira/browse/C

Re: select query on entire primary key returning more than one row in result

There's some precedent for similar issues with static columns in 3.5 with https://issues.apache.org/jira/browse/CASSANDRA-11513 - a deterministic (or somewhat deterministic) path for reproduction would help narrow the issue down farther. I've played around locally with similar schemas (sans the str

Re: select query on entire primary key returning more than one row in result

Jira CASSANDRA-12003 Has been created for the same. On Tue, Jun 14, 2016 at 11:54 PM, Atul Saroha wrote: > Hi Tyler, > > This issue is mainly visible for tables having static columns, still > investigating. > We will try to test after remov

Re: select query on entire primary key returning more than one row in result

Hi Tyler, This issue is mainly visible for tables having static columns, still investigating. We will try to test after removing lucene index but I don’t think this plug-in could led to change in behaviour of cassandra write to table's memtable. ---

Re: select query on entire primary key returning more than one row in result

id is partition key, f_name is clustering key We weren't querying on lucene indexes. lucene index is on id, and f_d_name (another column). We were facing this issue on production in one column family, due to which we had to downgrade to 3.0.3

Re: select query on entire primary key returning more than one row in result

Is 'id' your partition key? I'm not familiar with the stratio indexes, but it looks like the primary key columns are both indexed. Perhaps this is related? On Tue, Jun 14, 2016 at 1:25 AM, Atul Saroha wrote: > After further debug, this issue is found in in-memory memtable as doing > nodetool fl

Re: select query on entire primary key returning more than one row in result

After further debug, this issue is found in in-memory memtable as doing nodetool flush + compact resolve the issue. And there is no batch write used for this table which is showing issue. Table properties: WITH CLUSTERING ORDER BY (f_name ASC) > AND bloom_filter_fp_chance = 0.01 > AND cach

Re: select query on entire primary key returning more than one row in result

No, all rows were not the same. Querying only on the partition key gives 20 rows. In the erroneous result, while querying on partition key and clustering key, we got 16 of those 20 rows. And for "*tombstone_threshold"* there isn't any entry at column family level. Thanks, Siddharth Verma

Re: select query on entire primary key returning more than one row in result

were all rows same? If not what was different ? What was droppable tombstone compaction ratio for that table/CF? On Mon, Jun 13, 2016 at 6:11 PM, Siddharth Verma < verma.siddha...@snapdeal.com> wrote: > Running nodetool compact fixed the issue. > > Could someone help out as why it occurred. >

Re: select query on entire primary key returning more than one row in result

Running nodetool compact fixed the issue. Could someone help out as why it occurred.

select query on entire primary key returning more than one row in result

Hi, We are facing this issue on production, We upgraded our cassandra from 3.0.3 to 3.5 When we ran a query with partition key and clustering column(entire primary key specified), we get 16 rows in return. We have 2DC's, each with RF 3 for our keyspace. 1. We connected with cqlsh, and setting co