jorisvandenbossche commented on issue #37411: URL: https://github.com/apache/arrow/issues/37411#issuecomment-1700775715
Hmm, that's unfortunate. It's indeed caused by switching to the standard cast compute kernels, instead of using the custom (and in other ways more limited) Scalar cast implementation. But so clearly that also supported some things not yet supported in the cast kernels. I am not sure if there would be an easy way to fix the regression (apart from reverting), except for adding the "string->date32" cast kernel (although that's something we should do anyway). The "string -> timestamp" kernel lives here: https://github.com/apache/arrow/blob/9b6be29f431705ce1f85cc218c66d4d03698f06b/cpp/src/arrow/compute/kernels/scalar_cast_temporal.cc#L410-L452 It might not be too hard to add a date32 version, essentially using the above but changing `ParseTimestampISO8601` with `ParseYYYY_MM_DD` (which is what is being used for the scalar casting / string parsing for date32), and simplified to not deal with timezones. -- 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]
