alamb commented on PR #21743: URL: https://github.com/apache/datafusion/pull/21743#issuecomment-4412252130
I think at this point in DataFusion's life (where it has a bunch of existing users with real customers, etc) we need to be careful about changing semantics of already existing functions If there is some clear benefit or the old behavior is clearly wrong, that is one thing However, just changing the semantics to be slightly more compatible with Postgres I don't think is a great reason to break downstream users I think this is somewhat covered in https://datafusion.apache.org/contributor-guide/api-health.html#when-to-make-breaking-api-changes but that doesn't explicitly mention SQL. I'll try and propose adding some SQL specific changes to it too -- 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]
