apoorvmittal10 commented on PR #20246: URL: https://github.com/apache/kafka/pull/20246#issuecomment-3160029498
@JimmyWang6 I think we should support both i.e. current and strict functionality. That means if the acquire method is called with acquire mode as `strict` then we should only acquire till `maxFetchRecords` else can go upto batch boundaries for optimization. This will give SharePartition flexibility to support both. From clients, we need to have another param in ShareFetchRequest which governs if the max records are strict. The client changes can be done later as it will require a small KIP, cc: @ShivsundarR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
