JingsongLi commented on PR #8272: URL: https://github.com/apache/paimon/pull/8272#issuecomment-4747279335
Thanks for the fix. I think one edge case still bypasses the new keyed count-limit logic: returns directly when , before the keyed path runs. If the first non-null value for a row already contains more than distinct nested keys, or contains duplicate nested keys where should choose the latest row, that first array is kept as-is. On later merges, treats all of those keys as existing, so the count limit never brings it back under the intended distinct-key cap. Could we route the keyed case through the same map/limit/sequence merge path, and add a test with a multi-row first input array? -- 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]
