Coming October 15, 2024: Transitioning all data mart customers to relational schema

To improve and streamline our services, Zus will retire non-relational data mart schemas on October 15, 2024. This change will transition all customers to the new, more usable and performant relational schema.

Changes to different schemas

A Zus data mart customer today can have up to three different schemas available to them:

• [CUSTOMER_NAME]: The Zus legacy schema, available to select customers - will be retired on October 15, 2024
• [CUSTOMER_NAME]_STAGING: The Zus preview relational schema, available to select customers - will be retired on October 15, 2024
• [CUSTOMER_NAME]_RELATIONAL: The Zus relational schema, generally available to all customers - will continue to be supported through future versioning

For more information on the features on the relational schema and how to access it, please refer to our changelog post introducing the relational schema.

What this means for customers

To ensure a smooth transition, we recommend the following steps during the transition period:

1. Familiarize yourself with the relational schema: Review the updated documentation to understand the enhancements and changes.
2. Test the relational schema: Use your development or testing environments to ensure you have access to the relational schema.
3. Update your systems: Modify any scripts, integrations, or workflows that rely on the legacy schemas to be compatible with the relational schema.

If you encounter any issues or have questions during the transition, our support team is available to assist you. Please reach out to us at [email protected].

Future of versioning of data marts

Zus will update the relational schema to keep up with customer needs and data quality best practices, but will ensure that changes to an existing version of the schema are non-breaking.

If breaking changes are needed, they will be introduced in a new schema version. Each version will be supported for a minimum of 9 months, and customers will be given at least 60 days to transition to a new version once it is made generally available. Zus reserves the right to introduce a breaking change without notice if it impacts an unused feature of the data mart.

Stay tuned for updates and detailed release notes with each new version. We are committed to providing the best experience and ensuring seamless transitions.

❓

What is a breaking change?

A breaking change in a data mart schema disrupts existing functionality or requires users to alter how they interact with the data mart. These changes can impact data querying, processing, or interpretation, necessitating adjustments to reports, dashboards, or applications relying on the schema.

Examples of breaking changes include:

• Schema modifications:
  • Changing the name of an existing column or table
  • Removing an existing table or column
• Data type changes: Altering the data type of an existing column (e.g., from integer to string)
• Constraint changes:
  • Modifying or removing primary keys
  • Modifying or removing foreign key relationships
  • Adding or removing unique constraints

Note: Adding a column or table or reordering existing columns within a table does not constitute a breaking change.