jorisvandenbossche commented on PR #12902: URL: https://github.com/apache/arrow/pull/12902#issuecomment-1102788129
We already have `min`/`max` and `min_raw`/`max_raw`, so I would like to avoid adding a third one to overcome this backwards compatibility issue ... It's certainly also an option to see this as a "bug fix" (we shouldn't have used integers for the date type before) and ask kartothek to update their code. It's also for the lesser used date type (not for timestamp), and quite likely the behaviour here now also might have changes for other less used types that were not explicitly handled before (eg I don't how "interval" type would be handled?) -- 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]
