...
As previously outlined in the Ingesting Data via Endpoint section, using the process endpoint is one way of triggering the Lens to ingest your source data. When an execution of the Lens fails after being triggered in this way, the response will be a status 400 Bad Request as follows and contain a response message similar to that sent to the dead letter queue as outlined above.
| Code Block | ||
|---|---|---|
| ||
{
"codename": 400"RESTful-Lens",
"time":"2020-04-30T16:13:33.528",
"messagetype": "HTTP 400 Bad Request"RESTful-Lens",
"error":"Endpoint 'https://bitbucket.org/data-lens/datalens-examples/raw/error/restful-lens/example1/input/restful/json-api-no-data-array-page1.json' could not be processed due to: java.lang.NullPointerException",
"version":"1.1.0.0"
"provenance": "...[prov]..."
} |
RML
The RML endpoint is all about the mapping file that you created using the Mapping Config Web App. It consists of a GET and a PUT endpoint, allowing you to get the current master mapping file currently in use on the Lens, and well as replacing the master mapping file with a new one.
...