parthchandra commented on PR #6449: URL: https://github.com/apache/datafusion-comet/pull/6449#issuecomment-5919290392
The diff is a clean, byte-identical `-x` cherry-pick of `aee5e06133c` with green CI - no code concerns. One process question: Can we get an explicit decision on whether branch-1.0 should take #6339? The underlying #6288 corruption (a sliced nested boolean read from bit 0) predates 1.0.0, and a comment notes this pick also covers #6464 (native explode slicing its output). So if the explode or aggregate slicing paths are reachable on 1.0, the bad data is reachable there too. A yes/no on the 1.0 backport, or a tracking issue, would close the loop per the "a fix on one release branch goes to every newer one" policy. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
