These functions are wrappers around their `dplyr` equivalents that set Spark SQL-compliant values for the `suffix` argument by replacing dots (`.`) with underscores (`_`). See [join] for a description of the general purpose of the functions.
Usage
# S3 method for class 'tbl_spark'
inner_join(
x,
y,
by = NULL,
copy = FALSE,
suffix = c("_x", "_y"),
auto_index = FALSE,
...,
sql_on = NULL
)
# S3 method for class 'tbl_spark'
left_join(
x,
y,
by = NULL,
copy = FALSE,
suffix = c("_x", "_y"),
auto_index = FALSE,
...,
sql_on = NULL
)
# S3 method for class 'tbl_spark'
right_join(
x,
y,
by = NULL,
copy = FALSE,
suffix = c("_x", "_y"),
auto_index = FALSE,
...,
sql_on = NULL
)
# S3 method for class 'tbl_spark'
full_join(
x,
y,
by = NULL,
copy = FALSE,
suffix = c("_x", "_y"),
auto_index = FALSE,
...,
sql_on = NULL
)Arguments
- x, y
A pair of lazy data frames backed by database queries.
- by
A join specification created with
join_by(), or a character vector of variables to join by.If
NULL, the default,*_join()will perform a natural join, using all variables in common acrossxandy. A message lists the variables so that you can check they're correct; suppress the message by supplyingbyexplicitly.To join on different variables between
xandy, use ajoin_by()specification. For example,join_by(a == b)will matchx$atoy$b.To join by multiple variables, use a
join_by()specification with multiple expressions. For example,join_by(a == b, c == d)will matchx$atoy$bandx$ctoy$d. If the column names are the same betweenxandy, you can shorten this by listing only the variable names, likejoin_by(a, c).join_by()can also be used to perform inequality, rolling, and overlap joins. See the documentation at ?join_by for details on these types of joins.For simple equality joins, you can alternatively specify a character vector of variable names to join by. For example,
by = c("a", "b")joinsx$atoy$aandx$btoy$b. If variable names differ betweenxandy, use a named character vector likeby = c("x_a" = "y_a", "x_b" = "y_b").To perform a cross-join, generating all combinations of
xandy, seecross_join().- copy
If
xandyare not from the same data source, andcopyisTRUE, thenywill be copied into a temporary table in same database asx.*_join()will automatically runANALYZEon the created table in the hope that this will make you queries as efficient as possible by giving more data to the query planner.This allows you to join tables across srcs, but it's potentially expensive operation so you must opt into it.
- suffix
If there are non-joined duplicate variables in
xandy, these suffixes will be added to the output to disambiguate them. Should be a character vector of length 2.- auto_index
if
copyisTRUE, automatically create indices for the variables inby. This may speed up the join if there are matching indexes inx.- ...
Other parameters passed onto methods.
- sql_on
A custom join predicate as an SQL expression. Usually joins use column equality, but you can perform more complex queries by supply
sql_onwhich should be a SQL expression that usesLHSandRHSaliases to refer to the left-hand side or right-hand side of the join respectively.