Timur, As Michael said one thing you can consider is the regex subscription if those topics have some common prefix / suffix / pattern.
Another idea I can think of is to have two Streams app, one for reading the input topics and pipe them into the repartitioned intermediate topics that can be controlled by the streams app itself, and the second app reading from the intermediate topics and process the rest of the topology. When input topics change, you can simple bounce the first app only, which is a very thin client and hence should take much less time to restart. Guozhang On Wed, Nov 9, 2016 at 12:30 PM, Michael Noll <[email protected]> wrote: > I am not aware of any short-term plans to support that, but perhaps others > in the community / mailing list are. > > On Wed, Nov 9, 2016 at 11:15 AM, Timur Yusupov <[email protected]> > wrote: > > > Are there any nearest plans to support that? > > > > On Wed, Nov 9, 2016 at 1:11 PM, Michael Noll <[email protected]> > wrote: > > > > > This is not possible at the moment. However, depending on your use > case, > > > you might be able to leverage regex topic subscriptions (think: "b*" to > > > read from all topics starting with letter `b`). > > > > > > On Wed, Nov 9, 2016 at 10:56 AM, Timur Yusupov <[email protected]> > > > wrote: > > > > > > > Hello, > > > > > > > > In our system it is possible to add/remove topics in runtime and we > are > > > > trying to use KafkaStreams for incoming messages processing. > > > > > > > > It is possible to resubscribe KafkaStreams instance to updated set of > > > > topics? > > > > > > > > For now I see the only way is to shutdown exiting KafkaStreams > instance > > > and > > > > start a new one, but sometimes that takes up to 30-40 seconds... > > > > > > > > Thanks, Timur. > > > > > > > > > > -- -- Guozhang
