Subscribe to updatesDeprecated node metadata changes were completed with the release of 7.15.
Previous posts
March 13, 2025 - Upcoming Deprecated Node Metadata Changes
March 3, 2025 - Deprecated Node Metadata Changes
In our ongoing efforts to enhance performance and maintainability, we're removing some legacy metadata fields that are no longer needed.
This process is happening in two stages:
Release 7.14 - Already completed ✅
Release 7.15 - Coming soonCompleted on March 18, 2025 ✅.
What this means for you:
No workflows will be disrupted.
No data will be affected.
When doing a commit, you might see changes for Nodes that you haven’t modified. This is expected when deprecated metadata is removed. You will need to:
Making a commit with the changes.
Continue on with your workflow.
Example of a commit with metadata changes
Deprecated Properties Removed:
Deprecated fields in 7.15 will affect all Source Node Types regardless of age or activity status. These fields may still appear in our API, but are no longer used in the Node metadata.
dataset
table
metadata.join
metadata.sourceMapping - already absent from most sources
See our previous changelog post about the changes in 7.14.
Coalesce cleaning up deprecated metadata fields in Nodes. The change will improve data integrity across Coalesce. This will happen in two stages:
Release 7.14
Release 7.15
When doing a commit, you might see changes for Nodes that you haven’t modified. This is expected while deprecated metadata is removed. We suggest making a commit with the changes then continuing on with your workflow. Do not delete, edit, or modify the deprecated fields in any way.
Deprecated fields in 7.14 will primarily affect older workspaces that haven't been accessed recently. For actively maintained workspaces, the impact should be minimal. However, if you attempt to commit against previously archived or long-dormant workspaces, you may encounter these changes.
Deprecated Properties Removed
The following properties will be completely removed if present:
Top-level column properties:
ghostRecordValue
descendedFrom
hashColumns
columnsForHash
Inside hashDetails object:
hashType
hubHashes
Properties corrected for Invalid Data
Properties set to empty string (""):
dataType - if not a string type
transform - if empty
Properties completely removed if invalid
appliedColumnTests - if null
config - if null
hashDetails - if it's a string (should be an object)
Column Reference Fixes
Column Reference (columnReference)
stepCounter - if null/undefined, set to the node's ID
All IDs within column references are converted to strings (previously numbers were allowed - this change has been around for a long time)
Source Column References (sourceColumnReferences)
For each reference in the array:
All IDs within column references are converted to strings
stepCounter - if null/undefined, set to empty string ("")
Hashed Columns Fixes
For hashedColumns array:
All IDs within column references are converted to strings
Deprecated fields in 7.15 will affect all Source Node Types regardless of age or activity status.
Deprecated Properties Removed:
dataset
table
metadata.join
metadata.sourceMapping - already absent from most sources
Coalesce will be taking a scheduled maintenance window. During this time, search functionality within the generated documentation pages will be temporarily unavailable.
Maintenance Details:
• Date: Monday, February 17, 2025
• Time: 8:00 PM - 10:00 PM US/Pacific
We are performing this maintenance to enhance the stability and performance of our platform. We expect search services to be fully restored by 10:00 PM PST, but will notify users if there are any delays or updates.
The rest of the platform will remain fully operational during this time.
We appreciate your understanding and apologize for any inconvenience this may cause. If you have any questions or concerns, please feel free to reach out to our support team.
Command line users on version 7.5.8 or below should upgrade to coa version 7.10.2 immediately.
Users on`coa` version 7.5.8 and below may encounter deployment and refresh errors. The issue occurs with the presence of`platformKind:snowflake` in the data.yml.
To fix any critical deployment or refresh issues:
Upgrade to coa version 7.10.2 as soon as possible to prevent further issues.
If you are unable to upgrade your coa version and need to deploy immediately:
Check your commits for platformKind:snowflake in the data.yml file.
Manually remove the platformKind:snowflake and commit the changes.
Deploy as normal
We are working on a change to be delivered within the next 24 hours to allow backwards compatibility for older versions of coa as to not disrupt operations.
On September 5, 2024, Coalesce will begin enabling two upgrades for all organizations.
Git Repo Format Upgradeis available now. Mandatory upgrades will start September 5, 2024 and expect to be complete by September 12, 2024.
We encourage you to prepare for the changes by:
Upgrade the CLI to the latest version.
Have your organization's administrators enable the Git Repo Format Upgrade before the mandatory deadline.
Optionally, contact support to enable the RBAC migration early.
Review existing roles and understand the permissions they will have under the new system.
By preparing for these changes early, you can avoid unintended consequences, such as being unable to make commits until the upgrade is complete.
We encourage you to review our documentation for more details:
Contact our support team to start preparing.
This release includes performance improvements and bug fixes.
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.
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
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.
You can now run existing Jobs in the Coalesce App.
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.
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
On September 5, 2024, Coalesce will enable the Git Repo Format Upgrade . After September 5, 2024, all Git repos will be automatically updated.
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.
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.
You must be using the new Git Repo Format Upgrade to use Coalesce Packages.
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.