[R] Allow functions with {{pkg::}} prefixes

[asfimport]

{}Proposed approach{}:

• add functionality to allow binding registration with the pkg::fun() name;
  • Modify register_binding() to register 2 identical copies for each pkg::fun binding, fun and pkg::fun.
  • Add a binding for the :: operator, which helps with retrieving bindings from the function registry.
  • Add generic unit tests for the pkg::fun functionality.
• register nse_funcs requiring indirect mapping
  • register each binding with and without the pkg:: prefix
  • add / update unit tests for the nse_funcs bindings to include at least one pkg::fun() call for each binding
• register nse_funcs requiring direct mapping (unary and binary bindings)
  • register each binding with and without the pkg:: prefix
  • add / update unit tests for the nse_funcs bindings to include at least one pkg::fun() call for each binding
• register agg_funcs for use with summarise()
• document changes in the Writing bindings documentation

  • going forward we should be using pkg::fun when defining a binding, which will register 2 copies of the same binding.

    Different implementation options are outlined and discussed in the design document.

    {}Description{}:
    Currently we implement a number of functions from packages like lubridate which work well when called without namespacing (e.g. {}year(){}), however if someone calls lubridate::year() we get a not-implemented method (e.g. {}Warning: Expression lubridate::year(time_hour) not supported in Arrow{}). Is it possible for us to look and see if we have an arrow function that matches the function itself.
    {code:r}
    library(arrow, warn.conflicts = FALSE)
    library(dplyr, warn.conflicts = FALSE)

    ds <- InMemoryDataset$create(nycflights13::flights)

    ds %>%
    mutate(year = lubridate::year(time_hour)) %>%
    collect()
    #> Warning: Expression lubridate::year(time_hour) not supported in Arrow; pulling
    #> data into R
    #> # A tibble: 336,776 × 19
    #> year month day dep_time sched_dep_time dep_delay arr_time sched_arr_time
    #>
    #> 1 2013 1 1 517 515 2 830 819
    #> 2 2013 1 1 533 529 4 850 830
    #> 3 2013 1 1 542 540 2 923 850
    #> 4 2013 1 1 544 545 -1 1004 1022
    #> 5 2013 1 1 554 600 -6 812 837
    #> 6 2013 1 1 554 558 -4 740 728
    #> 7 2013 1 1 555 600 -5 913 854
    #> 8 2013 1 1 557 600 -3 709 723
    #> 9 2013 1 1 557 600 -3 838 846
    #> 10 2013 1 1 558 600 -2 753 745
    #> # … with 336,766 more rows, and 11 more variables: arr_delay ,
    #> # carrier , flight , tailnum , origin , dest ,
    #> # air_time , distance , hour , minute , time_hour

ds %>%
mutate(year = year(time_hour)) %>%
collect()
#> # A tibble: 336,776 × 19
#> year month day dep_time sched_dep_time dep_delay arr_time sched_arr_time
#>
#> 1 2013 1 1 517 515 2 830 819
#> 2 2013 1 1 533 529 4 850 830
#> 3 2013 1 1 542 540 2 923 850
#> 4 2013 1 1 544 545 -1 1004 1022
#> 5 2013 1 1 554 600 -6 812 837
#> 6 2013 1 1 554 558 -4 740 728
#> 7 2013 1 1 555 600 -5 913 854
#> 8 2013 1 1 557 600 -3 709 723
#> 9 2013 1 1 557 600 -3 838 846
#> 10 2013 1 1 558 600 -2 753 745
#> # … with 336,766 more rows, and 11 more variables: arr_delay ,
#> # carrier , flight , tailnum , origin , dest ,
#> # air_time , distance , hour , minute , time_hour
{code}

Reporter: Jonathan Keane / @jonkeane
Assignee: Dragoș Moldovan-Grünfeld / @dragosmg

Subtasks:

• [R] Add functionality to allow binding registration with the pkg::fun name
• [R] Register nse_funcs requiring indirect mapping
• [R] Register nse_funcs requiring direct mapping (unary & binary)
• [R] [Doc] Document changes in the Writing bindings documentation

Related issues:

• [R] dplyr n function cannot be called with dplyr::n() (is duplicated by)
• [R] Create a function registry for our NSE funcs (relates to)

PRs and other links:

• GitHub Pull Request #13160
• GitHub Pull Request #13513

_{Note: This issue was originally created as ARROW-14575. Please see the migration documentation for further details.}

[asfimport]

