junaiddshaukat opened a new issue, #39382:
URL: https://github.com/apache/beam/issues/39382

   Currently every Impulse transform gets its own bootstrap topic
   (`__beam_impulse_<applicationId>_<transformId>`), because Kafka Streams 
rejects
   registering one topic on two source nodes and a pipeline can contain several
   Impulses (e.g. an empty `Create` plus the dummy branch `PAssert` adds).
   
   Per review of #39380 this can be optimized: keep a single per-application
   bootstrap topic with one source node, and fan the created element out to all
   Impulse processors from there, instead of one topic per transform.
   
   Part of #18479.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to