Hello Raman, It seems from your case that `topic-1` is used for both the global ktable as well as another stream, which then be transformed to a new stream that will be "joined" somehow with the global ktable. Could you elaborate your case a bit more on why do you want to use the same source topic for two entities in your topology?
Guozhang On Tue, Apr 2, 2019 at 3:41 PM Raman Gupta <rocketra...@gmail.com> wrote: > I have a topology like this: > > +-----------> global-ktable +---------+ > | | > + v > topic-1 stream > + ^ > | | > +----> other stream +--> topic-2 +----+ > > IOW, a global ktable is built from topic-1. Meanwhile, "other stream" > transforms topic-1 to topic-2. Finally, "stream" operators on topic-2, > and as part of its logic, reads data from "global-ktable". > > I am worried about the race condition present in "stream" between the > message showing up on topic-2, and the "get" from "global-ktable". Is > there a way, other than retrying the `get`, to avoid this race? > > Regards, > Raman > -- -- Guozhang
