Skip to content

Commit 1c2ee41

Browse files
committed
1 parent e1aa7d9 commit 1c2ee41

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎docs/source/user-guide/explain-usage.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ physical plan in Figure 1 in tree format will look like
131131
Each node in the tree/plan ends with `Exec` and is sometimes also called an `operator` or `ExecutionPlan` where data is
132132
processed, transformed and sent up.
133133

134-
1. First, data in parquet the `hits.parquet` file us read in parallel using 16 cores in 16 "partitions" (more on this later) from `DataSourceExec`, which applies a first pass at filtering during the scan.
134+
1. First, data in parquet the `hits.parquet` file is read in parallel using 16 cores in 16 "partitions" (more on this later) from `DataSourceExec`, which applies a first pass at filtering during the scan.
135135
2. Next, the output is filtered using `FilterExec` to ensure only rows where `starts_with(URL, 'http://domcheloveplanet.ru/')` evaluates to true are passed on
136136
3. The `CoalesceBatchesExec` then ensures that the data is grouped into larger batches for processing
137137
4. The `ProjectionExec` then projects the data to rename the `WatchID` and `ClientIP` columns to `wid` and `ip` respectively.

0 commit comments

Comments
 (0)