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

0.8 Patch Release for Arrow 19 Support #1672

Open
srilman opened this issue Feb 17, 2025 · 3 comments
Open

0.8 Patch Release for Arrow 19 Support #1672

srilman opened this issue Feb 17, 2025 · 3 comments

Comments

@srilman
Copy link
Contributor

srilman commented Feb 17, 2025

Hi! At Bodo, we've been working on replacing our Iceberg connector backend with PyIceberg (bodo-ai/Bodo#235). It's been going great so far, but we noticed that the latest 0.8.1 release of PyIceberg doesn't support PyArrow 19. That's kind of frustrating because we had already started to do the Arrow 19 upgrade (bodo-ai/Bodo#240) because it comes with SAS token support for their AzureFileSystem, which is really important for Snowflake I/O.

It looks like 0.8.1 itself was released to add support for Python 3.13 along with other stuff, so I was wondering if we could do the same thing again: release a 0.8.2 loosing the PyArrow constraint. Does that sound reasonable? From my understanding, the 0.9.0 is potentially around the corner, but I don't know how long the release process takes for minor releases in comparison to this.

Happy to help in any way, since it's a a bit of a blocker on our side.

@srilman srilman changed the title 0.8 Patch Release for Arrow 19 Supoort 0.8 Patch Release for Arrow 19 Support Feb 17, 2025
@kevinjqliu
Copy link
Contributor

hey @srilman i just started a thread for 0.9.0 release https://lists.apache.org/thread/rr8lcf96jl6079dz6vfkwr5spbvlxzpm

as for PyArrow 19, the current constraint in pyproject.toml is

pyarrow = { version = ">=17.0.0,<20.0.0", optional = true }

which should cover Arrow 19.

@srilman
Copy link
Contributor Author

srilman commented Feb 17, 2025

@kevinjqliu That's great, missed that. How long does the release process usually take? Looks like last time there was about a 11 day difference between the first rc and the release. Is it expected to be similar?

@kevinjqliu
Copy link
Contributor

most likely. we have to go through the process to create a release candidate, have it verified by the community, and when it passes, push the final artifacts to pypi and svn.

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