[CASSANDRA-15962] Digest for some queries is different depending whether the data are retrieved from sstable or memtable

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.11.10, 4.0-rc1, 4.0
• Component/s: Consistency/Coordination
• Bug Category: Correctness - Consistency
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: 3.11.0

Source Control Link

https://github.com/apache/cassandra/commit/a9ab7bde4e35856f407458c341883c4cde7484cd

Test and Documentation Plan

The unit test is in the PR

• Assignee: Jacek Lewandowski
• Reporter: Jacek Lewandowski

Authors

Francisco Fernandez, Jacek Lewandowski

Reviewers

Benjamin Lerer, Sylvain Lebresne

• Created: 20/Jul/20 13:19
• Updated: 19/Nov/21 06:53
• Resolved: 25/Jan/21 10:50

Description

Not sure into which category should I assign this ticket.

 

Basically when reading using certain column filters, the digest is different depending whether we read from sstable and memtable. This happens on trunk and cassandra-3.11 branches. However it works properly on cassandra-3.0 branch.

 

I'm attaching a simple test for trunk to demonstrate what I mean. 

 

Please verify my test and my conclusions

 

Issue Links

• is duplicated by: CASSANDRA-15640 digest may not match when single partition named queries skip older sstables
• is related to: CASSANDRA-16223 Reading dense table yields invalid results in case of row scan queries