Hi Elliot, This is not currently supported, but I, for one, think it would be awesome. It's something I have considered tackling in the future.
Feel free to create a Jira ticket asking for it (but please take a minute to search for preexisting tickets). Offhand, my #1 concern would be how it works with EOS, but this is probably a surmountable problem. As a workaround if you need this property, you could write a "bridge" application with a consumer connected to A and producer connected to B, and mirror the input topics from A to B, then process fully on B. And the output to C would look similar. Come to think of it, you can probably use Mirror Maker for this. Thanks, -John On Wed, Sep 12, 2018 at 4:38 AM Elliot West <tea...@gmail.com> wrote: > Hello, > > Apologies if this is a naïve question, but I'd like to understand if and > how KStreams and KSQL can deal with topics that reside in more than one > cluster. For example, is it possible for a single KS[treams|QL] application > to: > > 1. Source from a topic on cluster A > 2. Produce/Consume to intermediate topics on cluster B > 3. Sink a final results to cluster C > > Or is it the case that all events read/written by such an application must > exist on the same Kafka cluster? > > Thanks, > > Elliot. >
