Closed jrhizor closed 2 years ago
Hi everyone. I came across this potential issue and I am responding here to Jared's questions from Papercups.
Here are the details of the endpoint: URL: https://data.egov.bg/api/getResourceData body: {"resource_uri" : "e59f95dd-afde-43af-83c8-ea2916badd19"} headers: {"Accept-Charset":"utf-8"} (did a lot of trial and error here - was not working with {"Content-Type": "application/json"}) http_method: POST
The source data can be seen at this URL: https://data.egov.bg/data/resourceView/e59f95dd-afde-43af-83c8-ea2916badd19
The response contains a UTF-8 entities - maybe this is the probelem? The response can be generated by executing in ubuntu:
curl -X POST https://data.egov.bg/api/getResourceData -H "Content-Type: application/json" -d "{\"resource_uri\" : \"e59f95dd-afde-43af-83c8-ea2916badd19\"}"
Any help is appreciated.
Thanks @crunchtoinfo, this is enough information to reproduce on our end.
@cgardens:
There are two problems here. First, I think the "data" field hack is causing a problem. The raw table created is called just _airbyte_raw_data
with no actual value. I think this is why normalization is failing.
Secondly, the actual call should be able to support {"Content-Type": "application/json"}
as it works with curl
. It definitely does look like an encoding issue.
Closing this because HTTP Source is deprecated
Postgres normalization failing after a successful sync from the HTTP endpoint.
┆Issue is synchronized with this Asana task by Unito