The issue is fixed with nodetool scrub, now both rows are under the same
clustering.
I'll open a jira to analyze the source of this issue with Cassandra 3.11.3
Thanks.
Le jeu. 16 mai 2019 à 04:53, Jeff Jirsa a écrit :
> I don’t have a good answer for you - I don’t know if scrub will fix this
>
I don’t have a good answer for you - I don’t know if scrub will fix this (you
could copy an sstable offline and try it locally in ccm) - you may need to
delete and reinsert, though I’m really interested in knowing how this happened
if you weren’t ever exposed to #14008.
Can you open a JIRA? If
Jeff, In this case is there any solution to resolve that directly in the
sstable (compact, scrub...) or we have to apply a batch on the client level
(delete a partition and re write it)?
Thank you for your reply.
Le mer. 15 mai 2019 à 18:09, Ahmed Eljami a écrit :
> effectively, this was writte
effectively, this was written in 2.1.14 and we upgrade to 3.11.3 so we
should not be impacted by this issue ?!
thanks
s is determined by the partition key PLUS the clustering columns.
>>> Hard to tell from your data below, but is it possible that one of the
>>> clustering columns (perhaps g) has different values? That would easily
>>> explain the 2 rows returned – because they ARE dif
umns. Hard to tell from your data below, but is it possible that one of
>> the clustering columns (perhaps g) has different values? That would easily
>> explain the 2 rows returned – because they ARE different rows in the same
>> partition. In your data model, make sure you need all th
gt; might expect.
>
>
>
> Sean Durity
>
>
>
>
>
> *From:* Ahmed Eljami
> *Sent:* Wednesday, May 15, 2019 10:56 AM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] Two separate rows for the same partition !!
>
>
>
> Hi guys,
>
>
>
> W
partition. In your data
model, make sure you need all the clustering columns to determine uniqueness or
you will indeed have more rows than you might expect.
Sean Durity
From: Ahmed Eljami
Sent: Wednesday, May 15, 2019 10:56 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Two separate rows for
Hi guys,
We have a strange problem with the data in cassandra, after inserting twice
the same partition with differents columns, we see that cassandra returns 2
rows on cqlsh rather than one...:
a| b| c| d| f| g| h| i| j| k| l
--++---+-
