You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "João Pedro Fonseca (Jira)" <ji...@apache.org> on 2024/09/12 16:48:00 UTC
[jira] [Commented] (KAFKA-8666) Improve Documentation on usage of Materialized config object
[ https://issues.apache.org/jira/browse/KAFKA-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881368#comment-17881368 ]
João Pedro Fonseca commented on KAFKA-8666:
-------------------------------------------
Hi, [~mjsax]! Could I close this one?
> 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
> Assignee: João Pedro Fonseca
> Priority: Major
> Labels: newbie
> Fix For: 4.0.0
>
>
> 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
(v8.20.10#820010)