pitrou commented on issue #50509: URL: https://github.com/apache/arrow/issues/50509#issuecomment-5664240103
> this can be problematic for RunEndEncodedBuilder with floating-point values, as it can produce a zero value, which cannot be considered an empty value (Case 1). This is the same behavior as other numeric types, so I don't understand the problem. > Even worse, it can be mistakenly confused with actual floating-point values (see the example below). That would be a bug in `RunEndEncodedBuilder::AppendEmptyValues` then? Let's make sure that "empty" values don't get compressed with a run of non-empty values. -- 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]
