Default Schema Names Are Here!

Our latest update introduces Materialization-Level Default Schemas and Materialization-Level Delta Updates Configuration, two features designed to simplify data flow setups and expand customization options.

Materialization-Level Default Schemas

Materializations into SQL-based destinations often require specifying schema names, which can be repetitive and error-prone for teams managing multiple pipelines. To address this, we’ve introduced default schemas at the materialization level, providing:

• Automatic Schema Assignment: Flow now assigns a default schema name for each materialization, based on the destination’s configuration and collection metadata.
• Custom Overrides: Users can still specify custom schema names if needed, but the default simplifies configuration for many use cases.

This feature reduces setup time and ensures consistency across pipelines, making Flow more intuitive for new and experienced users alike.

Materialization-Level Delta Updates Configuration

In this update, we also shipped a feature to allow users to configure delta updates on the materialization level.

With the increasing need to handle incremental changes efficiently, Flow now supports delta updates at the materialization level. This enhancement allows users to configure if all bindings in a Materialization should have delta updates enabled.

By enabling delta update configurations at the materialization level, users gain granular control over how changes are handled, expanding compatibility with various systems and reducing unnecessary data overhead.

Try It Today

Both features are now available in Estuary Flow.

If you have any questions, don't hesitate to send us a message in our Slack Community!