-
Notifications
You must be signed in to change notification settings - Fork 150
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
Ensure that RestCatalog passes user config to FileIO #476
Merged
liurenjie1024
merged 2 commits into
apache:main
from
sdd:fix-rest-catalog-file-io-config-bug
Aug 20, 2024
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -504,8 +504,15 @@ impl Catalog for RestCatalog { | |
.query::<LoadTableResponse, ErrorResponse, OK>(request) | ||
.await?; | ||
|
||
let config = resp | ||
.config | ||
.unwrap_or_default() | ||
.into_iter() | ||
.chain(self.user_config.props.clone().into_iter()) | ||
.collect(); | ||
|
||
let file_io = self | ||
.load_file_io(resp.metadata_location.as_deref(), resp.config) | ||
.load_file_io(resp.metadata_location.as_deref(), Some(config)) | ||
.await?; | ||
|
||
let table = Table::builder() | ||
|
@@ -542,8 +549,15 @@ impl Catalog for RestCatalog { | |
.query::<LoadTableResponse, ErrorResponse, OK>(request) | ||
.await?; | ||
|
||
let config = resp | ||
.config | ||
.unwrap_or_default() | ||
.into_iter() | ||
.chain(self.user_config.props.clone().into_iter()) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ditto. |
||
.collect(); | ||
|
||
let file_io = self | ||
.load_file_io(resp.metadata_location.as_deref(), resp.config) | ||
.load_file_io(resp.metadata_location.as_deref(), Some(config)) | ||
.await?; | ||
|
||
let table_builder = Table::builder() | ||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the order is reversed compared with java implementaion:
https://github.com/apache/iceberg/blob/63af974efe51486c89bff8df5416781ab3181976/core/src/main/java/org/apache/iceberg/rest/RESTSessionCatalog.java#L942
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But if it was that way around, you could not use the local user_config to override a property that came from the REST service? I think we would want the ability to do that. I think it makes more sense the way around that I have it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think both two methods have pros and cons.
If we prioritize user config, we get max flexibility, but also would be easy to introduce bugs. For example, what if user misconfiged some fileio property which should be managed by rest catalog?
Also, the rest catalog spec 's statement make me feel that we should repsect rest catalog's response.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My rationale behind this was so that users could override values from the REST config. For instance if you wanted to try out using an S3 proxy / cache by overriding the value of the S3 warehouse endpoint. I can change it if you insist, but that would reduce the usefulness of this change in my eyes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds like a reasonable case for me. cc @Xuanwo @Fokko what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a strong preference for this but respecting the user's override seems sensible to me. We can mention its behavior in the API comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added some doc comments to the two relevant methods to clarify the behaviour. Hope this helps.