Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 87EE5200B33 for ; Wed, 15 Jun 2016 02:31:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 86458160A56; Wed, 15 Jun 2016 00:31:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DBACC160A06 for ; Wed, 15 Jun 2016 02:31:20 +0200 (CEST) Received: (qmail 31488 invoked by uid 500); 15 Jun 2016 00:31:19 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 31478 invoked by uid 99); 15 Jun 2016 00:31:19 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jun 2016 00:31:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id CBF40C0E1A for ; Wed, 15 Jun 2016 00:31:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.4 X-Spam-Level: * X-Spam-Status: No, score=1.4 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_RATIO_06=0.001, HTML_MESSAGE=2, KAM_HUGEIMGSRC=0.2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_REMOTE_IMAGE=0.01] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=datastax.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 1aAHzIy-lFEV for ; Wed, 15 Jun 2016 00:31:14 +0000 (UTC) Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 763635F295 for ; Wed, 15 Jun 2016 00:31:14 +0000 (UTC) Received: by mail-oi0-f49.google.com with SMTP id p204so10374640oih.3 for ; Tue, 14 Jun 2016 17:31:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datastax.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Q9AcuYgbFTnVPWK0HU6l7O/nIMP4CAJKiOc5SNkYs+4=; b=k7DkdJJ51rgHhPETGvm4yKm8Jb6g6145Rxc2cLPZT0iCrmhkfnv/HBSY58CTk6TF55 dlvAmgLv+FcTgeIfSJ1C0JNAii5jyGA+boxXp0GgnhLL/LOU7YcOZHHYPCAArlmPB9wm xrKfUzSWRT88YNkGk/g7Kk+w0LxCdyhLbypcg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Q9AcuYgbFTnVPWK0HU6l7O/nIMP4CAJKiOc5SNkYs+4=; b=BFRyKeJiPD4sIl1AomN65WKiaag/Nv1S+6y/L2YGSCuC7ytFFSLUsk/2AFlhkjc7ZC VdIC95R/+fEUnJOvpq9JWmSbzO3NX+8HJWDmj4qd7U+iKF8pfjrIqoPL9rij5PxtQm+v JpfatH6l1dHA8oSVBFf9g8Cl4zwdjhKLqluu8e5tYl/hYUcX4tYN5yH78bnk53dZ4HUQ la++/r6m2l0tpI0k7f3JNGESuyV78s3fxYMRB5hXsqgKOfKy05ziRofDyNo6z/N+iNBq f1+SeDN+DvA0DOQ2c9EhxbTuVZ8vQzH7C65jDzsM2tiMK11eYcx6F5FiqZTYDisV5bPC EFPw== X-Gm-Message-State: ALyK8tKIZSwENV/o92ZMwI9sGkQm36ZHdesOKOKTn/hKPKl1511A0MKFU756HA6tlsbpE1N7Eez/BeoJlEqNOcdQ X-Received: by 10.157.5.212 with SMTP id 78mr8790703otd.60.1465950666936; Tue, 14 Jun 2016 17:31:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.226.169 with HTTP; Tue, 14 Jun 2016 17:31:06 -0700 (PDT) In-Reply-To: References: From: Joel Knighton Date: Tue, 14 Jun 2016 19:31:06 -0500 Message-ID: Subject: Re: select query on entire primary key returning more than one row in result To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11398e02c2f0a50535463c31 archived-at: Wed, 15 Jun 2016 00:31:22 -0000 --001a11398e02c2f0a50535463c31 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 wouldn't have statics in its ColumnFilter (basically, the filter we apply when deciding if we need to look for the requested data in more SSTables). This was an incorrect understanding - in order to preserve the CQL semantic (see CASSANDRA-6588 for details), we are including all columns, including the static columns, in the fetched columns, which means they are part of the ColumnFilter. I believe there may be an opportunity for an optimization here, but that's a whole different discussion. I now agree that these are the same issue. You are correct in your analysis that 3.4/3.5 are the only affected versions. It has been patched in release 3.6 forward and was not introduced until 3.4 Thanks for sticking with me on this - I'm going to resolve CASSANDRA-12003 as a duplicate of CASSANDRA-11513. On Tue, Jun 14, 2016 at 4:21 PM, Bhuvan Rawal wrote: > 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. The= y > both don't occur in 3.0.4, 3.6 & 3.7. > > Please find below the results of selecting only pk and clustering key fro= m 11513. > It has also been verified that both issues occur while selecting all / > filtered rows therefore selection criteria is not an issue filtering by > WHERE is: > > cqlsh:ks> select pk,a from test0 where pk=3D0 and a=3D2; > > pk | a > ----+--- > 0 | 1 > 0 | 2 > 0 | 3 > > We can verify this claim by applying 11513 Patch to 3.5 Tag and build & > test for 12003. If it is fixed then we can guarantee the claim. Let me > know if any further input may possibly be required here. > > On Wed, Jun 15, 2016 at 2:23 AM, Joel Knighton > wrote: > >> 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 cluster= ing >> columns. I'd be cautious about concluding that CASSANDRA-12003 and >> CASSANDRA-11513 are the same issue and that CASSANDRA-12003 is fixed. >> >> If you have a reproduction path for CASSANDRA-12003, I'd recommend >> attaching it to a ticket, and someone can investigate internals to see i= f >> CASSANDRA-11513 (or something else entirely) fixed the issue. >> >> On Tue, Jun 14, 2016 at 2:13 PM, Bhuvan Rawal >> wrote: >> >>> 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=3D0 and a=3D2; >>> >>> >>> >>> On Wed, Jun 15, 2016 at 12:39 AM, Joel Knighton < >>> joel.knighton@datastax.com> wrote: >>> >>>> 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 >>>>> locally on >>>>> 3.5, possible duplicate. >>>>> >>>>> On Wed, Jun 15, 2016 at 12:29 AM, Joel Knighton < >>>>> joel.knighton@datastax.com> wrote: >>>>> >>>>>> 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 woul= d help >>>>>> narrow the issue down farther. I've played around locally with simil= ar >>>>>> schemas (sans the stratio indices) and couldn't reproduce the issue. >>>>>> >>>>>> On Tue, Jun 14, 2016 at 1:41 PM, Bhuvan Rawal >>>>>> wrote: >>>>>> >>>>>>> Jira CASSANDRA-12003 >>>>>>> Has been >>>>>>> created for the same. >>>>>>> >>>>>>> On Tue, Jun 14, 2016 at 11:54 PM, Atul Saroha < >>>>>>> atul.saroha@snapdeal.com> wrote: >>>>>>> >>>>>>>> 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=E2=80=99= t think >>>>>>>> this plug-in could led to change in behaviour of cassandra write t= o table's >>>>>>>> memtable. >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------= --------------------------------------------------- >>>>>>>> Atul Saroha >>>>>>>> *Lead Software Engineer* >>>>>>>> *M*: +91 8447784271 *T*: +91 124-415-6069 *EXT*: 12369 >>>>>>>> Plot # 362, ASF Centre - Tower A, Udyog Vihar, >>>>>>>> Phase -4, Sector 18, Gurgaon, Haryana 122016, INDIA >>>>>>>> >>>>>>>> On Tue, Jun 14, 2016 at 9:54 PM, Tyler Hobbs >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Is 'id' your partition key? I'm not familiar with the stratio >>>>>>>>> indexes, but it looks like the primary key columns are both index= ed. >>>>>>>>> Perhaps this is related? >>>>>>>>> >>>>>>>>> On Tue, Jun 14, 2016 at 1:25 AM, Atul Saroha < >>>>>>>>> atul.saroha@snapdeal.com> wrote: >>>>>>>>> >>>>>>>>>> After further debug, this issue is found in in-memory memtable a= s >>>>>>>>>> doing nodetool flush + compact resolve the issue. And there is n= o batch >>>>>>>>>> write used for this table which is showing issue. >>>>>>>>>> Table properties: >>>>>>>>>> >>>>>>>>>> WITH CLUSTERING ORDER BY (f_name ASC) >>>>>>>>>>> AND bloom_filter_fp_chance =3D 0.01 >>>>>>>>>>> AND caching =3D {'keys': 'ALL', 'rows_per_partition': 'NONE= '} >>>>>>>>>>> AND comment =3D '' >>>>>>>>>>> AND compaction =3D {'class': >>>>>>>>>>> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrateg= y', >>>>>>>>>>> 'max_threshold': '32', 'min_threshold': '4'} >>>>>>>>>>> AND compression =3D {'chunk_length_in_kb': '64', 'class': >>>>>>>>>>> 'org.apache.cassandra.io.compress.LZ4Compressor'} >>>>>>>>>>> AND crc_check_chance =3D 1.0 >>>>>>>>>>> AND dclocal_read_repair_chance =3D 0.1 >>>>>>>>>>> AND default_time_to_live =3D 0 >>>>>>>>>>> AND gc_grace_seconds =3D 864000 >>>>>>>>>>> AND max_index_interval =3D 2048 >>>>>>>>>>> AND memtable_flush_period_in_ms =3D 0 >>>>>>>>>>> AND min_index_interval =3D 128 >>>>>>>>>>> AND read_repair_chance =3D 0.0 >>>>>>>>>>> AND speculative_retry =3D '99PERCENTILE'; >>>>>>>>>>> CREATE CUSTOM INDEX nbf_index ON nbf () USING >>>>>>>>>>> 'com.stratio.cassandra.lucene.Index' WITH OPTIONS =3D {'refresh= _seconds': >>>>>>>>>>> '1', 'schema': '{ >>>>>>>>>>> fields : { >>>>>>>>>>> id : {type : "bigint"}, >>>>>>>>>>> f_d_name : { >>>>>>>>>>> type : "string", >>>>>>>>>>> indexed : true, >>>>>>>>>>> sorted : false, >>>>>>>>>>> validated : true, >>>>>>>>>>> case_sensitive : false >>>>>>>>>>> } >>>>>>>>>>> } >>>>>>>>>>> }'}; >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ----------------------------------------------------------------= ----------------------------------------------------- >>>>>>>>>> Atul Saroha >>>>>>>>>> *Lead Software Engineer* >>>>>>>>>> *M*: +91 8447784271 *T*: +91 124-415-6069 *EXT*: 12369 >>>>>>>>>> Plot # 362, ASF Centre - Tower A, Udyog Vihar, >>>>>>>>>> Phase -4, Sector 18, Gurgaon, Haryana 122016, INDIA >>>>>>>>>> >>>>>>>>>> On Mon, Jun 13, 2016 at 11:11 PM, Siddharth Verma < >>>>>>>>>> verma.siddharth@snapdeal.com> wrote: >>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Tyler Hobbs >>>>>>>>> DataStax >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> >>>>>> Joel Knighton >>>>>> Cassandra Developer | joel.knighton@datastax.com >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> Joel Knighton >>>> Cassandra Developer | joel.knighton@datastax.com >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> >> -- >> >> >> >> Joel Knighton >> Cassandra Developer | joel.knighton@datastax.com >> >> >> >> >> >> >> >> > > --=20 Joel Knighton Cassandra Developer | joel.knighton@datastax.com --001a11398e02c2f0a50535463c31 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Great work, Bhuvan - I sat down after work to look at this= more carefully.=C2=A0

For a short summary, you are corr= ect.=C2=A0

For a longer summary, I initially thoug= ht 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 wouldn= 't have statics in its ColumnFilter (basically, the filter we apply whe= n deciding if we need to look for the requested data in more SSTables). Thi= s was an incorrect understanding - in order to preserve the CQL semantic (s= ee CASSANDRA-6588 for details), we are including all columns, including the= static columns, in the fetched columns, which means they are part of the C= olumnFilter. I believe there may be an opportunity for an optimization here= , but that's a whole different discussion. I now agree that these are t= he same issue.

You are correct in your analysis th= at 3.4/3.5 are the only affected versions. It has been patched in release 3= .6 forward and was not introduced until 3.4

Thanks= for sticking with me on this - I'm going to resolve CASSANDRA-12003 as= a duplicate of CASSANDRA-11513.

=
On Tue, Jun 14, 2016 at 4:21 PM, Bhuvan Rawal <bhu1rawal@gmail.com> wrote:
Joel,

Thanks for your reply, I have = checked and found that the behavior is same in case of=C2=A0CASSANDRA-1151= 3. I have verified this=C2=A0behavior= =C2=A0(for both 11513 & 12003) to occur in=C2=A0case of 3.4 & 3.5. = They both don't occur in 3.0.4, 3.6 & 3.7.=C2=A0
<= span style=3D"font-size:12.8px">
Please find below the results of selecting only pk and clusteri= ng key from=C2=A011513. It has also= been verified that both issues occur while selecting all / filtered rows t= herefore selection criteria is not an issue filtering by WHERE is:

cqlsh:ks> select pk,a from test0 where pk= =3D0 and a=3D2;

=C2=A0pk | a
----+---
=C2=A0 0 | 1
=C2=A0 0 | 2
=C2=A0 0 | 3

We can verify this claim by applying 11513 Patch to 3= .5 Tag and build & test for 12003. If it is fixed then we can guarantee= the claim.=C2=A0Let me know if any further input may possibly be re= quired here.

On Wed, Jun 15, 2016 at 2:2= 3 AM, Joel Knighton <joel.knighton@datastax.com> wr= ote:
The important part = of that query is that it's selecting a static column (with select *), n= ot whether it is filtering on one. In CASSANDRA-12003 and this thread, it l= ooks like you're only selecting the primary and clustering columns. I&#= 39;d be cautious about concluding that CASSANDRA-12003 and CASSANDRA-11513 = are the same issue and that CASSANDRA-12003 is fixed.=C2=A0

<= div>If you have a reproduction path for CASSANDRA-12003, I'd recommend = attaching it to a ticket, and someone can investigate internals to see if C= ASSANDRA-11513 (or something else entirely) fixed the issue.

On Tue, Ju= n 14, 2016 at 2:13 PM, Bhuvan Rawal <bhu1rawal@gmail.com> = wrote:
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=3D0 and a=3D2;


On Wed, Jun 15, 2016 at 12:39 AM, Joe= l Knighton <joel.knighton@datastax.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
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 <bhu1r= awal@gmail.com> wrote:
I can reproduce=C2=A0CASSA= NDRA-11513=C2=A0locally on 3.5, possible duplicate.

On Wed, Jun 15, 2016 = at 12:29 AM, Joel Knighton <joel.knighton@datastax.com> wrote:
There's = some precedent for similar issues with static columns in 3.5 with https://issues.apache.org/jira/browse/CASSANDRA-11513=C2=A0- a determ= inistic (or somewhat deterministic) path for reproduction would help narrow= the issue down farther. I've played around locally with similar schema= s (sans the stratio indices) and couldn't reproduce the issue.

On Tue, Ju= n 14, 2016 at 1:41 PM, Bhuvan Rawal <bhu1rawal@gmail.com> = wrote:
Jira=C2=A0CASSANDRA-12003=C2=A0Has been created for the same.

On Tue, Jun 14, 2016 at 1= 1:54 PM, Atul Saroha <atul.saroha@snapdeal.com> wrote= :
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= =E2=80=99t think this plug-in could led to change in behaviour of cassandra= write to table's memtable.
<= br clear=3D"all">
----------------------------------------------= -----------------------------------------------------------------------
= Atul SarohaLead Software Engineer
M: +91 8447784271=C2=A0T: +91= 124-415-6069 EXT: 12369
Plot # 362, ASF Centre - Tower = A, Udyog Vihar,
=C2=A0Phase -4, Sector 18, Gurgaon, Haryana 122016, INDI= A

On Tue, Jun 14, 2016 at 9:5= 4 PM, Tyler Hobbs <tyler@datastax.com> wrote:
Is 'id' your partition key? I= 'm not familiar with the stratio indexes, but it looks like the primary= key columns are both indexed.=C2=A0 Perhaps this is related?

On Tue, Jun= 14, 2016 at 1:25 AM, Atul Saroha <atul.saroha@snapdeal.com>= wrote:
After fur= ther debug, this issue is found in in-memory memtable as doing nodetool flu= sh + compact resolve the issue. And there is no batch write used for this t= able which is showing issue.
Table properties:

WITH CLUSTERING ORDER BY (f_name ASC)
= =C2=A0=C2=A0=C2=A0 AND bloom_filter_fp_chance =3D 0.01
=C2=A0=C2=A0=C2= =A0 AND caching =3D {'keys': 'ALL', 'rows_per_partition= ': 'NONE'}
=C2=A0=C2=A0=C2=A0 AND comment =3D ''
= =C2=A0=C2=A0=C2=A0 AND compaction =3D {'class': 'org.apache.cas= sandra.db.compaction.SizeTieredCompactionStrategy', 'max_threshold&= #39;: '32', 'min_threshold': '4'}
=C2=A0=C2=A0= =C2=A0 AND compression =3D {'chunk_length_in_kb': '64', = 9;class': 'org.apache.cassandra.io.compress.LZ4Compressor'}
= =C2=A0=C2=A0=C2=A0 AND crc_check_chance =3D 1.0
=C2=A0=C2=A0=C2=A0 AND d= clocal_read_repair_chance =3D 0.1
=C2=A0=C2=A0=C2=A0 AND default_time_to= _live =3D 0
=C2=A0=C2=A0=C2=A0 AND gc_grace_seconds =3D 864000
=C2=A0= =C2=A0=C2=A0 AND max_index_interval =3D 2048
=C2=A0=C2=A0=C2=A0 AND memt= able_flush_period_in_ms =3D 0
=C2=A0=C2=A0=C2=A0 AND min_index_interval = =3D 128
=C2=A0=C2=A0=C2=A0 AND read_repair_chance =3D 0.0
=C2=A0=C2= =A0=C2=A0 AND speculative_retry =3D '99PERCENTILE';
CREATE CUSTO= M INDEX nbf_index ON nbf () USING 'com.stratio.cassandra.lucene.Index&#= 39; WITH OPTIONS =3D {'refresh_seconds': '1', 'schema&#= 39;: '{
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 fields : {
=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 id=C2=A0 : = {type : "bigint"},
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 f_d_name : {
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 type=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : "string",
= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 indexed=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : true,=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 sorted=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 := false,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 validated=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : true,=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 case_sensitive : false
=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }
=C2=A0=C2=A0= =C2=A0 }'};


<= div>
---------------------------------------------------= ------------------------------------------------------------------
Atul = Saroha
= Lead Software Engineer
M= : +91 8447784271=C2=A0T: +91 124-415-6069 EXT: 12369=
Plot # 362, ASF Centre - Tower A, Udyog Vihar,
=C2=A0Phase -4, = Sector 18, Gurgaon, Haryana 122016, INDIA

On Mon, Jun 13, 2016 at 11:11 PM, Siddharth = Verma <verma.siddharth@snapdeal.com> wrote:
No, = all rows were not the same.
Querying only on the partition key gi= ves 20 rows.
In the erroneous result, while querying on partition = key and clustering key, we got 16 of those 20 rows.

And for &q= uot;tombstone_threshold" there isn't any entry at column family level.
Thanks,
Siddharth Verma






--
Tyler Hobbs
DataStax
<= /div>





<= font color=3D"#888888">--
=

=

Joel Knighton
Cass= andra Developer | joel.knighton@datastax.com


=





--
=



--
=



--
=
=

Joel Knighton
<= span style=3D"font-size:16px;font-family:Calibri;color:rgb(0,0,0);vertical-= align:baseline;white-space:pre-wrap;background-color:transparent">Cassandra= Developer | joel.knighton@datastax.com


<= span style=3D"font-size:12px;font-family:Arial;color:rgb(17,85,204);text-de= coration:underline;vertical-align:baseline;white-space:pre-wrap"> =
=

--001a11398e02c2f0a50535463c31--