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
https://issues.apache.org/jira/browse/CASSANDRA-14008
If this was written in 2.1/2.2 and you upgraded to 3.0.x (x < 16) or
3.1-3.11.1, could be this issue.
--
Jeff Jirsa
> On May 15, 2019, at 8:43 AM, Ahmed Eljami wrote:
>
> What about this part of the dump:
>
> "type" : "row",
>
What about this part of the dump:
"type" : "row",
"position" : 4123,
"clustering" : [ "", "Token", "abcd", "" ],
"cells" : [
{ "name" : "dvalue", "value" : "", "tstamp" :
"2019-04-26T17:20:39.910Z", "ttl" : 31708792, "expires_at" :
"2020-04-27T17:20:31Z", "exp
Hi Sean,
Thanks for reply,
I'm agree with you about uniquness but when the output of sstabledump show
that we have the same value for the column g => "clustering" : [ "",
"Token", "abcd", "" ],
and when we select with the whole primary key with the valuers wich I see
in the sstable, cqlsh retu
Uniqueness 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 different rows in the same partit
