You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nate McCall (JIRA)" <ji...@apache.org> on 2019/07/24 23:48:00 UTC
[jira] [Updated] (CASSANDRA-15244) After Delete the data for
particular partition , even still selecting that row. nodes all are in
sync. we did full repair as well.
[ https://issues.apache.org/jira/browse/CASSANDRA-15244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate McCall updated CASSANDRA-15244:
------------------------------------
Resolution: Not A Problem
Status: Resolved (was: Triage Needed)
Hi [~sateesh.v] I'm not sure I understand the whole message, but from what I am reading Cassandra is functioning as designed.
The users email list will be a good place to ask this question. You can find details on subscribing on this page:
http://cassandra.apache.org/community/
> After Delete the data for particular partition , even still selecting that row. nodes all are in sync. we did full repair as well.
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15244
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming
> Reporter: sateesh Vemulapalli
> Priority: Normal
> Attachments: corrupt.csv
>
>
> CASSANDRA VER: 3.11.4
> jdk 8
> Centos: 7
>
> After Deleting the row for particular partition , even after still selecting that row. nodes all are in sync. we did full repair as well. but row still selecting ..
>
> If i trying to insert same partition , even though another row creating with space. not overwriting row. this is unexpected behavior of Cassandra.
>
> ====> INSERT SAME PARTITION KEY (UNEXPECTED BEHAVIOR:) getting space on as prefix.
>
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-24 02:00:00 | 1999091 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-27 03:00:00 | 1999092 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-27 03:00:00 | 1999091 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-01 01:00:00 | 1999092 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-01 00:00:00 | 1999092 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-27 02:00:00 | 1999091 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-24 00:00:00 | 1999091 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-26 02:00:00 | 1999091 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-26 02:00:00 | 19990901 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-07-22 21:00:00 | 1999092 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-29 03:00:00 | 1999092 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-01 02:00:00 | 1999092 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-01 02:00:00 | 1999090 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-22 01:00:00 | 1999092 | null | null | null | null
> e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-25 02:00:00 | 1999091 | 1558639781444 | -0.663086 | 0.775391 | 0.156738
>
> (15 rows)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org