fix(python): guard DataFusion FFI export on datafusion major version#4142
Conversation
Signed-off-by: Ethan Urbanski <[email protected]>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4142 +/- ##
==========================================
- Coverage 76.23% 76.17% -0.06%
==========================================
Files 164 164
Lines 45468 45471 +3
Branches 45468 45471 +3
==========================================
- Hits 34661 34638 -23
- Misses 9171 9198 +27
+ Partials 1636 1635 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ion-elgreco
left a comment
There was a problem hiding this comment.
I don't believe it should be only equal to a major version but greater than or equal to
|
@ion-elgreco if this version of the python package were used in the future with a datafusion-ffi of Basically as I understand the problem here, this version number will have to change as newer major releases are built into our wheels |
Only if the ffi interface changes but that's assuming we will have breaking changes every major release of datafusion-ffi. But before it was working for multiple major versions |
|
@ion-elgreco in the future we can update the check with the new major versions, but I think we should be strict until newer versions are proven to work. The consequences of failing is a complete segfault which is about as disastrous of an outcome as it gets |
|
@rtyler alright that's fair |
Description
Changes:
Note: This guard is a temporary safety net to prevent segfaults until DataFusion 52 Python wheels are available on PyPI. Once wheels land, users can install datafusion==52.* and use SessionContext registration normally.
Related Issue(s)
Documentation