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
We should port paradedb/main to a datafusion-55 prelease. Currently (July 13th 2026) that means targeting datafusion@main, because no DataFusion 55 branch has been cut yet (expect it to be called "branch-55").
Why are you requesting this feature?
Upcoming work on segment partitioning will rely on work happening upstream in apache/datafusion#22395
What is your proposed implementation for this feature?
Here are some initial datafusion-distributed and paradedb branches for this:
As seen in regress changes on the paradedb PR, we seem to be losing many dynamic filters, even in non-df-d plans. This could either be due to hacks that we have in place (./pg_search/src/scan/filter_passthrough_exec.rs), or to bugs upstream.
Activity
Upgrade to pre-release DataFusion 55 (#44)
chore: Upgrade to datafusion 55 (paradedb#5634)
Upgrade to pre-release DataFusion 55 (#44)
Upgrade to pre-release DataFusion 55 (#44)
Upgrade to pre-release DataFusion 55 (#44)
Upgrade to pre-release DataFusion 55 (#44)
Upgrade to pre-release DataFusion 55 (#44)
Upgrade to pre-release DataFusion 55 (#44)
Upgrade to pre-release DataFusion 55 (paradedb#44)
Upgrade to pre-release DataFusion 55 (#44)
Upgrade to pre-release DataFusion 55 (paradedb#44)
Upgrade to pre-release DataFusion 55 (paradedb#44)
Upgrade to pre-release DataFusion 55 (paradedb#44)
Upgrade to pre-release DataFusion 55 (paradedb#44)
Upgrade to pre-release DataFusion 55 (paradedb#44)
Upgrade to pre-release DataFusion 55 (#44)