adriangb opened a new issue, #25169:
URL: https://github.com/apache/datafusion/issues/25169
### Describe the bug
`generate_series` / `range` over timestamps accept only nanosecond
precision. Any other `TimeUnit` fails with an error that says the argument is
not a timestamp, while naming a timestamp:
```sql
SELECT * FROM generate_series(
arrow_cast(TIMESTAMP '2024-01-01 00:00:00','Timestamp(Second, None)'),
arrow_cast(TIMESTAMP '2024-01-03 00:00:00','Timestamp(Second, None)'),
INTERVAL '1 day');
Error during planning: First argument must be a timestamp or NULL,
got Literal(TimestampSecond(1704067200, None), None)
```
The same query with `Timestamp(Nanosecond, …)` works.
### To Reproduce
The query above, on DataFusion 55.0.0 (`da89c7c85b`).
### Expected behavior
Either accept all four `TimeUnit`s (coercing to nanoseconds internally), or
produce an error that says what is actually wrong — something like "expects
nanosecond precision, got Timestamp(Second)".
The current message is actively misleading: it says the argument must be a
timestamp and then prints a timestamp, which sends you looking in the wrong
place. This matters more than it looks, because second and millisecond
precision are common in Parquet files, so a `generate_series` over a column
read from storage can fail while the same logic written with literals succeeds.
Found while adding timezone characterization tests in #25164.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
