wwj6591812 commented on PR #8116: URL: https://github.com/apache/paimon/pull/8116#issuecomment-4933779196
@JingsongLi Thanks for the suggestion. I revisited the execution path and changed the implementation to handle LIMIT directly at the outer KeyValueTableRead boundary. The limit is no longer forwarded to SplitRead or handled in MergeFileSplitRead. KeyValueTableRead now wraps the final reader returned by createReader(Split) and createReader(List<Split>) with LimitRecordReader, after table-level filters and query authorization. The list path also enforces one limit across all concatenated splits. This relies on the existing lazy reader behavior and keeps the PR focused on the TableRead.withLimit contract rather than claiming an additional general SQL runtime optimization. I have also updated the PR title and description accordingly. Please take another look. Thanks. -- 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]
