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

Patch Release 0.7.1 #1031

Closed
wants to merge 11 commits into from
Closed

Patch Release 0.7.1 #1031

wants to merge 11 commits into from

Conversation

sungwy
Copy link
Collaborator

@sungwy sungwy commented Aug 9, 2024

No description provided.

ndrluis and others added 11 commits August 9, 2024 12:56
* Fix: accept empty arrays in struct field lookup

Fixes #992.

Empty `pyarrow` arrays are considered falsy, which caused a `ResolveError` for required fields during scan operations.

* Integration test: empty scan on non-nullable ordered string column

This covers the issue reported in #992 where empty scan queries yielded a `ResolveError`. Specifically, this occurred under the following conditions:
- a table with an ordered, non-nullable string column
- a scan filtering for a non-existing value _within_ the range of the values in that particular column

* Lint (add missing newline)
* Exclude Python 3.9.7 due to import error in catalog module

Adjusts the supported Python versions to exclude 3.9.7, as importing the
catalog module on this version results in an unexpected error.
The issue does not occur in versions 3.9.6 or 3.9.8, indicating a specific
incompatibility with Python 3.9.7.

* Update pyproject.toml

Co-authored-by: Kevin Liu <[email protected]>

---------

Co-authored-by: Kevin Liu <[email protected]>
* Allow setting `write.parquet.row-group-limit`

And update the docs

* Add test

* Make ruff happy

---------

Co-authored-by: Sung Yun <[email protected]>
@sungwy sungwy requested a review from Fokko August 9, 2024 13:53
@Fokko
Copy link
Contributor

Fokko commented Aug 9, 2024

@sungwy Looks good! I'm also okay with just cherry-picking these directly on the branch. All the commits are good because they have already been merged. I think a PR makes sense when you have a lot of merge conflicts that need to be resolved.

@sungwy
Copy link
Collaborator Author

sungwy commented Aug 9, 2024

I'll get that done. Thank you for the input @Fokko

@sungwy sungwy closed this Aug 9, 2024
@sungwy
Copy link
Collaborator Author

sungwy commented Aug 9, 2024

Done - I'll start the release process on https://github.com/apache/iceberg-python/tree/pyiceberg-0.7.x

@Fokko Fokko deleted the sy-pyiceberg-0.7.1 branch August 9, 2024 19:40
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.

5 participants