[CASSANDRA-15733] jvm dtest builder should be provided to the factory and expose state

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.17, 3.0.21, 3.11.7, 4.0-beta1, 4.0
• Component/s: Test/dtest/java
• Labels: pull-request-available
• Change Category: Quality Assurance
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/4fef917f985ea13ea46f68aae00645cb3592ffcf

Test and Documentation Plan

manual verification

• Assignee: David Capwell
• Reporter: David Capwell

Authors

David Capwell

Reviewers

Alex Petrov

• Created: 15/Apr/20 20:28
• Updated: 16/Mar/22 13:24
• Resolved: 05/Jun/20 17:37

Description

Currently the builder is rather heavy and creates configs plus call the factory with specific fields only, this isn’t that flexible and makes it harder to have custom cluster definitions which require additional fields to be defined. To solve this we should make the builder be sent to the factory and expose the state so the factory can get all the fields it needs, the factory should also be in charge of creating the configs

Issue Links

• blocks: CASSANDRA-15851 Add bytebuddy support for in-jvm dtests
• relates to: CASSANDRA-15456 Backport CASSANDRA-15332 dtest changes to 3.x
• links to: GitHub Pull Request #9
• links to: GitHub Pull Request #539
• links to: GitHub Pull Request #552
• links to: GitHub Pull Request #553
• links to: GitHub Pull Request #554