Skip to content

Consider folding CoalesceAsyncExecInput physical optimizer rule into CoalesceBatches #18155

Description

@Jefffrey

Is your feature request related to a problem or challenge?

These are quite similar, I wonder if we can embed the logic from CoalesceAsyncExecInput into existing rule CoalesceBatches to consolidate the codebase a bit 🤔

Reference links:

Describe the solution you'd like

Move logic of CoalesceAsyncExecInput into CoalesceBatches and delete CoalesceAsyncExecInput

Describe alternatives you've considered

If not possible then don't do this approach

Additional context

No response

Activity

  1. added theissue type on Oct 19, 2025
  2. 0xEbrahim commented on Oct 19, 2025

    @0xEbrahim

    Can you assign to me, i will work on it at the weekend

  3. Jefffrey commented on Oct 19, 2025

    @Jefffrey
    ContributorAuthor

    Can you assign to me, i will work on it at the weekend

    Cheers! Feel free to take this issue as described here: https://datafusion.apache.org/contributor-guide/index.html#open-contribution-and-assigning-tickets

  4. 0xEbrahim commented on Oct 19, 2025

    @0xEbrahim

    take

  5. Tim-53 commented on Nov 8, 2025

    @Tim-53
    Contributor

    I noticed there hasn’t been any recent activity on this issue, so I went ahead and opened #18540 that folds CoalesceAsyncExecInput into CoalesceBatches as proposed.

  6. added a commit that references this issue on Nov 11, 2025
    9029ff1
  7. added a commit that references this issue on Nov 11, 2025
    953cbc4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions