We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For times before the unix epoch (1970-01-01T00:00:00) times at the boundary are incorrectly put into the previous time bin.
In datafusion-cli:
> SELECT date_bin(INTERVAL '30 second', '1969-12-31T19:00:00') as t; +---------------------+ | t | +---------------------+ | 1969-12-31T18:59:30 | +---------------------+ 1 row(s) fetched. Elapsed 0.002 seconds. > SELECT date_bin(INTERVAL '30 second', '1969-12-31T19:00:30') as t; +---------------------+ | t | +---------------------+ | 1969-12-31T19:00:00 | +---------------------+ 1 row(s) fetched. Elapsed 0.001 seconds.
A time at the date_bin boundary to be in the correct bin:
> SELECT date_bin(INTERVAL '30 second', '1969-12-31T19:00:00') as t; +---------------------+ | t | +---------------------+ | 1969-12-31T19:00:00 | +---------------------+ 1 row(s) fetched. Elapsed 0.002 seconds. > SELECT date_bin(INTERVAL '30 second', '1969-12-31T19:00:30') as t; +---------------------+ | t | +---------------------+ | 1969-12-31T19:00:30 | +---------------------+ 1 row(s) fetched. Elapsed 0.001 seconds.
No response
The text was updated successfully, but these errors were encountered:
Possibly related: #10602
Sorry, something went wrong.
I believe that @itsjunetime is planning to look into this one
take
mhilton
Successfully merging a pull request may close this issue.
Describe the bug
For times before the unix epoch (1970-01-01T00:00:00) times at the boundary are incorrectly put into the previous time bin.
To Reproduce
In datafusion-cli:
Expected behavior
A time at the date_bin boundary to be in the correct bin:
Additional context
No response
The text was updated successfully, but these errors were encountered: