wwj6591812 commented on PR #8116: URL: https://github.com/apache/paimon/pull/8116#issuecomment-4829963475
> I don't quite understand why it's so complicated, just judge for low level Read whether it's possible to perform limit pruning inside, is that enough? Thanks for the review. @JingsongLi After re-reading the code, I agree — merge-read limit safety can be decided entirely in MergeFileSplitRead, without orchestration in the upper layer. Changes: 1、MergeFileSplitRead: uses effectiveReadLimit() / mergeReadLimitDisabledReason() to decide whether limit pruning is safe during merge read. 2、KeyValueTableRead: only passes limit to split reads and wraps multi-split reads with LimitRecordReader for correct SQL semantics. 3、Query-auth splits are the only exception: filters run after split read, so merge-read limit is skipped there. Removed withApplyMergeReadLimit / isMergeReadLimitActive and related tests; functional UT coverage is unchanged. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
