This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.
✅ What you built
A new column in your passenger Ontology dataset to serve as a more expressive title key for your Ontology object type.
A streamlined flight alerts Ontology dataset that removes an unnecessary column.
Updated table registrations for your passenger and flight alert object types to account for these changes.
✅ What you learned
Additive changes to the backing dataset do not interfere with the Phonograph synchronization process.
Phonograph does not automatically accept schema changes, and so you'll need to handle them manually by updating the property mapping and Phonograph table registration.
The Job Tracker application provides detailed messages about any Phonograph sync errors.
To process a deleted column from a backing dataset, you should unmap the property, save the Ontology, and update the table registration in OMA.
To process a schema change on an existing mapped column, you should change the data type in the column mapping configuration, save the Ontology, and update the table registration in OMA.
The Foundry documentation contains instructions for processing schema changes on columns that have received writeback edits.