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
I can't think of any practical usecase for making making pure null arrays , though maybe I am missing something. Adding lots of code for a case no one is likely to actually use seems unecessary to me.
Thus, perhaps following DuckDB's behavior and picking some arbitrary type like int32[] is reasonable. Or maybe even generating a "not yet supported" error and waiting for someone to report on their actual usecase before we spend engineering time on sorting out how to make it behave 🤔
@alamb In my opinion, we should not pay attention to pure null arrays now, so I agree with you that it is better to wait until another user raises this issue.
Describe the bug
DataFusion supports now heterogeneous arrays (i.e. containing
NULL
with another data type), but does not support pure null array.To Reproduce
DataFusion:
Expected behavior
The output should be equal like in other databases (DuckDB, ClickHouse, PostgreSQL):
DuckDB:
ClickHouse:
PostgreSQL:
Additional context
No response
The text was updated successfully, but these errors were encountered: