alamb commented on issue #13704: URL: https://github.com/apache/datafusion/issues/13704#issuecomment-2531427153
> I though this is covered by https://github.com/apache/datafusion/issues/12357 I could have included it in the same PR, but I thought this might generate some more discussion so might be better kept as a separate PR / issue > People are building database systems based on DataFusion where frontend is not DataFusion and SQL dialect is not DF's either. For example DataFusion Ballista effectively implements Spark SQL. SDF (not OSS) implements various SQL dialects on top of DF, etc. I know and I agree it is a very important usecase. I will try and update the wording in https://github.com/apache/datafusion/pull/13706 to reflect this sentiment > Thus, while it's important to be explicit what the frontend is meant to accept, it's also important to limit impact of this decision to DataFusion frontend only. It cannot trickle down across whole codebase. Yes, 100% agree. I also think it is worth thinking how we can keep any "postgres specific" stuff localized (or localize it even more0 to make it easier to override for systems that have different needs -- 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]
