[ 
https://issues.apache.org/jira/browse/CASSANDRA-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206487#comment-17206487
 ] 

Josh McKenzie commented on CASSANDRA-15538:
-------------------------------------------

What's our appetite for taking Harry from "it is possible to do this with 
Harry" to "we are in fact doing this with Harry" in the 4.0 time frame? Any 
points of view on blocking the release based on that work being done?

Are there areas of the codebase we feel still have significant risk that we 
should further exercise with things like Harry and Fallout before release (i.e. 
local read/write paths, etc), or are we confident that the combination of no 
LegacyLayout for 4.0 + diff testing will give users a solid 4.0 experience and 
we can wire up the other stuff after?

> 4.0 quality testing: Local Read/Write Path: Other Areas
> -------------------------------------------------------
>
>                 Key: CASSANDRA-15538
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15538
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/dtest/java, Test/dtest/python
>            Reporter: Josh McKenzie
>            Priority: Normal
>             Fix For: 4.0-beta, 4.0-triage
>
>
> Reference [doc from 
> NGCC|https://docs.google.com/document/d/1uhUOp7wpE9ZXNDgxoCZHejHt5SO4Qw1dArZqqsJccyQ/edit#]
>  for context.
> *Shepherd: Aleksey Yeschenko*
> Testing in this area refers to the local read/write path (StorageProxy, 
> ColumnFamilyStore, Memtable, SSTable reading/writing, etc). We are still 
> finding numerous bugs and issues with the 3.0 storage engine rewrite 
> (CASSANDRA-8099). For 4.0 we want to ensure that we thoroughly cover the 
> local read/write path with techniques such as property-based testing, fuzzing 
> ([example|http://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html]),
>  and a source audit.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to