-
Notifications
You must be signed in to change notification settings - Fork 608
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
Channel join loses duplicate keys #654
Comments
Yes, currently it's indeed as a inner join. Using |
Would it be possible to get options for specifying the other types of joins? |
It should be possible. |
I have a problem with
This is given that X and Y are files. Not sure if that is the reason. From the second operation I would have expected: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
If I have a pipeline like this:
The output looks like this:
instead of like this:
When joining in this case,
Sample4
exists twice in the paired channel, and the second one is lost at the second join.My current workaround is here: https://github.com/stevekm/nextflow-demos/blob/253b8e3ea8547d88f571e7c718e34696cf5b9be1/join-pairs/main.nf
However it is very cumbersome. I think this might be resolved by having the options for 'left outer join', 'right outer join', or 'full outer join', since it appears that only an inner join is being used.
The text was updated successfully, but these errors were encountered: