Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@kevinjqliu
Copy link
Contributor

@kevinjqliu kevinjqliu commented Feb 25, 2025

Closes #1721

Otherwise, there's a default behavior change in new 0.9.0 release. Previous versions will write to data/, new version will write to data/<hash>/

@kevinjqliu kevinjqliu requested a review from Fokko February 25, 2025 22:00
Copy link
Contributor

@Fokko Fokko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this @kevinjqliu.

I think it would be good to add this to 0.9.0

@Fokko Fokko added this to the PyIceberg 0.9.0 milestone Feb 25, 2025
@kevinjqliu kevinjqliu merged commit 1d24e71 into apache:main Feb 25, 2025
7 checks passed
@kevinjqliu
Copy link
Contributor Author

reverts #1509, cc @smaheshwar-pltr

@kevinjqliu kevinjqliu deleted the kevinjqliu/location-provider branch February 25, 2025 22:40
@smaheshwar-pltr
Copy link
Contributor

Thanks for the ping @kevinjqliu.

(Feel free to respond later) Curious what the problem here was. I'd have thought that old tables would still be readable by new PyIceberg and old PyIceberg would still be able to read tables created by the new one. Is changing locations just too dramatic for this release?

@Fokko's #1452 (comment) that prompted this still seems reasonable (maybe longer-term), or is it not?

@kevinjqliu
Copy link
Contributor Author

Is changing locations just too dramatic for this release?

My main concern was around the default behavior change. For example, if i had a pipeline running with 0.8.1 and now i upgrade to 0.9.0. The data file location is suddenly changed to use the hashed path. We can add it to the release notes, but i think changing the default behavior will surprise some users.

@smaheshwar-pltr
Copy link
Contributor

Thanks @kevinjqliu for the explanation.
I said something similar in #1509 (comment) / #1509 (comment) so agreed!

@kevinjqliu
Copy link
Contributor Author

:) Sorry for the back and forth!
Another thing is that having data/ as the default data location is more friendly to new users.

kevinjqliu pushed a commit that referenced this pull request Feb 26, 2025
Update the docs to reflect the simple location provider as the default
location provider.

related to #1721, and #1722.
gabeiglio pushed a commit to Netflix/iceberg-python that referenced this pull request Aug 13, 2025
Closes apache#1721

Otherwise, there's a default behavior change in new 0.9.0 release.
Previous versions will write to `data/`, new version will write to
`data/<hash>/`
gabeiglio pushed a commit to Netflix/iceberg-python that referenced this pull request Aug 13, 2025
Update the docs to reflect the simple location provider as the default
location provider.

related to apache#1721, and apache#1722.
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.

turn ObjectStoreLocationProvider off by default

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.