After updating a feed configuration (such as removing a column or changing a field’s data type), existing data stored in the source domain table must be updated to match the new shape. Previously, Amperity would force a truncation of the domain table and purge the existing data.

Now instead of requiring a full reload of the data, you can kick off a schema migration workflow after a feed update to resolve any mismatches between the existing domain data and the new feed configuration. This job generally takes just a few minutes and hopefully will save lots of headache by avoid a forced historical load! Try it out by enabling feature flag "Feed Migrations"!

This capability is available in preview - if you are interested in trying it out, let us know. We expet to release it in the coming weeks.