Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REGRESSION] Parsing timestamps with fractional seconds / microseconds / milliseconds / nanoseconds #3859

Closed
alamb opened this issue Mar 14, 2023 · 1 comment · Fixed by #3858
Assignees
Labels
arrow Changes to the arrow crate bug

Comments

@alamb
Copy link
Contributor

alamb commented Mar 14, 2023

Describe the bug
#3801 introduced a regression. Prior to arrow 34 the following timestamp could be parsed:

1969-01-01T00:00:00.1' 

However, after the upgrade it will generate a parse error. This can be worked around by padding the precision to be a whole number of seconds, microseconds, milliseconds, or nanoseconds. For example

1969-01-01T00:00:00.100' 

To Reproduce

Try to parse this as a timestamp:

1969-01-01T00:00:00.1' 

Expected behavior
It should be parsed correctly

Additional context
Found during DataFusion upgrade: apache/datafusion#5441

@tustvold
Copy link
Contributor

label_issue.py automatically added labels {'arrow'} from #3860

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arrow Changes to the arrow crate bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants