dragosmg commented on code in PR #13541:
URL: https://github.com/apache/arrow/pull/13541#discussion_r923222453
##########
r/R/dplyr.R:
##########
@@ -219,6 +219,31 @@ tail.arrow_dplyr_query <- function(x, n = 6L, ...) {
x
}
+#' Show the details of an Arrow Execution Plan
+#'
+#' This is a function which gives more details about the Execution Plan
(`ExecPlan`)
+#' of an `arrow_dplyr_query` object. It is similar to `dplyr::explain()`.
+#'
+#' @param x an `arrow_dplyr_query` to print the `ExecPlan` for.
+#'
+#' @return The argument, invisibly.
+#' @export
+#'
+#' @examplesIf arrow_with_dataset() & requireNamespace("dplyr", quietly = TRUE)
+#' library(dplyr)
+#' mtcars %>%
+#' arrow_table() %>%
+#' filter(mpg > 20) %>%
+#' mutate(x = gear/carb) %>%
+#' show_exec_plan()
+show_exec_plan <- function(x) {
+ adq <- as_adq(x)
+ plan <- ExecPlan$create()
+ final_node <- plan$Build(x)
+ cat(plan$ToString())
Review Comment:
@nealrichardson thanks for pointing me to use the first part of the
`ExecPlan_run`. I managed to get some output related to the `SinkNodes`, see
below:
``` r
mtcars %>%
arrow_table() %>%
filter(mpg > 20) %>%
arrange(desc(wt)) %>%
show_exec_plan()
#> ExecPlan with 4 nodes:
#> 3:OrderBySinkNode{by={sort_keys=[FieldRef.Name(wt) DESC],
null_placement=AtEnd}}
#> 2:ProjectNode{projection=[mpg, cyl, disp, hp, drat, wt, qsec, vs, am,
gear, carb]}
#> 1:FilterNode{filter=(mpg > 20)}
#> 0:TableSourceNode{}
```
but, we still lose some information when head/tail are involved:
``` r
mtcars %>%
arrow_table() %>%
filter(mpg > 20) %>%
arrange(desc(wt)) %>%
head(3) %>%
show_exec_plan()
#> ExecPlan with 3 nodes:
#> 2:SinkNode{}
#> 1:ProjectNode{projection=[mpg, cyl, disp, hp, drat, wt, qsec, vs, am,
gear, carb]}
#> 0:SourceNode{}
```
What I noticed is that, besides the loss of information on the `FilterNode`,
the starting point becomes a `SourceNode` and not a `TableSourceNode`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
