You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the FFI crate evolves we need some way to verify across the FFI boundary the version compatibility.
Describe the solution you'd like
Likely we need to add a function that is a simple version output in datafusion-ffi so that users can query across the boundary and verify the versions of the API are compatible.
Describe alternatives you've considered
None I can think of.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I likely don't really understand FFI yet, but I think what is needed is that the FFI bindings used match the version of DataFusion that will use the TableProvider
SO in this case if we merge #13823 prior to releaseing 0.44.0 it will mean anyone who wants to use their table provider in 0.44 via FFI will hvae to update the FFI bindings. So to use a TableProvider based on DataFusion 43 someone will have to implement the DataFusion 44 bindings by calling the DataFusion 43 provider
Is your feature request related to a problem or challenge?
This came up as part of this PR: #13823
As the FFI crate evolves we need some way to verify across the FFI boundary the version compatibility.
Describe the solution you'd like
Likely we need to add a function that is a simple version output in
datafusion-ffi
so that users can query across the boundary and verify the versions of the API are compatible.Describe alternatives you've considered
None I can think of.
Additional context
No response
The text was updated successfully, but these errors were encountered: