Or is the motivation that resolving the committed/latest offsets is an
infrequent event (and only for bounded read) so the optimization is not
worth it?
On Wed, Mar 2, 2022 at 2:16 PM Mason Chen wrote:
> Hi all,
>
> I noticed in the javadocs that SplitReaders should not have a blocking
> handleS
Hi all,
I noticed in the javadocs that SplitReaders should not have a blocking
handleSplitsChanges implementation:
https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-base/src/main/java/org/apache/flink/connector/base/source/reader/splitreader/SplitReader.java#L55
However
