You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When executing a query with a timestamp outside the supported range in the arrow cast, users receive a confusing error message about nanosecond overflow. This error message does not clearly explain the limitation of timestamp queries in Datafusion, confusing users.
To Reproduce
Execute a query with a timestamp outside the supported range (e.g., SELECT * FROM t WHERE a < '1650-01-01 01:01:01'::timestamp).
Expected behaviour
I expected to receive a clear error message that explains the limitation of timestamp queries in Datafusion (1677 to 2262) and suggests using timestamps within this range.
Additional context
This issue affects users who query timestamps outside the supported range in the arrow-cast. Improving the error message handling to provide clearer guidance would enhance user experience and reduce confusion.
The text was updated successfully, but these errors were encountered:
Describe the bug
When executing a query with a timestamp outside the supported range in the arrow cast, users receive a confusing error message about nanosecond overflow. This error message does not clearly explain the limitation of timestamp queries in Datafusion, confusing users.
To Reproduce
Expected behaviour
I expected to receive a clear error message that explains the limitation of timestamp queries in Datafusion (1677 to 2262) and suggests using timestamps within this range.
Additional context
This issue affects users who query timestamps outside the supported range in the arrow-cast. Improving the error message handling to provide clearer guidance would enhance user experience and reduce confusion.
The text was updated successfully, but these errors were encountered: