CACHE_MAX_BYTES_BUFFERING_CONFIG does not have any impact if you query the state. If you query it, you will always get the latest values. CACHE_MAX_BYTES_BUFFERING_CONFIG only effects the downstream KTable changelog stream (but you do not use this anyway).
If I understand you correctly, if you remove the map() you get three count results <"A-1":1>, <"A-2":1>, and <"B-1":1> Are you sure, that you map is correct? I am not familiar with Scala, but the key and value must both not be null to be included in the count. Could it be that `k.split("-")(0)` returns a null key? -Matthias On 11/23/16 7:00 AM, Hamidreza Afzali wrote: > Thanks Matthias. > > Disabling the cache didn't solve the issue. Here's a sample code: > > https://gist.github.com/hrafzali/c2f50e7b957030dab13693eec1e49c13 > > The topology doesn't produce any result but it works when commenting out > .map(...) in line 21. > > Thanks, > Hamid >
signature.asc
Description: OpenPGP digital signature