Hi @ajinkyasagar,
I’m confused by what you mean with the statement below. The filters applied by the @StreamListener previously also only applied to events after they were received from the broker. At that point they are within your app running on a single JVM. Maybe I’m just confused. Can you share an example of what worked with @StreamListener that doesn’t work now?
Regarding routing function i can not achive horizontal scalability as function and router function needs to be in same webservice which will run on single JVM
Instead of streamlistener is there any way i can add properties in yaml file where i can mention condition on header
If you’re using the routing function (pending issue above) you can specify those via the properties/yaml file using somethign likespring.cloud.function.routing-expression=headers['type']