[
https://issues.apache.org/jira/browse/KAFKA-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745164#comment-16745164
]
Tommy Becker commented on KAFKA-7075:
-------------------------------------
[~lmontrieux] I'm curious what your use-case is. After experimenting with
addGlobalStore(), I'm not sure what value it has. At first glance it seems to
allow you to plug in a custom processor that allows you to maintain your global
store however you wish. But the initial population of the store does not go
through this processor, so if you want to do anything beyond loading the exact
contents of the topic, you're out of luck. This method actually seems dangerous
because if your custom processor does not use the keys from the topic verbatim,
you'll get all manner of weird behavior.
> Allow Topology#addGlobalStore to add a window store
> ---------------------------------------------------
>
> Key: KAFKA-7075
> URL: https://issues.apache.org/jira/browse/KAFKA-7075
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Nishanth Pradeep
> Priority: Major
> Labels: newbie
>
> Today although {{Topology#addGlobalStore}} can take any {{StateStore}} types,
> the internal implementation {{InternalTopologyBuilder#addGlobalStore}} only
> accepts {{StoreBuilder<KeyValueStore>}}. It means if users pass in a windowed
> store builder in {{Topology#addGlobalStore}} it will cause a runtime
> ClassCastException.
> We should fix this issue by relaxing the {{InternalTopologyBuilder}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
