-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Port CRAN's fuzzyjoin Funtions to dplyr #3293
Comments
Thanks. Are you suggesting to run the fuzzy join directly on the database? |
Either in database or in R itself. However, when you query a SQL database I guess you could always do a cheat like this I guess:
|
fuzzyjoin seems to be removed from CRAN, are you aware of a successor? |
At the company where I work we have GitHub Webpage Blocked, and I cannot check properly this issue. The point is that if the package has been removed from CRAN, there is even more reason to fork some of its functions (as they are) and move them to mainstream dplyr. I checked them out in the past and they are properly written. The fuzzyjoin GitHub Repository is at the following link: https://github.com/dgrtwo/fuzzyjoin I'll check it out when I arrive at home, though these days I am little busy learning the H2O.ai framework, and doing a couple of Cheatsheets for using its machine learning functions. Juan |
The fuzzyjoin package indeed seems not to be longer actively maintained. |
Just released a new version on CRAN today: |
Good to see it back. Will think about it in the context of #2240. |
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
I would suggest porting some of CRAN's fuzzyjoin package functions to dplyr (With proper Contribution Acknowledgement):
https://cran.r-project.org/web/packages/fuzzyjoin/index.html
Of special interest is "fuzzy_join" function, which allows to do SQL queries such as these:
The text was updated successfully, but these errors were encountered: