Skip to main content

Release Notes December 2022

Orchestrators​

Feature release status badge: Feature
Feature
Sharing Ingestion Tables between SOLE and MATE​

We have implemented a new feature to easily share ingestion table definitions between SOLE and MATE to avoid creating dbt sources manually. The benefits of this approach are:

  • Improved onboarding of new data sources
  • Shorter time to go live for new projects
  • No duplication of effort

See the autogenerate MATE dbt sources from SOLE-managed ingestion tables documentation for more information.

Feature release status badge: Feature
Feature
Enhancement of the QUERY_TAG Parameters​

  • For pipeline queries, we've added Project ID, Project Name, and Project Path in the QUERY_TAG parameters.

Feature release status badge: Bug Fix
Bug Fix
Bug Fixes in SOLE and Orchestrators​

  • Fixed the after parameter for Task - see updated documentation.

  • Updated the SOLE Table column default parameter to support additional data types such as float, integer, boolean, and null.

  • Updated SOLE to prevent job failure on changing authentication mode.

  • Updated the data retention implementation in SOLE Database and Schema:

    • Fixed a bug where value 0 for data_retention_time_in_days in Database was ignored.
    • Fixed a bug where value 0 for data_retention_days and false for is_managed in Schema were ignored.
    note

    If you have the data retention value set to 0 in your Database or Schema configuration, this value will start to be applied accordingly in Snowflake.

  • Updated catalog_title and catalog_id to add the database name as a prefix in Data.World.

    note

    Adding the database as a prefix in the catalog_id will create new catalogs. In case of the very unlikely scenario where the DataOps.live team would have to perform a rollback, the catalog_ids will be reverted.

Platform​

Feature release status badge: Improvement
Improvement
Runner Kubernetes PriorityClass Support​

We have added support for setting the Kubernetes PriorityClass on pipeline jobs running in a kubernetes cluster.

You can opt-in to use this new runner by using the image tag latest-next when installing or upgrading a runner.

For how to do this, see Run the DataOps Runner with Kubernetes.

Last updated on