gt; > > comes
> > > > > to expectations, is don¹t go with a cluster. Just have a
> > > script/watcher
> > > > > app that does the polling and then, when it detects new topics, for
> > > each
> > > > > new topic: start a new i
cript/watcher
> > > > app that does the polling and then, when it detects new topics, for
> > each
> > > > new topic: start a new instance of your app on a new box that listens
> > to
> > > > that single topic. It might take a few seconds to
box that listens
> to
> > > that single topic. It might take a few seconds to startup, but its
> easy
> > > to code, easy to maintain, and easy to understand. Which makes for a
> > more
> > > resilient application.
> > > -Erik
> > >
> &
Hello,
Is there a simple way to set up a consumer that automatically picks up all the
topics for all the partitions, dynamically extending its range as new topics
get created?
The underlying idea is that we want to have a few over-arching consumers (I'm
aware that's not great for the
rg>
Subject: automatically consume from all topics
Hello,
Is there a simple way to set up a consumer that automatically picks up all
the topics for all the partitions, dynamically extending its range as new
topics get created?
The underlying idea is that we want to have a few over-arching
s <j.peet...@wintoncapital.com>
> Reply-To: "users@kafka.apache.org" <users@kafka.apache.org>
> Date: Thursday, September 10, 2015 at 6:09 AM
> To: "users@kafka.apache.org" <users@kafka.apache.org>
> Subject: automatically consume from all topi
rom: Joris Peeters <j.peet...@wintoncapital.com>
> > Reply-To: "users@kafka.apache.org" <users@kafka.apache.org>
> > Date: Thursday, September 10, 2015 at 6:09 AM
> > To: "users@kafka.apache.org" <users@kafka.apache.org>
> > Subject:
