Product Updates

Version 7.4.4

by Coalesce
Updates
Action Required

Updates

This release includes performance improvements and bug fixes.


🛑Action Required🛑

Git Repo Format Upgrade must be completed by September 5, 2024.

On September 5, 2024, Coalesce will enable the Git Repo Format Upgrade for all existing customers.

As part of the upgrade, you’ll need to upgrade your CLI and enable the Git Repo Format Upgrade. Review our announcement to learn more.

We're excited to announce that Role-Based Access Control (RBAC) will be enabled for all Coalesce users on September 5, 2024.

RBAC enhances security by ensuring that users have only the access they need, reducing risks and simplifying permission management.

Organizations will be automatically upgraded on September 5, 2024, but if you'd like early access, please reach out to our support team. Take a look at our documentation to get started.

Review our RBAC Migration Guide to understand how these changes will affect your organization.

Version 7.4.3

by Coalesce
New
Action Required
Updates

🛑Action Required🛑

Git Repo Format Upgrade must be completed by September 5, 2024.

On September 5, 2024, Coalesce will enable the Git Repo Format Upgrade for all existing customers.

As part of the upgrade, you’ll need to upgrade your CLI and enable the Git Repo Format Upgrade. Review our announcement to learn more.


We’ve released Version 7.4.3

New

Edit Nodes API

We’ve released three new endpoints that allow you to manage Nodes in your Workspaces.

  • List Nodes - Returns a list of all the Nodes in a Workspace.

  • Get Node - Returns information about a single Node.

  • Set Node - Edit existing Nodes in a Workspace.

Refresh Jobs

You can now run existing Jobs in the Coalesce App. 


Updates

  • We’ve updated our Git integration to better handle sync and validation errors.

  • We’ve improved the speed of the Build page for large data pipelines.

Bug Fixes

  • We fixed a bug where you couldn’t clear multiple sources using the Bulk Editor.

  • We fixed an issue where users received an error about uncommitted changes when updating from the remote repository, despite not making any changes.

  • We fixed a bug where not all tables were available when adding a source.

  • We fixed an issue where Docs were slow to open.

  • We fixed a bug where Node descriptions that were null wouldn't deploy.

Find Us Online


Upgrade Your Git Repo

by Coalesce
Action Required

On September 5, 2024, Coalesce will enable the Git Repo Format Upgrade . After September 5, 2024, all Git repos will be automatically updated.

What is the Git Repo Format Upgrade?

We have updated the way files are committed into Git. Previously it was split into a data.yml and the specific nodes.yml files. Now you can see the changes for:

  • Node Types

  • Environment Mappings

  • Subgraphs

  • Jobs

  • Macros

  • Packages

The upgrade is required for Packages and CLI use.

How to Opt-In

Organization Administrators can turn it on for the whole organization. Go to Org Settings > Preferences and Enable Git Repository Format Update. Once enabled, all Workspace users will be prompted to switch to the new format. They won't be able to make commits until they switch to the new format.

  • Users will be notified the upgrade is available, but won't be able to upgrade.

  • Previously committed metadata can still be deployed after the upgrade.

Packages

You must be using the new Git Repo Format Upgrade to use Coalesce Packages.

CLI

If you use the CLI and HAVE NOT upgraded to the new Git Repo Format, you have until September 5, 2024 to upgrade your CLI. After September 5, 2024, the Git Repo Format Upgrade will be turned on for all Coalesce organizations and any CLI versions below 7.0.18 won't be compatible with Coalesce versions 7.2.x and above.

If you have upgraded to the new Git Repo Format and use the Coalesce CLI, please upgrade your CLI version to prevent interruptions in workflow.

Dhaulagiri 7.2.7

by Coalesce
New
Action Required
Updates
Bug Fix

Coalesce Packages

We're excited to launch Coalesce Packages!

Packages are curated collections of node types that make it faster to build data projects in a sustainable and standardized way. Use packages to streamline your development by removing repetitive work and focusing more on your data.

Data teams can choose from a variety of Packages that are designed to:

  • Speed up foundational development activities with basic, ready-made node types for Work, Dimension, Fact, and View tables.

  • Maximize the power of Snowflake innovation with support for Dynamic Tables, Streams & Tasks, Materialized Views, Snowflake Cortex ML-based functions, external data loading with Snowpark, and more.

  • Streamline work on methodology-related initiatives such as building a Data Vault.

Accelerate AI- and ML-focused innovation with custom node types to operationalize anomaly detection, forecasting, sentiment analysis, and more in Snowflake data pipelines.

Read our documentation on Packages to get started.

Browse the Coalesce Marketplace for available packages.

Git Repo Format Upgrade

We have updated the way files are committed into Git. Previously it was split into a data.yml and the specific nodes.yml files. Now you can see the changes for:

  • Node Types

  • Environment Mappings

  • Subgraphs

  • Jobs

  • Macros

  • Packages

How to Opt-In

Organization Administrators can turn it on for the whole organization. Go to Org Settings > Preferences and Enable Git Repository Format Update. Once enabled, all Workspace users will be prompted to switch to the new format. They won't be able to make commits until they switch to the new format.

  • Users will be notified the upgrade is available, but will not be able to upgrade.

  • Previously committed metadata can still be deployed after the upgrade.

Learn more about what gets committed in What Gets Committed.

🛑Action Required🛑

Git Repo Format Upgrade

Git Repo Format Upgrade is opt-in until August 1, 2024. After August 1, 2024, all Git repos will be automatically updated.

Coalesce CLI

Upgrade your Coalesce CLI to version 7.0.18. Versions below 7.0.18 will not be compatible with Coalesce version 7.2.x and above.

If you use the CLI and HAVE NOT upgraded to the new Git Repo Format, you have until August 1, 2024 to upgrade your CLI. After August 1, 2024, the Git Repo Format Upgrade will be turned on for all Coalesce organizations and any CLI versions below 7.0.18 will not be compatible with Coalesce versions 7.2.x and above.

If you have upgraded to the new Git Repo Format and use the Coalesce CLI, please upgrade your CLI version to prevent interruptions in workflow.


Updates

We’ve made our Git integration even better. 

  • Improvements to the Force Checkout screen so it's easier to understand what happens in a force checkout.

  • Checking out branches has improved. With easier to understand messages and clearer understanding of what happens to commits when changing branches.

  • Added two columns for Used by Workspace and Deployed In Environment so you know where your commits are being used and deployed.

  • The Git Modal header now shows your current branch, current commit, and if you have any uncommitted changes.

  • Merging branches provides better feedback.

Take a look at our revamped Git Integration documentation.

Bug Fixes

  • Fixed an issue where business keys were being duplicated when the column was copied.

  • Fixed an issue where the Create and Run buttons were removed from User-Defined Nodes.

  • Fixed an issue where the table description would show in the column documentation.

  • Fixed an issue where the Node name is cut off when viewing the Column Lineage.

  • Fixed an issue where during deployment, if the table already exists in Snowflake and a node is deployed with a matching name , but different data, then the table is dropped and re-created during deployment. Now, during deployment, the table is cloned and temporary columns are created.

  • Fixed an issue where certain Multi-source View nodes that were changed from UNION to UNION ALL were not recognized during the deployment.

  • Fixed an issue where dragging columns into the Mapping Grid was sometimes unavailable.

  • Fixed an issue where new Environments configured with Key Pair authentication would not be able to use the Storage Mapping screen.

Documentation

There's a lot of new content to help you use Coalesce.

Find Us Online



CLI Version Deprecation

by Coalesce
Action Required
{error_message}

Leave your name and email so that we can reply to you (both fields are optional):

Thanks for your feedback!