DataIngestionReadyState
Used only as output after a readiness check. In case of 'not ready', the ready property is set to 'false' and the object contains a cause with code and message.
{
"ready": false,
"cause": {
"code": "INR1001",
"message": "The data set is currently being processed"
}
}
Causes consist of a code and a message to indicate why exactly the data set is not ready. The code is four digits long and always prefixed with "INR" for "Ingestion - Not Ready". A list with the concrete codes and the semantics can be found in the table below.
Code | Semantic |
|---|---|
INR1000 | Undefined. Used for unexpected situations. |
INR1001 | Data set in process. The referenced data set is locked by another process (data ingestion cycle, manual data load, etc.). The user must wait until the locked is lifted and repeat the request. |
INR1002 | Living process quota exceeded. Usage of the data ingestion API is limited to data sets with a 'living process' license. The assigned 'living process' license defines an upper bound (process quota) for the number of process instances within the corresponding data set. Code INR1002 indicates that the process quota defined by the assigned 'living process' license is already exceeded and it is not allowed to ingest more data. The user can reduce the number of process instances within the dataset by deleting process instances or alternatively assign a 'living process' license with a higher process quota. |
INR1003 | Unexpected source table type. Indicates that at least one of the referenced source tables has an unexpected type, for example, was created via the CSV upload. To use a table in the context of the data ingestion API, it either needs to have been created by that API or updated by it via the replace source table functionality. |
INR1004 | No data to load. Indicates that there is no new pending data for the tables referenced in the data modeling section. Therefore a data load is not necessary. |