Spurious warnings about many-to-many joins about dplyr HOT 5 CLOSED

@tomwagstaff-opml thanks for trying it out on your computer too!

Since there currently isn't anything actionable on our end, I am going to close this. But we do want to help, so please feel free to open another issue if you can find a reproducible example that isn't working as expected, thanks!

from dplyr.

What version of dplyr are you using? This got dramatically less annoying with dplyr 1.1.1

this hasn't been explicitly noted

There are many NEWS bullets about this

In our testing this has been working as expected, so we would need a full reprex at this point to see if anything is wrong

from dplyr.

I'm using dplyr 1.1.3

When I say not explicitly noted, I mean by setting the relationship parameter within the join function.

As I said, I'm afraid I can't share the example I'm working on - I've just traced through the examples and found they are in fact unique matches.

from dplyr.

There is nothing I can do without an example, sorry.

It seems to be working as expected, i.e. the comment "the second column(s) to match on are being ignored when the warning is generated" does not appear to be true for me.

library(dplyr)

x <- tibble(
  a = c(1, 1, 2, 2),
  b = c(1, 2, 3, 4)
)

left_join(x, x, join_by(a, b))
#> # A tibble: 4 × 2
#>       a     b
#>   <dbl> <dbl>
#> 1     1     1
#> 2     1     2
#> 3     2     3
#> 4     2     4

^{Created on 2023-11-22 with reprex v2.0.2}

from dplyr.

I'm afraid I can't reproduce it with a trivial example either. This is closer to my situation, but runs fine:

x <- tibble(
  a = c(1, 1, 2, 2),
  b = c(1, 2, 1, 2)
)

y <- rename(x, c = b)

inner_join(x, y, by = c("a", "b" = "c"))

Hopefully someone in a position to share their data and code will turn up the same issue.

from dplyr.