fix(webhdfs): fix WebHDFS provider to handle requests without Range header#90
Conversation
|
This contribution has received funding from the Spanish government (grant EQC2021-007479-P, funded by MCIN/AEI/10.13039/501100011033), the EU NextGeneration/PRTR (PRTR-C17.I1), and the Generalitat de Catalunya. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #90 +/- ##
==========================================
+ Coverage 75.79% 76.02% +0.22%
==========================================
Files 26 26
Lines 3772 3774 +2
==========================================
+ Hits 2859 2869 +10
+ Misses 913 905 -8 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
It would be really useful if you could create a new release including these two WebHDFS fixes: Thank you! |
|
please fix:
|
Okay, no problem. |
|
All set on my side, should be good now. |
|
These error alerts seriously interfere with other people's development tests, please fix pytest error: |
|
All the warnings related to the WebHDFS provider have been addressed. |
still... try |
4fd2c30 to
fcd503c
Compare
|
All the warnings have been addressed. |
Checklist
changelog.en.mdif necessary? Don't forget to add your name and github profile link!Description
This PR fixes the WebHDFS provider to correctly handle requests without a Range header.
Previously, if a request did not include the Range header, the provider would raise an exception when range support was enabled. This breaks the expected behavior where a request without a Range should download the entire file.
With this change, the WebHDFS provider:
fixes #88