Hello all, I have the need to query end offsets for a particular topic using a consumer that has been configured with the "READ_COMMITTED" isolation level. The response I get via the Java client includes offsets at the end of the log that have not yet been committed and therefore can't be consumed.
After digging around in the Java client code, it looks like the isolation level is being transmitted in the API request to the broker. So my question is does the broker use this information when crafting a response and, if it is taken into account, why does it return log end offsets for transactions that have not yet been committed? For my own future reference I was struggling to find any details on the broker API anywhere, if someone could point me in the right direction, I'd really appreciate it. Thanks, Chris Jansen
