Feature: Write to branches
Fixes: https://github.com/apache/iceberg-python/issues/306
@sungwy @kevinjqliu This PR is ready for review
Fixed another bug. Writes with same name but different ref types were being successful. This is a bug in the current release version too
Please review whenever you get some time.
Thanks for the contribution! I'll take a look. I remember adding support for branch is complicated since we need to consider different edge cases.
I have mostly tried to cover all edge cases. The idea is that the branch is just another iceberg table where the snapshots append independently of the main branch.
I also agree with your concern. If it helps, we can add more test cases
Hey @kevinjqliu Did you get a chance to look at this?
Thank you for the review @kevinjqliu
@kevinjqliu What are the next steps to get this merged?
cc @HonahX / @Fokko / @sungwy
@vinjai coming back to this after the 0.8.1 release :) Feel free to tag me again once the comments above are addressed. Thanks again for the contribution!
hey @vinjai are you interested to pick this back up?
Hey @kevinjqliu I was traveling for the past two months and couldn’t complete the review comments. I’ll be back in a week, will address the comments then, and get this moving.
thank you! @vinjai feel free to tag me again for review :)
Hey @kevinjqliu I have resolved all comments. Will resolve the merge conflicts once you have gone through these changes (to avoid rework).
Let me know once you have reviewed the above comments
Hey @kevinjqliu Did you get a chance to look at the PR again?
Hi, just wondering if there is an update on this PR?
Hey @kevinjqliu Bumping up for review
Thanks @dbuades for pinging me, and sorry for letting this one linger for so long. Let me review this tomorrow morning.
@vinjai Do you have time to resolve the conflicts by any chance?
Hey @Fokko Will try to resolve the conflicts over the weekend.
Hey @vinjai, did you get a chance to fix those conflicts? 🙂
@vinjai I fixed the conflicts on this branch, feel free to cherry pick the last commit https://github.com/apache/iceberg-python/pull/2009 Otherwise I can open a PR on my side and take it from there 🙂
Thanks @SebastienN15 — I’ll review your commit and take it forward from there. I’ll share the working PR tomorrow.
Identified and fixed a bug related to empty tables. Planning to add test cases to cover this scenario.
Hey @Fokko This PR is ready for review again
Hey @Fokko I noticed that the integration tests for Python 3.9 are failing. Possibly, a runtime issue:
ServerError: NoSuchBucketException: The specified bucket does not exist (Service: S3, Status Code: 404, Request ID: 18436A88DE8BCC82, Extended Request ID: dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8) (SDK Attempt Count: 1)
I ran the same tests locally with Python 3.9.6, and they passed without issues. Is there any change required in the PR to resolve the above failure?
@vinjai Thanks for pinging me. The issue has been fixed in https://github.com/apache/iceberg-python/pull/2049. Locally, you're still using an older version of minio, and therefore the tests pass. Could you pull in the latest main branch to fix the CI? Thanks!
Hey @Fokko I've pulled the latest changes from the main branch. Please re-trigger the workflow.
@vinjai I'm sorry, can you resolve the conflicts once more? I'll merge right after
Hey @vinjai, would you be able to resolve the conflicts? I would love to see this PR merged 🙏
Hey @Fokko I have resolved all conflicts and merged the recent changes. While running integration tests, I am facing this error for a few tests:
java.lang.IllegalStateException: Memory was leaked by query. Memory leaked: (360448)
Allocator(toArrowBatchIterator) 0/360448/360448/9223372036854775807 (res/actual/peak/limit)
The same error is coming on the main branch too.
Any idea on how to resolve this?
Hey @Fokko,
I tried the tests on a different machine. The tests are running fine. Request you to run the workflow and merge this PR ahead.
Thanks