Remove PyArrow version upper bound and update lockfile#2262
Merged
kevinjqliu merged 2 commits intoapache:mainfrom Jul 30, 2025
Merged
Remove PyArrow version upper bound and update lockfile#2262kevinjqliu merged 2 commits intoapache:mainfrom
kevinjqliu merged 2 commits intoapache:mainfrom
Conversation
3 tasks
kevinjqliu
approved these changes
Jul 30, 2025
Contributor
kevinjqliu
left a comment
kevinjqliu
left a comment
There was a problem hiding this comment.
LGTM We dont need to restrict pyarrows upperbound, this also allows end users to try out newer releases of pyarrow
Contributor
Author
|
I just fixed an error with |
kevinjqliu
reviewed
Jul 30, 2025
| ports: | ||
| - 10000:10000 | ||
| command: ["azurite-blob", "--loose", "--blobHost", "0.0.0.0"] | ||
| command: ["azurite-blob", "--loose", "--skipApiVersionCheck", "--blobHost", "0.0.0.0"] |
Contributor
There was a problem hiding this comment.
Contributor
|
thank you @ehsantn |
gabeiglio
pushed a commit
to Netflix/iceberg-python
that referenced
this pull request
Aug 13, 2025
<!-- Thanks for opening a pull request! --> As title. Closes apache#2258. Updated the lockfile just in case but it didn't change the Arrow version. <!-- In the case this PR will resolve an issue, please replace ${GITHUB_ISSUE_ID} below with the actual Github issue id. --> <!-- Closes #${GITHUB_ISSUE_ID} --> # Rationale for this change PyIceberg doesn't need this upper bound since it uses stable public APIs of PyArrow (as far as I can tell). Dependency version upper bounds are known to be problematic: 1. Cause cascading dependency conflicts 2. Block security and bug fixes 3. Limit user flexibility In my case, this causes issues for Bodo's Arrow upgrades since both Arrow and PyIceberg are dependencies. # Are these changes tested? Existing tests. # Are there any user-facing changes? <!-- In the case of user-facing changes, please add the changelog label. --> None except allowing newer PyArrow versions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As title. Closes #2258. Updated the lockfile just in case but it didn't change the Arrow version.
Rationale for this change
PyIceberg doesn't need this upper bound since it uses stable public APIs of PyArrow (as far as I can tell).
Dependency version upper bounds are known to be problematic:
In my case, this causes issues for Bodo's Arrow upgrades since both Arrow and PyIceberg are dependencies.
Are these changes tested?
Existing tests.
Are there any user-facing changes?
None except allowing newer PyArrow versions.