Skip to content

Remove deprecated OBJECT_STORE_PATH and WRITE_FOLDER_STORAGE_LOCATION - #12174

Closed
Fokko wants to merge 4 commits into
apache:mainfrom
Fokko:fd-remove-deprecated-stuff
Closed

Remove deprecated OBJECT_STORE_PATH and WRITE_FOLDER_STORAGE_LOCATION #12174
Fokko wants to merge 4 commits into
apache:mainfrom
Fokko:fd-remove-deprecated-stuff

Conversation

@Fokko

@FokkoFokko commented Feb 4, 2025

Copy link
Copy Markdown
Contributor

I was digging into this for PyIceberg, this has been deprecated since 0.12.0

@singhpk234singhpk234 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

[Minor] Looks like we wanna drop OBJECT_STORE_PATH and WRITE_FOLDER_STORAGE_LOCATION rather than PR heading
WRITE_METADATA_LOCATION and WRITE_FOLDER_STORAGE_LOCATION

+1 for removing !

Comment on lines -140 to +137
dataLocation = properties.get(TableProperties.OBJECT_STORE_PATH);
if (dataLocation == null) {
dataLocation = properties.get(TableProperties.WRITE_FOLDER_STORAGE_LOCATION);
if (dataLocation == null) {
dataLocation = String.format("%s/data", tableLocation);
}
}
dataLocation = String.format("%s/data", tableLocation);

@dramaticllydramaticllyFeb 6, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I enjoy remove deprecated method or config but it's always a bit risky. From a iceberg user perspective, if I had a running iceberg data pipeline, I might not ever going to change/move away from deprecated one.

So in a worst case scenario for a given table with OBJECT_STORE_PATH or WRITE_FOLDER_STORAGE_LOCATION is set and its value is not equal to WRITE_DATA_LOCATION, shall we abort the write to force user action?

I think current logic is ignoring the old table properties and directly write into default, I think it might be reasonable but want to know if this is intended. Maybe we can raise the awareness on dev list about the change?

@FokkoFokkoFeb 17, 2025

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

It has been deprecated for quite a while, but I'm happy to send out an email on the dev list.

And yes, there is some risk involved if you don't import the TableProperties.{OBJECT_STORE_PATH,WRITE_FOLDER_STORAGE_LOCATION}. This way you don't see the deprecation, and your code will still compile after the removal of the property. Let's hear what others think.

@kevinjqliukevinjqliu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM, also +1'ed on devlist.

I double checked usage and reference by using github search and confirmed that its not used.
Previous PRs (#3094 & #2965) also supports removal.

@FokkoFokko changed the title Remove deprecated WRITE_METADATA_LOCATION and WRITE_FOLDER_STORAGE_LOCATIONRemove deprecated OBJECT_STORE_PATH and WRITE_FOLDER_STORAGE_LOCATION Feb 18, 2025
@Fokko

Copy link
Copy Markdown
ContributorAuthor

Closing this one in favor of #12315

@FokkoFokko closed this Feb 24, 2025
@Fokko
Fokko deleted the fd-remove-deprecated-stuff branch April 9, 2025 22:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@Fokko@dramaticlly@kevinjqliu@singhpk234