Skip to content
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.

fix the code path in projection-pushdown #211

Merged
merged 1 commit into from
Dec 20, 2022
Merged

fix the code path in projection-pushdown #211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions user_guide/src/optimizations/lazy/projection-pushdown.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Again, let's take a look the query plan.
dataset.show_graph(optimized=False)
```

![](./../outputs/projection_pushdown/graph.png)
![](../../outputs/projection_pushdown/graph.png)

Now were focussed on the projection's indicated with π. The first node shows π 3/6,
indicating that we select 3 out of 6 columns in the `DataFrame`. If we look the csv scans
Expand All @@ -48,7 +48,7 @@ Let's see how `Polars` optimizes this query.
dataset.show_graph(optimized=True)
```

![](./../outputs/projection_pushdown/graph-optimized.png)
![](../../outputs/projection_pushdown/graph-optimized.png)

The projections are pushed down the join operation all the way to the csv scans. This
means that both the scanning and join operation have become cheaper due to the query
Expand Down