parthpathak1201 commented on issue #50548: URL: https://github.com/apache/arrow/issues/50548#issuecomment-5021128442
for RLE batches, every level is the same value, so checking first & last is the same as checking all of them. for bit-packed, even the full scan can't really guarantee catching corruption... a corrupted value could still land in the valid range. and we already have page CRC for actual corruption detection. so the O(n) scan was just burning cpu without adding much real safety just seemed like an easy perf win without losing anything meaningful I can understand why 'pointless' could maybe sound strong here, I was going for something like ~overkill? -- 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]
