jayzhan211 commented on PR #11447: URL: https://github.com/apache/datafusion/pull/11447#issuecomment-2230463798
@eejbyfeldt I see. I agree the motivation here is not really a good reason, but it is my tradeoff about how we can move on for aggregate function. I think the tradeoff here is having *idea* nullability for possible optimization and having *correct* but simple nullability **for now** and able to bring in *idea* nullability with **actual** optimization in the future. > For me, the reason to have the correct nullability of the field inside the returned list is the same as having correct nullability for any other field The nullability of field is actually the reason that matters to me. I'm not sure if there is possible improvement for **nullable element** in aggregate function. If there is any optimization like what you show me previously, I would be happy to keep the nullability and find an idea way to bring it to UDAF. -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
