Hello Farhon,
I think your idea about KStream-KTable join is a good approach with some
tweaks, more specifically:
1. Model your rider request as a normal record stream with the combo key of
(latitude, longitude).
2. Model your driver location as an ever-updating table with the combo key
of (lati
Quick reply only, since I am on my mobile. Not an exact answer to your
problem but still somewhat related:
http://www.infolace.com/blog/2016/07/14/simple-spatial-windowing-with-kafka-streams/
(perhaps you have seen this already).
-Michael
On Sun, Aug 28, 2016 at 4:55 AM, Farhon Zaharia
wrote:
