[
https://issues.apache.org/jira/browse/CASSANDRA-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094160#comment-17094160
]
David Capwell commented on CASSANDRA-15733:
-------------------------------------------
updated all branches to include CASSANDRA-15756
[trunk|https://app.circleci.com/pipelines/github/dcapwell/cassandra/223/workflows/de8e2ce0-6326-4dc8-8aab-667572896814]
[3.11|https://app.circleci.com/pipelines/github/dcapwell/cassandra/224/workflows/be3760bd-5f8b-42cc-adb4-e835d402bd69]
[3.0|https://app.circleci.com/pipelines/github/dcapwell/cassandra/225/workflows/fae15e4a-dc73-4a52-bbe5-106d4f726d54]
[2.2|https://app.circleci.com/pipelines/github/dcapwell/cassandra/226/workflows/be1d3ea6-12dc-4908-8b5b-3147775cd277]
> jvm dtest builder should be provided to the factory and expose state
> --------------------------------------------------------------------
>
> Key: CASSANDRA-15733
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15733
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> 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
--
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
