[
https://issues.apache.org/jira/browse/CASSANDRA-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784075#comment-17784075
]
Alex Petrov edited comment on CASSANDRA-18993 at 11/8/23 2:35 PM:
------------------------------------------------------------------
[~e.dimitrova] it depends. If Jacek commits the test I submitted on 18932, I am
ok to close this one, but if the test is not committed there, I will get it
committed here.
was (Author: ifesdjeen):
It depends. If Jacek commits the test I submitted there, I am ok to close this
one, but if the test is not committed there, I will get it committed here.
> Harry-found silent data loss issue
> ----------------------------------
>
> Key: CASSANDRA-18993
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18993
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Reporter: Alex Petrov
> Assignee: Jacek Lewandowski
> Priority: Normal
> Fix For: 4.1.x, 5.0-beta, 5.x
>
>
> Harry has discovered a silent data loss bug in trunk, but it goes all the way
> back to appx 4.1.
> Some rows are not visble after flush. Compared Harry repro running a memtable
> instead of a regular Harry model, and it still reproduces (in other words, it
> is almost certainly not a Harry issue).
> Simple schema, and only one flush is required for repro, so not an unlikely
> bug. Max partition size is 1k rows, so not an unlikely setup here, either. No
> concurrency involved; reproduces stably. Good chance this is related to the
> fact the schema has DESC clusterings.
> I am working on posting a Harry branch that stably reproduces it.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
