You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "highluck (Jira)" <ji...@apache.org> on 2020/07/06 13:36:00 UTC
[jira] [Assigned] (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:all-tabpanel ]
highluck reassigned KAFKA-8666:
-------------------------------
Assignee: highluck
> 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: highluck
> 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
(v8.3.4#803005)