benibus commented on issue #25025: URL: https://github.com/apache/arrow/issues/25025#issuecomment-1439069334
I did play around with that idea, although I'm a little hesitant to commit to explicit initialization since I fear the C++ breakage would be severe - primarily because we wouldn't be able to access the extended registry from within libarrow itself. For instance, `ExecContext`'s default constructor wouldn't be able to implicitly register those kernels outside of libarrow_compute, so any user/test code that utilizes `equal` or `add` would now need to proactively load the registry. You could get around that in the wrappers to some extent, but it wouldn't be complete. 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). -- 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]
