comphead opened a new issue, #5600: URL: https://github.com/apache/arrow-datafusion/issues/5600
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** The discussion is to collect community thoughts on implementing spark builtin functions listed https://spark.apache.org/docs/3.2.0/api/sql/ We more often face the requests to implement Spark functions and the use case on person/company stack, one treats the spark more important, for others its opposite and PG compatibility is a priority Builtin function list between Postgres and Spark are expectedly not the same. I believe it can be rare and worse cases when the function name the same but signature and/or return type is different. The discussion goal is to find out how to organize DF and keep compatibility for majors like Spark, Postgres, and perhaps other systems <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) --> **Describe the solution you'd like** @alamb in https://github.com/apache/arrow-datafusion/issues/5568#issuecomment-1466608119 made a proposition to create an extensible crate for spark functions, or even it can be a separate subproject so the PG users have the possibility to exclude Spark functions. <!-- A clear and concise description of what you want to happen. --> **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> Not doing this **Additional context** <!-- Add any other context or screenshots about the feature request here. --> Created after https://github.com/apache/arrow-datafusion/issues/5568#issuecomment-1466608119 -- 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]
