[CASSANDRA-19282] Investigate a different way how to verify CQLSSTableWriterTest data after loading

• Type: Improvement
• Status: Triage Needed
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 5.0.x, 5.x
• Platform: All
• Assignee: Doug Rohrer
• Reporter: Stefan Miklosovic

Authors

Doug Rohrer

• Created: 22/Jan/24 12:24
• Updated: 02/Mar/24 08:46

Description

In CASSANDRA-18714, we realized that client tests (CQLSSTableWriterClientTest) are not executing the same set of tests as CQLSSTableWriterTest does. This unfortunate discrepancy was addressed in CASSANDRA-18714 were both client and daemon tests extend abstract test class where all tests are hence client and daemon run same tests, just from different angle.

This clear improvement in the consolidation of tests is not 100% pure in trunk. Due to nature of the implementation in trunk, the only thing which is skipped in trunk is verification of data after generated SSTables are loaded in case of client tests. This was not done before CASSANDRA-18714 either (because client tests were not testing what daemon ones would in the first place).

This ticket is for the investigation how to unify tests for both modes in trunk, we might probably load SSTables on the disk by means of SSTableScanner, for example.

Issue Links

• is related to: CASSANDRA-18714 Expand CQLSSTableWriter to write SSTable-attached secondary indexes