Kimahriman commented on issue #11923: URL: https://github.com/apache/datafusion/issues/11923#issuecomment-2281241125
> What might be the downside if the array is always nullable? Loss the possibility for non-null optimization That would be the main thing. In this case I came across this trying to integrate array support into `datafusion-comet` and it was inconsistent with Spark's handling of arrays. Maybe not the best reason to change, but it also seems weird to have nullability be tracked but not track it correctly. > If there is such a need for most of the functions, we might not need `return_type` anymore but `return_type_from_exprs` instead. That is a huge change. The actual change per function isn't that much, working on what the `make_array` update would look like. -- 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]
