Product Updates

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.

Coalesce Not Affected by Global CrowdStrike Outage

by Coalesce
Announcement

The global IT issues caused by CrowdStrike while widespread are not currently affecting Coalesce's systems. Coalesce does utilize CrowdStrike but this issue is isolated and not affecting our production cloud infrastructure. We are continuously monitoring our systems and are available via support for any questions.

Version 7.3.8

by Coalesce
New
Updates

Role-Based Access Control

We are excited to announce the upcoming launch of Role-based Access Control (RBAC) on our platform, a new feature designed to enhance security and provide more granular access controls within our environment.

Role-based Access Control (RBAC) is a method of restricting system access to authorized users based on their role within an organization.

RBAC is currently in private preview and is available only upon request. To enable RBAC for your organization, please contact the Coalesce support team. We appreciate your feedback and look forward to enhancing this feature based on your insights during this phase.

Review our RBAC documentation to learn more.

Updates

We’ve updated our Merge Conflicts workflow. Now you can clearly see which lines need to be reviewed, move between each conflict easily, and can decide to keep or reject changes with the click of a button.

Take a look at our Merge Conflicts documentation.

Documentation

Some new documentation we’ve added includes:

Find Us Online




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



Dhaulagiri 7.0.16 Release

by Coalesce
New
Updates
Bug Fix

We've rolled out our new release, Dhaulagiri 7.0.0. This release focuses on making the platform faster and more reliable.

What's New

CLI

CLI option to set Coalesce domain, making it easier for PrivateLink and Non-U.S. based customers to configure coawithout needing to set environment variables.

Config file example

[default]
domain=your deployment server. For example, https://app.eu.coalescesoftware.io
token=yourtoken
snowflakeAuthType=Basic or KeyPair
...

CLI Example

$ coa --domain="your deployment server" refresh

Learn more in CLI Setup.

SSO (Single Sign-On)

We now support the same SSO user logging into multiple orgs.

Updates

  • We made some minor UI improvements to:

    • User and Org settings

    • Node Type menu

    • User Credentials form

    • Node failure in a Workspace, now shows the node name instead of the node ID.

  • The Node Graph is easier to navigate because of improvements to zooming and panning.

  • YAML validation was improved by preventing invalid metadata from being checked out.

  • Storage Mappings alert users if they aren't authorized for the database or if the database doesn't exist.

  • If an unauthenticated user tries to visit a link that requires authentication, they'll be redirected to the login page. After logging in, they'll be taken back to the page they were trying to visit.

  • Hidden or enableIf=false config items don't show up in documentation anymore.

  • Override Create SQL in View Node now adds double quotes to column names.

Bug Fixes

  • Get Job Status endpoint succeeds for Workspace runs when launched from the API.

  • Bulk editing only hash columns now succeeds.

  • Fixed issue with coa CLI not working behind some network proxies.

Documentation

We've made a lot of changes to our documentation.

Organization

We've organized the documentation so you can find the content where you need it. If you're working on Building Your Pipeline or Deploying Your Pipeline, you can find the content you need.

New Content

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

Feedback

Let us know what you think of the changes by taking our documentation survey.

Find us online

v6.2.8 Cho Oyu

by Coalesce
New
Bug Fix

What’s New

  • Coalesce now supports Ping Identity for SSO.

Bug Fixes

  • Fixed an issue involving XML parsing.

  • This release includes performance improvements around Runs and multisource nodes.

  • Minor UI fixe

{error_message}

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

Thanks for your feedback!

v6.2.2 Cho Oyu

by Coalesce
New
  • Fixed a problem that caused deployments to fail.

  • Git Resync branch for off-platform changes was failing. This has been fixed.

  • We fixed a bug that caused the Docs to crash sometimes.

{error_message}

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

Thanks for your feedback!

v6.2.0 Cho Oyu

by Coalesce
New
Bug Fix

What’s New

  • New Generated Documentation has arrived! You can read more about this feature on our documentation page here.

  • Coalesce runs can now be cancelled via CLI, API, and in the UI. You can read more about this feature here.

  • There's now an endpoint for querying single runs, more details here.

  • SQL in Run Results pages can now be displayed as formatted or raw via toggle, in both the Build and Deploy tabs.

  • Tabs in the Build section of the application can now be reordered via drag and drop.

  • Many smaller UI changes to improve the user experience.

Bug Fixes

  • Improved functionality of Force Checkout in git modal to be more resilient.

  • Fixed a bug when implementing columnDropdownSelector object in UDNs.

  • Fixed a bug that could occur if a user clicked the Run button repeatedly within a node.

  • Improved error messaging when using invalid characters for Storage Mapping names.

  • Fixed off-by-one drag and drop behavior that could occur in Nodes' column mapping grids.

  • Fixed a transient and misleading 404 error that would sometimes appear when connecting to Snowflake via OAuth.

  • When creating a new branch, your list of changes will now appropriately be reflected in the git modal.

  • Fixed a Snowflake privileges bug that could occur when using default Deployment Strategy.

  • Clicking View Column Lineage now automatically opens the relevant tab.

  • Improved performance when duplicating Development Workspaces and bulk editing Nodes.

  • Many smaller bug fixes to improve the speed and reliability of the application.

{error_message}

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

Thanks for your feedback!