Technical Debt
Trivial - P5 Summary
The cpp suite uses configuration files to define a workload. The different items that can be used are defined in test_data.py. The read operation configuration seems to be made of the record configuration which indicates the size of the keys and values. For such an operation it does not make sense, we don't need to indicate the size of the keys or values when we perform a read.
Motivation
- Is this issue urgent?
No
Acceptance Criteria (Definition of Done)
Remove the record configuration that is part of the read configuration and make sure there is no test using it.
Suggested Solution
diff --git a/dist/test_data.py b/dist/test_data.py
index 8ec4b5814..706863cca 100644
--- a/dist/test_data.py
+++ b/dist/test_data.py
@@ -126,7 +126,7 @@ checkpoint_operation_thread_config = [
The rate at which checkpoint is executed.''')
]
custom_operation_thread_config = thread_count + transaction_config + throttle_config + record_config
-read_thread_config = thread_count + throttle_config + transaction_config + record_config
+read_thread_config = thread_count + throttle_config + transaction_config
remove_thread_config = thread_count + transaction_config + throttle_config
update_insert_thread_config = thread_count + transaction_config + throttle_config + record_config