-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Corrects mapping of parent join_keys columns when merging 2 data frames #503
Conversation
Code Coverage Summary
Diff against main
Results for commit: a89a530 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Test Performance DifferenceAdditional test case details
Results for commit 727edbc ♻️ This comment has been updated with latest results. |
I didn't dive deep into the new changes so won't be of much help with the review. Although, I feel we might want to bump up the |
…efault (#1020) # Pull Request <!--- Replace `#nnn` with your issue link for reference. --> Fixes insightsengineering/teal.slice#502 Part of insightsengineering/teal.slice#503 and insightsengineering/teal.data#215 ### Changes - Corrects test to reflect behavior resulting from `teal.data` default parent setting when creating new `join_key`
Pull Request
Fixes #502 (and CI in
teal@main
)Context
A
join_key("d1", "d2", c("d1_k" = "d2_k"))
will create a symetrical relationship between "d1" and "d2", where "d1" is the parent of "d2".The key mapping is inverted for (d2, d1), where key is stored as
c("d2_k" = "d1_k")
.So when the join_key is being extracted (
jk[dataset_1, dataset_2]
), the key columns fordataset_1
("d2" in previous line) is obtained vianames()
, while the columns of dataset_2 are present in the values (unname()
)Changes description
teal.data::parents(..) <- ...
in favor of new behavior that defines this parent-child relationship injoin_key
constructornote: As far as I can see in the codebase, only
...DataFrames
use parent-child relationship