Join two vectra tables
Usage
left_join(
x,
y,
by = NULL,
suffix = c(".x", ".y"),
na_matches = c("na", "never"),
...
)
inner_join(
x,
y,
by = NULL,
suffix = c(".x", ".y"),
na_matches = c("na", "never"),
...
)
right_join(
x,
y,
by = NULL,
suffix = c(".x", ".y"),
na_matches = c("na", "never"),
...
)
full_join(
x,
y,
by = NULL,
suffix = c(".x", ".y"),
na_matches = c("na", "never"),
...
)
semi_join(x, y, by = NULL, na_matches = c("na", "never"), ...)
anti_join(x, y, by = NULL, na_matches = c("na", "never"), ...)Arguments
- x
A
vectra_nodeobject (left table).- y
A
vectra_nodeobject (right table).- by
A character vector of column names to join by, or a named vector like
c("a" = "b").NULLfor natural join (common columns).- suffix
A character vector of length 2 for disambiguating non-key columns with the same name (default
c(".x", ".y")).- na_matches
How to match
NAkeys:"na"(default, as in dplyr) treatsNAas matchingNA;"never"uses SQL semantics whereNAnever matches.- ...
Ignored.
Details
All joins use a build-right, probe-left hash join. The entire right-side table is materialized into a hash table; left-side batches stream through. Memory cost is proportional to the right-side table size.
By default NA keys match NA (dplyr's na_matches = "na"); pass
na_matches = "never" for SQL NULL semantics. Key types are auto-coerced
following the bool < int64 < double hierarchy. Joining string against
numeric keys is an error.