Neal Richardson / @nealrichardson:
We could pre-process the expression/quosure and remove any ::, though that might not be safe? We could also include an allowlist/mapping of functions we would do this for (e.g. list(lubridate = c("year", "month", ...), dplyr = c("case_when", "n", ...), stringr = c("str_stuff", ...)).

[asfimport]

Jonathan Keane / @jonkeane:
Yeah, there is certainly some edgecases/unsafeness that we need to consider. Though hard-coding is frustrating, the allowlist would make it explicit what our intention is with the binding. I wonder if it is possible to mask with the {pkg::} included so that we would get the right behavior if someone had a custom-defined function that collides with a function we have made a binding for (e.g. I've defined a custom year() in my code, I know that that will mask lubridate's year(), so I put lubridate::year() in all my pipelines, but sometimes need to / want to call my custom year — this wouldn't (possibly) work until ARROW-14071 anyway).

Getting the execution exactly right and being able to select the right year() here is probably less important than erroring loudly and not using the bindings version when that's not what dplyr would do in that case. Though I will say that I have definitely seen things like this and worse in actuality!

[asfimport]

Dewey Dunnington / @paleolimbot:
It might be nice for clarity to register the package name with the function (i.e., arrow_register_translation("year", function(...) {}, package = "lubridate") instead of nse_funcs$year <- function(...) {}.

Erroring out could look like this (only slightly better than the current error, though).

library(arrow, warn.conflicts = FALSE)
library(dplyr, warn.conflicts = FALSE)

ds <- InMemoryDataset$create(nycflights13::flights)
funs <- arrow:::.cache$functions
funs[["::"]] <- function(lhs, rhs) {
 arrow:::arrow_not_supported("`::`")
}

assign("functions", funs, envir = arrow:::.cache)
ds %>% 
 mutate(year = lubridate::year(time_hour)) %>%
 collect()
#> Warning: In lubridate::year(time_hour), `::` not supported by Arrow; pulling
#> data into R
#> # A tibble: 336,776 × 19

A slightly different definition of :: could ignore it with a warning, although this is possibly a bit too magical.

library(arrow, warn.conflicts = FALSE)
library(dplyr, warn.conflicts = FALSE)

ds <- InMemoryDataset$create(nycflights13::flights)
funs <- arrow:::.cache$functions

funs[["::"]] <- function(lhs, rhs) {
 # already evaluated to an Expression?
 rhs <- rhs$field_name
 warning(paste0("Replacing `", as.character(substitute(lhs)), "::", rhs, "` with `", rhs, "`"))
 get(rhs, envir = parent.frame(), mode = "function")
}

assign("functions", funs, envir = arrow:::.cache)
ds %>% 
 mutate(year = lubridate::year(time_hour)) %>%
 collect()
#> Warning in lubridate::year: Replacing `lubridate::year` with `year`
#> # A tibble: 336,776 × 19
#> year month day dep_time sched_dep_time dep_delay arr_time sched_arr_time
#> <int> <int> <int> <int> <int> <dbl> <int> <int>
#> 1 2013 1 1 517 515 2 830 819
#> 2 2013 1 1 533 529 4 850 830
#> 3 2013 1 1 542 540 2 923 850
#> 4 2013 1 1 544 545 -1 1004 1022
#> 5 2013 1 1 554 600 -6 812 837
#> 6 2013 1 1 554 558 -4 740 728
#> 7 2013 1 1 555 600 -5 913 854
#> 8 2013 1 1 557 600 -3 709 723
#> 9 2013 1 1 557 600 -3 838 846
#> 10 2013 1 1 558 600 -2 753 745
#> # … with 336,766 more rows, and 11 more variables: arr_delay <dbl>,
#> # carrier <chr>, flight <int>, tailnum <chr>, origin <chr>, dest <chr>,
#> # air_time <dbl>, distance <dbl>, hour <dbl>, minute <dbl>, time_hour <dttm>

 

 

[asfimport]

Dewey Dunnington / @paleolimbot:
A few ideas related to this that may or may not help organize the increasing set of functions from different packages.

Translations for specific packages as R6 classes? Advantage here just that we get documentation that isn’t checked by CRAN for free.

BaseTranslations <- R6::R6Class(
 "BaseTranslations",
 public = list(
 
 #' Arrow compute translation for `base::sum()`
 #' 
 #' @param x A field reference or scalar
 sum = function(x) {
 arrow::Expression$create(
 "sum",
 if (inherits(x, "Expression")) x else sum(x)
 )
 }
 )
)

...and a totally untested interface for keeping track of function translations from multiple packages.

Helper to detect the package that a user intended based on their current search path

detect_package_name <- function(name, env = parent.frame()) {
 tryCatch({
 obj <- get(name, env = env, mode = "function", inherits = TRUE)
 obj_env <- environment(obj)
 if (is.null(obj_env)) {
 "base"
 } else if (".packageName" %in% names(obj_env)) {
 obj_env$.packageName
 } else {
 NULL
 }
 }, error = function(e) {
 NULL
 })
}

Using R6 for my basic implementation of a function registry that includes the intended package for a translation. These can be stacked and recombined similar to how environments can be stacked and combined so that each set of translations can have a limited scope.

TranslationRegistry <- R6::R6Class(
 "TranslationRegistry",
 public = list(
 initialize = function(parent = NULL) {
 private$parent <- parent
 private$functions <- new.env(parent = emptyenv())
 private$functions$`_all_functions` <- new.env(parent = emptyenv())
 },

 register_translation = function(name, fun, package = NULL, env = parent.frame()) {
 if (is.null(package)) {
 package <- detect_package_name(name)
 }

 if (!is.null(package) && !(package %in% names(private$functions))) {
 private$functions[[package]] <- new.env(parent = emptyenv())
 }

 if (!is.null(package)) {
 private$functions[[package]][[name]] <- fun
 }

 private$functions$`_all_functions`[[name]] <- fun

 invisible(self)
 },

 get_translation = function(name, package = NULL, env = parent.frame()) {
 if (is.null(package)) {
 package_det <- detect_package_name(name, env = env)
 } else {
 package_det <- package
 }

 if (is.null(package_det)) {
 package_det <- "_all_functions"
 }

 if (is.null(private$parent)) {
 tryCatch(get(name, envir = get(package_det, envir = private$functions)), error = function(e) {
 self$abort_function_not_found(name, package)
 })
 } else {
 tryCatch(
 get(name, envir = get(package_det, envir = private$functions)),
 error = function(e) private$parent$get_translation(name, package = package, env = env)
 )
 }
 },

 with_search = function(order = search()) {
 order <- rev(intersect(gsub("package:", "", order), names(private$functions)))
 funs_with_pkg <- unlist(
 lapply(
 setdiff(names(order), "_all_functions"),
 function(pkg) names(private$functions[[pkg]])
 )
 )
 funs_without_pkg <- setdiff(names(private$functions$`_all_functions`), funs_with_pkg)

 out_names <- c(funs_without_pkg, funs_with_pkg)
 out <- vector("list", length(out_names))
 names(out) <- out_names

 i <- 1L
 for (pkg in order) {
 for (name in names(private$functions[[pkg]])) {
 out[[i]] <- private$functions[[pkg]][[name]]
 i <- i + 1L
 }
 }

 out
 },

 abort_function_not_found = function(name, package) {
 if (is.null(package)) {
 msg <- glue::glue("No translations registered for function `{ name }()`")
 } else if (!(package %in% names(private$functions))) {
 msg <- glue::glue("No translations registered for package '{ package }'")
 } else {
 msg <- glue::glue("No translations registered for function `{ package }::{ name }()`")
 }

 rlang::abort(msg , class = "function_not_found")
 }
 ),

 private = list(
 parent = NULL,
 functions = NULL
 )
)

In practice this would be an under-the-hood thing accessed by regular functions

translations <- TranslationRegistry$new()
register_translation <- function(name, fun, package = NULL, env = parent.frame()) {
 translations$register_translation(name, fun, package = package, env = env)
}
get_translation <- function(name, package = NULL, env = parent.frame()) {
 translations$get_translation(name, package = package, env = env)
}
translations_with_search <- function(order = search()) {
 translations$with_search(order)
}

The basic idea is that you can register some functions and get a decent error when requesting one that doesn’t exist.

register_translation("sum", function(x) {
 arrow::Expression$create(
 "sum",
 if (inherits(x, "Expression")) x else sum(x)
 )
})

get_translation("sum")
#> function(x) {
#> arrow::Expression$create(
#> "sum",
#> if (inherits(x, "Expression")) x else sum(x)
#> )
#> }
get_translation("sum", package = "base")
#> function(x) {
#> arrow::Expression$create(
#> "sum",
#> if (inherits(x, "Expression")) x else sum(x)
#> )
#> }

get_translation("summ")
#> Error: No translations registered for function `summ()`
get_translation("sum", package = "basee")
#> Error: No translations registered for package 'basee'
get_translation("summ", package = "base")
#> Error: No translations registered for function `base::summ()`

Need to override :: for the nice errors

register_translation("::", function(lhs, rhs) {
 get_translation(
 as.character(substitute(rhs)),
 as.character(substitute(lhs))
 )
})

Use translations_with_search() to resolve the list of translations based on the current search path (so that we can use it for a data mask).

rlang::eval_tidy(
 rlang::quo(base::sum(some_field)),
 data = c(
 list(some_field = arrow::Expression$field_ref("some_field")),
 translations_with_search()
 )
)
#> Expression
#> sum(some_field, {skip_nulls=true, min_count=1})

[asfimport]

Dragoș Moldovan-Grünfeld / @dragosmg:
I have an draft PR for allowing pkg:: prefixes. What do you think of this approach?

• change the naming convention for bindings, by adding "package_" before the function name. For example "as_datetime" becomes {}"lubridate_as_datetime"{}. Doing this mainly for 2 reasons:
  • it gives us an indication of the package / namespace we're linking to
  • it avoids the use of the double-colon ({}::{}) operator (easier dealing with strings only)
• we register each binding both with its short name ({}"as_datetime"{}) and its full name ({}"lubridate_as_datetime"{})
• we change the expressions supplied by the user by replacing the double colon ({}::{}) with an underscore ({}_{})
• we can still include the original expression (containing :: in the error message)
• we don't have to define an allow list as the user will get the same message they are getting: "now pkg::fun() not supported in Arrow".

[asfimport]

Dragoș Moldovan-Grünfeld / @dragosmg:
I went in a slightly different direction from the one sketched-out by @paleolimbot for several reasons:

• chronologically, the above was outlined before the implementation of the new function registry (ARROW-15010), which diverged from the above sketch.
• the proposed implementation is somewhat simpler and, thus, easier to maintain
• it integrates well with the current function registry.

[asfimport]

Neal Richardson / @nealrichardson:
Issue resolved by pull request 13160
#13160