You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2024/01/22 12:25:00 UTC

[jira] [Created] (CASSANDRA-19282) Investigate different way how to verify CQLSSTableWriterTest data after loading

Stefan Miklosovic created CASSANDRA-19282:
---------------------------------------------

             Summary: Investigate different way how to verify CQLSSTableWriterTest data after loading
                 Key: CASSANDRA-19282
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19282
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Stefan Miklosovic
            Assignee: Doug Rohrer


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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org