[
https://issues.apache.org/jira/browse/KAFKA-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18111755#comment-18111755
]
Matthias J. Sax commented on KAFKA-6646:
----------------------------------------
Overall, I would believe this could still be a useful addition. On the other
hand, this ticket is very old, so it seems there was not much demand from KS
users for such a feature – otherwise, there would have been more activity on
the ticket.
It's not trivial to do and we would need to very carefully design it, and I am
not even sure if adding it to the global thread would be the right thing to do.
Ideally, we would have a few concrete use-cases at hand, to better understand
how KS users would want to use such a feature, to ensure if build it correctly.
> Add a GlobalKStream object type for stream event broadcast
> ----------------------------------------------------------
>
> Key: KAFKA-6646
> URL: https://issues.apache.org/jira/browse/KAFKA-6646
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Affects Versions: 1.1.0
> Reporter: Antony Stubbs
> Assignee: Hrishi Baskaran
> Priority: Major
> Labels: api, needs-kip
>
> There are some use cases where having a global KStream object is useful. For
> example, where a single event is sent, with very low frequency, to a cluster
> of Kafka stream nodes to trigger all nodes to do some processing of state
> stored on their instance.
> Workaround currently is to either create a second kstream app instance, being
> careful to configure it with a different state dir, and give it a unique app
> name per instance, then create a kstream in each one. Or - you can use the
> normal consumer client inside your kstream app with unique consumer groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
