-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-40142: [Python] Allow FileInfo instances to be passed to dataset init #40143
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
GH-40142: [Python] Allow FileInfo instances to be passed to dataset init #40143
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
|
|
cb03e28 to
dbdc9e2
Compare
|
the appveyor build seems to have timed out while compiling |
|
@jorisvandenbossche can I ask you to take a look at this? |
jorisvandenbossche
left a comment
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, sounds as a useful addition, and looks good!
|
Thank you! |
|
After merging your PR, Conbench analyzed the 7 benchmarking runs that have been run so far on merge-commit c57115d. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
Rationale for this change
Closes #40142
I'm developing a new dask integration with pyarrow parquet reader (see dask/dask-expr#882) and want to rely on the pyarrow Filesystem more.
Right now, we are performing a list operation ourselves to get all touched files and I would like to pass the retrieved
FileInfoobjects directly to the dataset constructor. This API is already exposed in C++ and this PR is adding the necessary python bindings.The benefit of this is that there is API is that it cuts the need to perform additional HEAD requests to a remote storage.
This came up in #38389 (comment) and there's been related work already with #37857
What changes are included in this PR?
Python bindings for the
DatasetFactoryconstructor that accepts a list/vector ofFileInfoobjects.Are these changes tested?
I slightly modified the minio test setup such that the prometheus endpoint is exposed. This can be used to assert that there hasn't been any HEAD requests.I ended up removing this again since parsing the response is a bit brittle.Are there any user-facing changes?
FileInfoobjects #40142