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 71beb85
Browse filesBrowse the repository at this point in the historyBrowse files
Treat a fetch as a barrier in the PushdownSort and FilterPushdown rules
Replace the scan-level `limit` checks with one check per rule, as
suggested in review: a node with a fetch keeps the first rows in its
input's current order, so `PushdownSort` must not reorder the input
below it and `FilterPushdown` must not move a filter from above into or
below it (the node's own filters still push down).
This also fixes#27194 at the default configuration. The two
`filter_pushdown.rs` snapshots that merged an outer filter into a
`FilterExec` with a fetch now keep the filters separate, which keeps the
rows the inner fetch picks.
0 commit comments