When a user updates a feed’s schema, 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.

With this product update, feed updates trigger a schema migration workflow to resolve any mismatches between the existing domain data and the new feed configuration. This workflow also occurs on sandbox promotion and pull.

Below is the list of feed updates that are supported by the schema migration workflow.

Below are feed updates that cannot run a schema migration job. In these scenarios, a truncation will be forced.

We’re improving our file-based ingestion process! By enhancing our courier configuration flow, we’re making data ingestion accessible to a broader, non-technical audience. Our old experience was time-consuming and required users to have technical expertise. This new experience delivers a new and improved first-class and easy-to-use customer experience, reducing the time required to onboard, explore, and configure new data sources in Amperity.

Our first launch of this updated courier experience, offers support for S3-based files only. We will continue iterating and improving as we add support for the remaining file-based systems. This new experience includes…

We look forward to rolling our support for additional file based, data warehouse, and API based connectors in the near future. Read more in our documentation.

Today we released a small quality of life improvement for those of you managing Feeds and Domain Tables. In the vast majority of cases, there is one feed per domain table, but in the past if you deleted either the feed or the domain table you had to remember to delete the matching item. Now deleting a domain table or feed will also delete the related feed or domain table, saving you time and preventing clutter in your tenant.

We've just completed work on a new experience for configuring Stitch. With the new experience we've made the most important settings more accessible and added in better descriptions and guidance. You can read more about configuring Stitch in our documentation.

We're excited to announce the new pairwise score inspector. This feature helps you understand how Stitch is clustering, by explaining the factors behind a pair's scoring.

In the tab of the , there are three new enhancements:

In addition, the tab of the has all this information as well. This feature should help you as you are working to understand why Stitch matched specific records and help with troubleshooting any issues.

We released a small change to show more precise row counts in orchestrations and campaigns. This should help you as you work to understand the specific details of rows being sent to different destinations.

Today we released an update to Amperity that introduces three important changes to the Notifications panel.

First, we've renamed to . This was done to more accurately describe what the panel’s real purpose, which is to show recent activity related to your work.

Second, we've removed ability to delete activity cards. We've heard from you that disappearing activities have historically caused confusion in understanding what happened within the system.

And last, we've put the panel inside of a collapsible side-bar, similar to what’s already in place within the query editor. This has been a long-standing request from all of you who wanted more space for your work without losing the ability to view the recent activity related to your task.

With this set of enhancements we believe we've addressed the feedback we've heard from you and freed up a lot more screen space for your work.

Recently we released an update to our SQL editor which is used throughout the platform. This upgrade use the Monaco Editor, the same core editor used by , and brings our editing experience up to par with industry standards.

It includes the following new capabilities:

And much more.

It’s available today in the query editor, the database table editor and the custom domain table editor.

Last month, we launched Sandbox Validations. These validations prevent you from promoting sandboxes until you address any outstanding errors.

One of these validations can result in a ‘schema mismatch’ error. This error occurs when a schema change is made to a feed/domain table that impacts the saved schema for a downstream database. To resolve this error and sync up the schema changes that were made upstream, you had to manually go into the downstream database table, click edit, and re-save the table,

Starting today, you can now automatically resolve schema mismatch errors with one click.

We've got more improvements on the way, including persisting check results so they don’t all disappear, adding more validations, and including more quick resolutions/suggestions.

We’re very excited to share that our workflow alerting now supports Slack. We realize that despite email’s ubiquity, not every customer wants to receive email alerts that then get filed into some folder and never looked at. Slack alerting gives us another communication channel for customers to integrate with their existing environments outside of Amperity.

This is now available from within the “Configure Alerts” dialog in the Workflow page. For more details, see our documentation.