Replies: 3 comments
-
The file looks like to be served compressed and with a header of "content-encoding: gzip" (independently of the request). Here I believe for duckdb to behave correctly in NOT sending "Accept-Header" headers in the request and NOT expecting content to arrive compressed. Workarounds are, for now, either fetching and feeding the file to duckdb externally OR set up (possibly via proxy) headers correctly in the remote resource. |
Beta Was this translation helpful? Give feedback.
-
Thank you for that clear explanation. It is logical indeed, as it happens also frequently for random servers to behave this way. |
Beta Was this translation helpful? Give feedback.
-
Hi @ericemc3 thanks for opening this issue. The problem is indeed what @carlopi is describing. Two comments:
|
Beta Was this translation helpful? Give feedback.
-
What happens?
I can't read a remote Json file, but it is ok if it is read locally.
To Reproduce
If i store first the result from https://statistiques-locales.insee.fr/GC_refdata.php?nivgeo=com_courant&extent=fe&lang=fr -> com.json
FROM read_json('com.json') ;
Ok
OS:
Win11
DuckDB Version:
10.0.3
DuckDB Client:
DuckDB cli
Full Name:
eric mauviere
Affiliation:
icem7
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
Not applicable - the reproduction does not require a data set
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
Beta Was this translation helpful? Give feedback.
All reactions