[
https://issues.apache.org/jira/browse/KAFKA-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888335#comment-16888335
]
Matthias J. Sax commented on KAFKA-8666:
----------------------------------------
Thanks for your interest.
Adding a new method would require a KIP. And I am personally not convinced that
it is a good idea. The current API design is inspired by the builder pattern
with the goal to reduce/avoid method overloads. Previously, we had many
overloads for many (sometimes all) different parameter combinations and the API
was pretty bad. Hence we changed it to single parameter methods that are
chained together, what make the API much more usable.
Thoughts?
> Improve Documentation on usage of Materialized config object
> ------------------------------------------------------------
>
> Key: KAFKA-8666
> URL: https://issues.apache.org/jira/browse/KAFKA-8666
> Project: Kafka
> Issue Type: Improvement
> Components: documentation, streams
> Reporter: Bill Bejeck
> Priority: Major
> Labels: newbie
>
> When using the Materialized object if the user wants to name the statestore
> with
> {code:java}
> Materialized.as("MyStoreName"){code}
> then subsequently provide the key and value serde the calls to do so must
> take the form of
> {code:java}
> Materialized.as("MyStoreName").withKeySerde(keySerde).withValueSerde(valueSerde)
> {code}
> If users do the following
> {code:java}
> Materialized.as("MyStoreName").with(keySerde, valueSerde)
> {code}
> the Materialized instance created by the "as(storeName)" call is replaced by
> a new Materialized instance resulting from the "with(...)" call and any
> configuration on the first Materialized instance is lost.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
