[
https://issues.apache.org/jira/browse/KAFKA-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889138#comment-16889138
]
Alexander Zafirov commented on KAFKA-8666:
------------------------------------------
Looking at the JavaDoc I think that it is elaborate enough
{code:java}
// Materialize a {@link StateStore} with the provided key and value {@link
Serde}s.
* An internal name will be used for the store.
{code}
Let's hope that people are using modern IDEs that discourage calling the static
methods on `Materialized` objects.
>From my standpoint I think this issue should be closed. Hope our discussion is
>useful for the people out there.
Thank you, Matthias.
> 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)
