Hi Colin, thank you for this KIP, it can become a really useful thing.
I just scanned through the discussion so far and wanted to start a
thread to make as decision about keeping the
cache with the Connection / Session or having some sort of UUID indexed
global Map.
Sorry if that has been settled already and I missed it. In this case
could anyone point me to the discussion?
Id rather see a protocol in which the client is hinting the broker that,
he is going to use the feature instead of a client
realizing that the broker just offered the feature (regardless of
protocol version which should only indicate that the feature
would be usable). This seems to work better with a per
connection/session attached Metadata than with a Map and could allow for
easier client implementations.
It would also make Client-side code easier as there wouldn't be any
Cache-miss error Messages to handle.
Thank you again for the KIP. And again, if this was clarified already
please drop me a hint where I could read about it.
Best Jan
On 21.11.2017 22:02, Colin McCabe wrote:
Hi all,
I created a KIP to improve the scalability and latency of FetchRequest:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-227%3A+Introduce+Incremental+FetchRequests+to+Increase+Partition+Scalability
Please take a look.
cheers,
Colin
