Current state: "Under Discussion"
Discussion thread: https://email@example.com/msg124881.html
To have more flexibility, builders should be provided for the following objects
These builders will give an easy way to construct these objects using different arguments/combinations without having to add a new constructor every time a new parameter is required.
They will also allow using already configured dependencies coming from an injection framework such as Spring (see https://github.com/spring-projects/spring-kafka/issues/2244).
From a user point of view, builders would be used as follow
To ease the integration with existing clients, a static builder may be added on related clients.
This KIP can be seen as the continuity of the KIP-832.
Four new builders will be added
- The builder will always
- override → single value
- complete the configuration parameters → list values
- Any closeable objects provided to a builder will still be closed once the client is closed, and as a result, a builder should only be used once. An exception will be thrown if build() is invoked multiple times.
- Any configurable object provided to a builder will be configured by the client after instantiation.
To finalize KIP-378, two new constructors will be added in the TopologyTestDriver as follow
Compatibility, Deprecation, and Migration Plan
No compatibility issue and no migration plan are required as this KIP will create new builders to give more flexibility.
Kafka users will simply have more ways to build producers, consumers and a topology test driver without any impacts on the existing.
The KIP-832 was the original proposal but won't be implemented in benefit of the current KIP.