[
https://issues.apache.org/jira/browse/ARROW-10848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624328#comment-17624328
]
Tim Loderhose commented on ARROW-10848:
---------------------------------------
I understand that the original issue isn't about this, however, I thought that
these comments in specific:
{quote}
Neal Richardson added a comment - 28/Jul/21 16:06
Is custom timestamp parsing enough--will that give me a date32 type if that's
what I declare in the types/schema?
Antoine Pitrou added a comment - 28/Jul/21 16:08
Custom timestamp parsers are only for timestamps columns.
Again, the question is whether these formats are common in the real world. My
intuition is "no", but I don't have any data.
{quote}
were discussing the potential use of applying the iso8601 parser also to date
(not timestamp) types.
This issue is fitting: https://issues.apache.org/jira/browse/ARROW-10847, but
didn't receive any attention.
> [C++] CSV ISO-8601 date and timestamp short form
> ------------------------------------------------
>
> Key: ARROW-10848
> URL: https://issues.apache.org/jira/browse/ARROW-10848
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Maciej
> Priority: Major
> Labels: csv
>
> Arrow supp{color:#172b4d}orts ISO-8601 for date and timestamp parsing but
> doesn't support short form of them. E.g.{color}
> {code:java}
> 19990108
> or
> 19990108 040506
> {code}
> Examples taken from:
> [https://www.postgresql.org/docs/12/datatype-datetime.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
