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
{{ message }}
Repository navigation
Commit 9935bc6
Browse filesBrowse the repository at this point in the historyBrowse files
docs: correct the pin rationale and derived-context caveats
The Cargo.toml comment justified the pre-release pin by "the FFI codec
rebinding in `PySessionContext::derived_parts`", a symbol that no longer
exists. That rebinding was not removed, it moved into
`set_session_query_planner`, which every `with_*` method calls. It depends on
`FFI_QueryPlanner::new_with_ffi_codecs` unwrapping a `ForeignQueryPlanner` and
replacing its codecs, a swap that is a silent no-op before 55.1.0
(apache/datafusion#24722). So the pin is still required, not droppable.
The `with_*` methods rebuild the installed planner on the *shared* session, so
the rebind takes effect even when the returned context is discarded.
`with_python_udf_inlining` additionally claimed "the original session is
unchanged", which the rebuild contradicts; it is the context's own codec
settings that are unchanged.
Also:
- Note that the arity-vs-body TypeError split in `call_capsule_getter` holds
only because the call originates in Rust. A Python-level shim between the
host and the getter would supply a traceback and silently disable it.
- Document the new FFI major-version gate in the 55.0.0 upgrade guide. Table
providers previously performed no such check, so a mismatched extension
library that used to load now raises ImportError.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
0 commit comments