[
https://issues.apache.org/jira/browse/ARROW-18214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Boettiger updated ARROW-18214:
-----------------------------------
Description:
Arrow needs to represent datetime / timestamp values as character strings, e.g.
when writing to CSV or when generating partitions on timestamp-valued column.
When this occurs, Arrow generates a string such as:
"2022-11-01 21:12:46.771925+0000"
In particular, this uses a space instead of a T between the date and time
components. I believe either is permitted in [RFC
3339|https://www.rfc-editor.org/rfc/rfc3339.html#section-5]
??5.6. NOTE: ISO 8601 defines date and time separated by "T". Applications
using this syntax may choose, for the sake of readability, to specify a
full-date and full-time separated by (say) a space character.??
But as RFC 3339 notes, this is not valid under ISO 8601. It would be
preferable to stick to the stricter ISO 8601 convention.
was:
Arrow needs to represent datetime / timestamp values as character strings, e.g.
when writing to CSV or when generating partitions on timestamp-valued column.
When this occurs, Arrow generates a string such as:
"2022-11-01 21:12:46.771925+0000"
In particular, this uses a space instead of a T between the date and time
components. I believe either is permitted in [RFC
3339|https://www.rfc-editor.org/rfc/rfc3339.html#section-5]
??5.6. NOTE: ISO 8601 defines date and time separated by "T". Applications
using this syntax may choose, for the sake of readability, to specify a
full-date and full-time separated by (say) a space character.??
But as RFC 3339 notes, this is not valid under ISO 8601. It would be
preferable to stick to the stricter ISO 8601 convention. This would be more
consistent with other software.
> [R] Use ISO 8601 in character representations of datetimes?
> -----------------------------------------------------------
>
> Key: ARROW-18214
> URL: https://issues.apache.org/jira/browse/ARROW-18214
> Project: Apache Arrow
> Issue Type: Bug
> Reporter: Carl Boettiger
> Priority: Major
>
> Arrow needs to represent datetime / timestamp values as character strings,
> e.g. when writing to CSV or when generating partitions on timestamp-valued
> column. When this occurs, Arrow generates a string such as:
> "2022-11-01 21:12:46.771925+0000"
> In particular, this uses a space instead of a T between the date and time
> components. I believe either is permitted in [RFC
> 3339|https://www.rfc-editor.org/rfc/rfc3339.html#section-5]
> ??5.6. NOTE: ISO 8601 defines date and time separated by "T". Applications
> using this syntax may choose, for the sake of readability, to specify a
> full-date and full-time separated by (say) a space character.??
>
> But as RFC 3339 notes, this is not valid under ISO 8601. It would be
> preferable to stick to the stricter ISO 8601 convention.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
