Hi Guozhang, So, in this case I should know the max number of possible keys so that I can create that number of partitions.
Thanks Adrienne On Wed, Oct 5, 2016 at 1:00 AM, Guozhang Wang <wangg...@gmail.com> wrote: > By default the partitioner will use murmur hash on the key and mode on > current num.partitions to determine which partitions to go to, so records > with the same key will be assigned to the same partition. Would that be OK > for your case? > > > Guozhang > > > On Tue, Oct 4, 2016 at 3:00 PM, Adrienne Kole <adrienneko...@gmail.com> > wrote: > > > Hi, > > > > From Streams documentation, I can see that each Streams instance is > > processing data independently (from other instances), reads from topic > > partition(s) and writes to specified topic. > > > > > > So here, the partitions of topic should be determined beforehand and > should > > remain static. > > In my usecase I want to create partitioned/keyed (time) windows and > > aggregate them. > > I can partition the incoming data to specified topic's partitions and > each > > Stream instance can do windowed aggregations. > > > > However, if I don't know the number of possible keys (to partition), then > > what should I do? > > > > Thanks > > Adrienne > > > > > > -- > -- Guozhang >
