Is this implemented ? https://cwiki.apache.org/confluence/display/KAFKA/Consumer+API+changes ?
This is message filtering on the client or server side ? On Tue, Aug 4, 2015 at 9:54 PM, Gwen Shapira <g...@confluent.io> wrote: > The way Kafka is currently implemented is that Kafka is not aware of the > content of messages, so there is no Selector logic available. > > The way to go is to implement the Selector in your client - i.e. your > consume() loop will get all messages but will throw away those that don't > fit your pattern. > > > It may be worthwhile to add a ticket for pluggable selector logic in the > new consumer. I can't guarantee it will happen, there are infinite things > that can be plugged into consumers and we need to draw the line somewhere, > but worth a discussion. > > On Tue, Aug 4, 2015 at 2:05 PM, Alvaro Gareppe <agare...@gmail.com> wrote: > > > The is way to implement a "selector" logic in kafka (similar to JMS > > selectors) > > > > So, allow to consume a message if only the message contains certain > header > > or content ? > > > > I'm evaluating to migrate from ActiveMQ to kafka and I'm using the > selector > > logic widely in the application > > > > -- > > Ing. Alvaro Gareppe > > agare...@gmail.com > > > -- Ing. Alvaro Gareppe agare...@gmail.com
