You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by "alamb (via GitHub)" <gi...@apache.org> on 2023/03/15 10:00:45 UTC

[GitHub] [arrow-datafusion] alamb commented on issue #5600: [DISCUSSION] Add separate crate to cover spark builtin functions

alamb commented on issue #5600:
URL: https://github.com/apache/arrow-datafusion/issues/5600#issuecomment-1469703505

   I also agree (unsurprisingly) that a separate crate for libraries of functions would be valuable. 
   
   Overall, keeping datafusion setup with a core and then a bunch of extension points,  such that different sets of functionalty can be assembled for whatever usecase people want would be my ideal.
   
   For example, there are already a bunch of functions that in theory should be "optional" via feature flags-- 
   
   https://github.com/apache/arrow-datafusion/blob/6bfede0e1e1a09bd06ea0166e01c0ad4834a1721/datafusion/physical-expr/Cargo.toml#L35-L42
   
   But I am not sure how well the vision and reality match (as in does anyone use datafusion without them)


-- 
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@arrow.apache.org

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