Skip to content

Update to a datafusion-55 prerelease #5553

Closed

Description

@stuhood

What feature are you requesting?

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.

Full Name:

Stu Hood

Affiliation:

ParadeDB

Activity

  1. added a commit that references this issue on Jul 28, 2026
    fb90b2b
  2. added a commit that references this issue on Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

featureNew feature or requestpriority-highHigh priority issuerefactorRefactor of existing code

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions