alamb commented on pull request #7967:
URL: https://github.com/apache/arrow/pull/7967#issuecomment-683714908


   > Final note: this whole discussion may be a bit too detailed for udfs, and 
we could instead offer a simpler interface to not handle these complex cases. 
However, this whole discussion applies in almost the same way to built-in 
functions: the only difference is whether they are of static lifetime or part 
of a registry. That is why I am so interested in all the "hard" cases.
   
   Another option that might be worth considering is "only allow simple types 
for user defined functions -- e.g. a single set of input types and a return 
type" 
   
   This would mean we could only implement functions like `array` and `concat` 
(as you have described it) as built in functions, but it would definitely 
simplify the code and UDF interface definition.
   
   I am not sure I like treating internal functions and external UDFs 
differently, but it might be worth considering. 


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to