Change casting from timestamp to date/time to extract the value, instead of just truncating as we currently do (which rounds, giving incorrect answers, in some cases). This should also be a safe cast by default (unless you want to do something like cast from timestamp[ns] to time32[s] which may overflow).
This should behave like Postgres DATE/CAST(... as TIME), or Pandas Timestamp.date/Timestamp.time.
Reporter: David Li / @lidavidm
Assignee: David Li / @lidavidm
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-13549. Please see the migration documentation for further details.
Change casting from timestamp to date/time to extract the value, instead of just truncating as we currently do (which rounds, giving incorrect answers, in some cases). This should also be a safe cast by default (unless you want to do something like cast from timestamp[ns] to time32[s] which may overflow).
This should behave like Postgres DATE/CAST(... as TIME), or Pandas Timestamp.date/Timestamp.time.
Reporter: David Li / @lidavidm
Assignee: David Li / @lidavidm
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-13549. Please see the migration documentation for further details.