Skip to content
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

Compatibility break on joins #66

Closed
CedricFR opened this issue Aug 29, 2018 · 2 comments
Closed

Compatibility break on joins #66

CedricFR opened this issue Aug 29, 2018 · 2 comments

Comments

@CedricFR
Copy link
Contributor

CedricFR commented Aug 29, 2018

Hi,

The latest modifications to the join functions are breaking some usage code.

The incriminated changes are: bbe03e8...17b3440

The problem is this case:

df >> left_join(df2, by=["column1", "column2", "column3"])

It used to mean "merge based on those 3 columns", but now it means "merge based on column1 for left dataframe, and column2 on the right dataframe", which is quite different!

What's the rationale? Is it because we're now supposed to use tuples and not lists in those cases?

Either way, if we decide this is the way forward, it should be a major version change because it breaks one of the major use cases of dfply. What do you think?

@kieferk
Copy link
Owner

kieferk commented Aug 29, 2018

That's my fault. I changed it to fix another issue and didn't think about what the change implied in enough detail before pushing the change.

I'm at work now but I'll revert this tonight and come up with a way to fix the other issue a different way.

Sorry about that!

@kieferk
Copy link
Owner

kieferk commented Aug 30, 2018

OK hopefully the current push to master will resolve the issue. Let me know if not, obviously. Sorry for the inconvenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants