-
Notifications
You must be signed in to change notification settings - Fork 837
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
Improve parquet MetadataFetch
and AsyncFileReader
docs
#6505
Conversation
/// Return a future that fetches the specified range of bytes asynchronously | ||
/// | ||
/// Note the returned type is a boxed future, often created by | ||
/// [FutureExt::boxed]. See the trait documentation for an example |
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.
If you are not familiar with rust futures BoxFuture
is somewhat exotic. I will also make a PR upstream in futures to try and improve the docs there
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.
rust-lang/futures-rs#2887 -- we'll see what the maintainers say
MetadataFetch
and AsyncFileReader
docs
Co-authored-by: Matthijs Brobbel <[email protected]>
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.
Looks good to me. 👍 @mbrobbel found the only issues I did.
Co-authored-by: Matthijs Brobbel <[email protected]>
Co-authored-by: Val Lorentz <[email protected]>
Co-authored-by: Val Lorentz <[email protected]>
Thank you everyone for your suggestions and support. |
Which issue does this PR close?
Part of #6504
Rationale for this change
While working on the example for using parquet metadata in a local cache (#6081) some of these traits and how to implement them were not clear to me
What changes are included in this PR?
Add additional documentation and explanations
Are there any user-facing changes?
Better documentation and examples. No functional changes