-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
Single partition fix #183
Single partition fix #183
Conversation
In the case where data is partitioned, and the upmost partition only has one possible value, we have no clear way to know that it is meant as a partition rather than a location if passed a list of paths. As a workaround, provide extra parameter to ParquetFile (and merge) to specify where the dataset root is.
@yackoa , can you test against your s3 data, please? You would do
|
@martindurant would this work for multiple leaf partitions as well ?
|
Yes indeed it should - it skips the inference of the root of the data-set in favour of the value provided. |
which means |
Yes, that is the idea. |
awesome !!! I reckon the The reason is that I have some programs working with the previous version (worked around with using is it |
Yes, you are correct for how to revert. This fix is not in conda-forge yet. |
I have been using conda for testing this on my work related EC2 machine where everything. It would be easy for me to test this in my work environment, since everything is already setup. That's why I had asked for the conda vesrion. I can PIP install in my local if needed. but would need sometime to get my dependencies in order, since currently my local and work machine is out of sync. |
Fixes #182