Re: [I] [DISCUSSION] Add separate crate to cover spark builtin functions [datafusion]

["Spaarsh (via GitHub)" <gi...@apache.org>]

Spaarsh commented on issue #5600:
URL: https://github.com/apache/datafusion/issues/5600#issuecomment-2646416918

   I began contributing to this repo only from a month ago so please pardon an errs from my side, but I just wanted to suggest something. 
   
   Since we're planning of having a separate mode for spark wherein a user can access all spark functions and also not make the main code dependent on this crate, I was thinking if there was still a way of using these spark functions alongside our main df functions (i implied that all core functions won't be available in this mode since there are many similarly named functions). Could we allow optional import of our main df functions in the spark mode cli? This might be a makeshift solution for now but this way our users who migrate from spark can ALSO be exposed to our core functions and use them!
   
   Or perhaps we could implement a "import function_name" kind of command that imports only a specific function or set of functions and checks for conflicting names.
   
   From my work in the xxhash functions in the code, the mod.rs enlists all functions in that directory so this seems easier in theory.
   
   Thanks.


-- 
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: github-unsubscribe@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org