You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "John Roesler (JIRA)" <ji...@apache.org> on 2019/02/11 23:01:00 UTC

[jira] [Updated] (KAFKA-7919) Reorganize Stores builders

     [ https://issues.apache.org/jira/browse/KAFKA-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Roesler updated KAFKA-7919:
--------------------------------
    Labels: needs-discussion needs-kip  (was: needs-kip)

> Reorganize Stores builders
> --------------------------
>
>                 Key: KAFKA-7919
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7919
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: John Roesler
>            Priority: Major
>              Labels: needs-discussion, needs-kip
>
> I have heard complaints from a few people that they find the whole process of using `Materialized`, `Stores`, `StoreBuilder`s, and `StoreSupplier`s confusing.
> I think it would help if we separated Stores into separate StoreBuilders and BytesStoreSuppliers factory classes. Or maybe even break the suppliers factory down further into `KeyValueBytesStoreSuppliers`, etc. Then, the javadocs in `Materialized.as` can point people to the right factory class to use, and, when they get there, they'll only be confronted with options they can make use of.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)