This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.
We recommend installing a schema check on all inputs to your pipeline and optionally (if you know the expected update frequency) the TSLU check. On all outputs (i.e., targets) of your build schedule, you should include at least a TSLU and schema check.
As you proceed, recall that you have three connected units of build, each with their own configured schedules:
flight_alerts_clean
, all the way to your generated and multi-output transforms (if you're following the "Builder" path, this means your filtered country and priority datasets). Remember to add all nodes upstream, too.*_json_raw
and *_csv_raw
input datasets to your Passengers schedule do not expect a particular schema due to the nature of the transform. Instead, consider placing the schema checks at the preprocessed stage for each.If you're following the "Builder" path, you may not have preprocessed Passenger datasets, and you may safely skip this step.
Tips: