alamb opened a new pull request, #8039: URL: https://github.com/apache/arrow-datafusion/pull/8039
## Which issue does this PR close? Part of https://github.com/apache/arrow-datafusion/issues/7110 and https://github.com/apache/arrow-datafusion/issues/7977 ## Rationale for this change Over time, the number of built in functions within DataFusion grows which is challenging both because: 1. The total footprint grows, even for those who don't need the specific functions 2. The desired semantics may be different (e.g. many of the built in functions in DataFusion mirror postgres behavior, but some users wish to mimic spark behavior 3. User defined functions are treated differently from built in functions in some ways (e.g. they can't have aliases) If is for this reason I would like to move towards *only* having functions defined as `ScalarUDFs` This will ensure: 1. ScalarUDFs have access to all the same functionality as "built in " functions 2. No function specific code will escape the planning ## What changes are included in this PR? 1. Make all fields of `ScalarUDF` private and add accessors. ## Are these changes tested? Covered by existing tests -- 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]
