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

Solving #293 #297

Closed
wants to merge 3 commits into from
Closed

Solving #293 #297

wants to merge 3 commits into from

Conversation

complyue
Copy link

@complyue complyue commented Mar 4, 2022

Attempt to solve #293, implementing Tables.partitions() for Arrow.Table turns out trivial enough, though I'm not clear what to do about companion test cases, documentation etc.

I'm lazy to have not excluded #296 from this PR, I'm open to draft another PR separated if you'd like, but the change set seems small, I hope you can have a quick look and decide what to do next.

@complyue complyue mentioned this pull request Mar 7, 2022
@complyue
Copy link
Author

complyue commented Mar 7, 2022

With an alternative solution #298, changes from #296 are removed from this PR, now it's only about Arrow.Table's Tables.partitions() implementation.

I suggest the commit history should be squashed, but don't have experience how to do that from my side, only seeing articles suggesting "Squash and merge" option of Github, but that seems only doable when merging a PR.

@quinnj
Copy link
Member

quinnj commented May 24, 2023

Sorry for never getting to review/support this. I agree the functionality is good and this was a good start. Instead of returning a tuple of tables, I opted for a more lazy approach of just defining a custom iterator + tests: #443

@quinnj quinnj closed this May 24, 2023
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

Successfully merging this pull request may close these issues.

2 participants