HuaHuaY commented on PR #51325: URL: https://github.com/apache/arrow/pull/51325#issuecomment-5770525578
> So it seems that the behavior differs between nested and non-nested types, despite the comment suggesting that NaN values should not be merged for nested types. Is this the expected behavior? The code at `cpp/src/arrow/compute/kernels/vector_run_end_encode.cc:597`, which I mentioned earlier, determines the behavior for non-nested types. I am not familiar with Arrow Compute. But I don't think there are any correctness issues with either behavior; both allow the original data to be recovered, with the difference being encoding efficiency. If we want to merge NaNs with identical physical representations, perhaps we could open a separate PR to do that for nested types. -- 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]
