For Audience based datasets, some MAIDs may be rejected by the ingestion process, and this information can be found within the status files in the S3 bucket after ingestion. This file shows the number of lines that were rejected, alongside a reason for why they did not pass through the ingestion process. The most common reason for this is due to the UUIDs being ‘malformed’ and not what we consider to be a MAID.
x lines were processed, in which y errors occurred.
Note that only up to 10000 error messages and 1000 malformed device ids were printed out.
Remaining lines were processed successfully.
More information on what is classed as a MAID can be found here.
The same principle goes for Proximity datasets as well. The onboarding results are written to the .fail file.
Onboarding result:
- status : WARNING
- start time : 2022-01-27T12:59:51.994189Z
- end time : 2022-01-27T12:59:53.203815Z
- duration : 1.21 seconds
Onboarding metrics:
- total file rows : 8963
- total datasets : 1
- total geometries : 8957
- total geometry references : 8957
- total rows with errors : 0
- total errors : 0
- total rows with warnings : 6
- total warnings : 12
- total missing geoIds : 0
Datasets geometry assignments:
- geo_id : 8957