jorisvandenbossche commented on issue #33769: URL: https://github.com/apache/arrow/issues/33769#issuecomment-1397094509
I think also for that reason (quantile by default always returns floats), we might not want to add support for quantile to temporal types (not sure if we actually ever considered this). There are interpolation methods (lowest, highest, nearest) that do preserve the input type, though. So maybe we could only allow those? But on your point of not matching pandas behaviour if you do the casting manually. I am not sure having this kernel in pyarrow would make any difference for that, since arrow would basically do the same under the hood and calculate the interpolated value based on the underlying integers. -- 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]
