Jefffrey opened a new issue, #24136: URL: https://github.com/apache/datafusion/issues/24136
### Is your feature request related to a problem or challenge? Looking at `btrim` for example: https://github.com/apache/datafusion/blob/f27e50c13647efa5292d5ef5b1e4ed6af3015962/datafusion/functions/src/string/btrim.rs#L82-L93 It specifies it accepts 2 string input types. However the planner doesn't coerce them to a common type, leaving it up to the UDF to handle casting to a common type for simplicity (otherwise get explosion of string types to handle): https://github.com/apache/datafusion/blob/f27e50c13647efa5292d5ef5b1e4ed6af3015962/datafusion/functions/src/string/btrim.rs#L32-L43 ### Describe the solution you'd like Some way in the coercible signature API to specify when inputs should have same type. We previously could do this via: ```rust TypeSignature::Uniform(2, vec![Utf8, Utf8View, LargeUtf8]) TypeSignature::Exact(vec![Utf8, Utf8]) // and other variants TypeSignature::String(2) ``` So if we want to still try move toward coercible API, it would be good to support this somehow otherwise its very much less ergonomic for UDFs to handle this logic themselves. ### 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
