2010YOUY01 opened a new issue, #7977: URL: https://github.com/apache/arrow-datafusion/issues/7977
### Is your feature request related to a problem or challenge? As previously discussed in https://github.com/apache/arrow-datafusion/issues/7110 https://github.com/apache/arrow-datafusion/pull/7752 : We want to define Scalar Functions outside the core to reduce Datafusion Core binary size, and also make UDF management easy. But the current `BuiltinScalarFunction` and `ScalarUDF` interface are not capable to do this, so we would like to introduce a new interface `trait ScalarFunctionDef` and gradually migrate existing functions into the new one. ### Describe the solution you'd like ## Objective 1. Define a new interface `trait ScalarFunctionDef` to solve the above-mentioned issue 2. Now built-in functions are using `Enum BuiltinScalarFunction` as the underlying execution mechanism in the core code, and scalar UDFs are using `Struct ScalarUDF`, both will be moving to `ScalarFunctionDef` as the unified internal representation. ## Implementation Plan 1. Introducing new interface `ScalarFunctionDef` and replace the old built-in functions' execution code 1.1 Replace SQL execution code with `ScalarFunctionDef` 1.2 Change other relevant execution components, like the Logical Expression Constructor for Scalar Functions, to be compatible with `ScalarFunctionDef`. 2. Migrate old UDF Implementations: `Struct ScalarUDF` -> `ScalarFunctionDef` 3. Function package management interface ...and migrating existing functions ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- 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]
