You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "paf31 (via GitHub)" <gi...@apache.org> on 2025/08/25 15:58:47 UTC
[I] TimestampParser does not support full ISO8601 [arrow-rs]
paf31 opened a new issue, #8219:
URL: https://github.com/apache/arrow-rs/issues/8219
**Describe the bug**
<!--
A clear and concise description of what the bug is.
-->
The documentation claims to support "RFC3339 / ISO8601 standard timestamps", but it will not accept strings with missing time components, for example `hh::mm` format (missing seconds).
Can the documentation be clarified, or the full format list supported?
**To Reproduce**
<!--
Steps to reproduce the behavior:
-->
In `datafusion-cli`:
```
> SELECT to_timestamp_micros('2025-08-14T00:00Z') as timestamp_col;
Arrow error: Parser error: Error parsing timestamp from '2000-01-01T00:00Z': error parsing time
```
**Expected behavior**
<!--
A clear and concise description of what you expected to happen.
-->
**Additional context**
<!--
Add any other context about the problem here.
-->
--
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: github-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] TimestampParser does not support full ISO8601 [arrow-rs]
Posted by "alamb (via GitHub)" <gi...@apache.org>.
alamb commented on issue #8219:
URL: https://github.com/apache/arrow-rs/issues/8219#issuecomment-3270967024
> I think we can support this format without a `second`, as it is valid in ISO8601(see [example](https://www.ionos.com/digitalguide/websites/web-development/iso-8601/) here, and [Wikipedia](https://en.wikipedia.org/wiki/ISO_8601)), I can help to fix this if this is valid, what do you think about this [@alamb](https://github.com/alamb) ?
Thanks for the ping @klion26 and the report @paf31
I agree that fixing TimestampParser to properly parse something that is a valid ISO8601 timestamp is a good idea, provided we can do so without hurting performance
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] TimestampParser does not support full ISO8601 [arrow-rs]
Posted by "klion26 (via GitHub)" <gi...@apache.org>.
klion26 commented on issue #8219:
URL: https://github.com/apache/arrow-rs/issues/8219#issuecomment-3265814247
Currently, we use [`TimestampParser`](https://github.com/apache/arrow-rs/blob/0c7cb2ac3f3132216a08fd557f9b1edc7f90060f/arrow-cast/src/parse.rs#L93) which always requires the `second` to exist. This will throw an error for the given input, "2000-01-01T00:00Z".
I think we can support this format without a `second`, as it is valid in ISO8601(see [example](https://www.ionos.com/digitalguide/websites/web-development/iso-8601/) here, and [Wikipedia](https://en.wikipedia.org/wiki/ISO_8601)), I can help to fix this if this is valid, what do you think about this @alamb ?
I've tried that, the `parse_from_str` from Chorono does not support this format either, but it supports a more generic function `parse`, which takes a parameter with the `StrftimeItems`(e.g., `%Y-%m-%dT%H:%MZ").
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org