jorisvandenbossche commented on issue #25025: URL: https://github.com/apache/arrow/issues/25025#issuecomment-1444091022
>> I should mention, another alternative would be to not build the separate lib at all - instead, just optionally include those kernels in libarrow. That might be the approach I take for the initial PR (we'd have a more concrete starting point, at least). > > That solves the main problem, which is just being able to assume availability of Cast. We can argue about what is the "main" problem, but this certainly doesn't solve the use case of being able to install the compute kernels optionally/separately, which a separate shared library would enable (eg a package manager like conda could package `libarrow_compute` separately from `libarrow`, so that the _user_ can determine if they need all compute or not. While with the above solution, it's the _developer/packager_ that needs to make this decision upfront if they include all compute kernels or not at compile time) -- 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]
