Skip to content

Regression: projection pushdown doesn't work as expected in DF50 #17513

Closed

Description

@xudong963
// t1 contains a,b
DF49
> explain select from t1 where t1.a > 1;
+--------------+----------------------------------+
| plan_type    | plan                             |
+--------------+----------------------------------+
| logical_plan | Projection:                      |
|              |   Filter: t1.a > Int32(1)        |
|              |     TableScan: t1 projection=[a] |
+--------------+----------------------------------+
1 row(s) fetched.
Elapsed 0.004 seconds.

DF50
> explain select from t1 where t1.a > 1;
+--------------+-----------------------------------+
| plan_type    | plan                              |
+--------------+-----------------------------------+
| logical_plan | Filter: t1.a > Int32(1)           |
|              |   TableScan: t1 projection=[a, b] |
+--------------+-----------------------------------+
1 row(s) fetched.
Elapsed 0.003 seconds.

Activity

  1. adriangb commented on Sep 11, 2025

    @adriangb
    Contributor

    I ran a bisect and found that #17295 introduced this bug

  2. added 2 commits that reference this issue on Sep 11, 2025
    1089c45
    66bece8
  3. added 2 commits that reference this issue on Sep 12, 2025
    5fd831f
    8e67df0
  4. added a commit that references this issue on Sep 13, 2025
    10343c1
  5. added a commit that references this issue on Sep 15, 2025
    28c77a8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    regressionSomething that used to work no longer does

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions