asolimando commented on issue #21642: URL: https://github.com/apache/datafusion/issues/21642#issuecomment-4254482681
From your description it's clear that the current behavior wasn't intentional and it wasn't done as an optimization, so I agree this should be fixed. More generally, however, we are not forced to preserve anything from the user query but its semantics (the "result set"), otherwise we wouldn't be able to do many more useful things like swapping join operands etc., and the optimizer and runtime would lose a lot of freedom. If we want to give the user the capability to preserve "aspects" of the input query, we should consider adding SQL hints to that effect, but even those are just hints and not hard constraints. -- 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]
