You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Hrishi Baskaran (Jira)" <ji...@apache.org> on 2026/10/18 18:10:00 UTC
[jira] [Assigned] (KAFKA-6646) Add a GlobalKStream object type for stream event broadcast
[ https://issues.apache.org/jira/browse/KAFKA-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hrishi Baskaran reassigned KAFKA-6646:
--------------------------------------
Assignee: (was: Hrishi Baskaran)
> 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
> 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)