-
Notifications
You must be signed in to change notification settings - Fork 91
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
feat: Bump hive_metastore to use pure rust thrift impl volo
#174
Conversation
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.
Generally LGTM, thanks!
.address(address) | ||
// Framed thrift rpc is not enabled by default in HMS, we use | ||
// buffered instead. | ||
.make_codec(volo_thrift::codec::default::DefaultMakeCodec::buffered()) |
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.
Maybe it's better to make this a config?
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 agree we should make this setting available to users, though I believe it's a lower priority. I've created an issue at #188 to keep track of this.
} | ||
|
||
/// Format an io error into iceberg error. | ||
pub fn from_io_error(error: io::Error) -> Error { |
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.
io::Error
is a common error, how about moving it to core crate?
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'm not sure if moving to core and making it a public API is a good idea. What if we address this once we have the same from_io_error
in core?
cc @Xuanwo Any updates? |
cc @liurenjie1024, please review again. Sorry for the late. |
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.
LGTM, let's move!
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.
Thanks for the PR @Xuanwo and @liurenjie1024 for the review 🙌
Close #155