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

feat(api): add positional joins #9533

Merged
merged 4 commits into from
Jul 15, 2024
Merged

Conversation

NickCrews
Copy link
Contributor

@NickCrews NickCrews commented Jul 6, 2024

closes #9486.

Add positional join to duckdb, pandas, and dask backends.

Amazingly simple to implement, a big cheers to the previous developers that made this code so clean and easy to edit!

By luck or magic, the pandas and dask backends seem to just work with no modification!

Should this be documented somewhere? I hesitate to clutter up the examples with this simple example. Really, I think the better thing that ibis really needs is a how-to guide on joining, where someone actually goes deep into the weeds and explains how things work.

@NickCrews NickCrews force-pushed the positional-join branch 2 times, most recently from d85bff3 to 9fc0ce7 Compare July 12, 2024 18:44
@cpcloud
Copy link
Member

cpcloud commented Jul 15, 2024

By luck or magic, the pandas and dask backends seem to just work with no modification!

Hm, CI seems to think otherwise 😅

@cpcloud cpcloud added this to the 9.2 milestone Jul 15, 2024
@cpcloud
Copy link
Member

cpcloud commented Jul 15, 2024

@jcrist @gforsyth Opinions on opening up the join API to how="positional"?

@gforsyth
Copy link
Member

They're a thing in at least DuckDB and polars, so it seems ok to enable them to me. I would push back against a top-level positional_join method, but I think adding it to how is alright.

@cpcloud cpcloud added ux User experience related issues pandas The pandas backend dask The Dask backend duckdb The DuckDB backend polars The polars backend labels Jul 15, 2024
@jcrist
Copy link
Member

jcrist commented Jul 15, 2024

They're a thing in at least DuckDB and polars, so it seems ok to enable them to me. I would push back against a top-level positional_join method, but I think adding it to how is alright.

Fully agree.

@cpcloud cpcloud changed the title feat: add positional joins feat(api): add positional joins Jul 15, 2024
@cpcloud cpcloud enabled auto-merge (squash) July 15, 2024 20:56
@cpcloud cpcloud merged commit 85ea9da into ibis-project:main Jul 15, 2024
83 checks passed
@NickCrews
Copy link
Contributor Author

Thank you all!

@coroa
Copy link
Contributor

coroa commented Jul 16, 2024

Just when I need it, thank you all!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dask The Dask backend duckdb The DuckDB backend pandas The pandas backend polars The polars backend ux User experience related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat: add how="positional" to Table.join()
5 participants