Maintaining clear and consistent documentation across pipelines is always a challenge. Coalesce makes it effortless by automatically generating natural language descriptions from your lineage and transformation metadata to create:
Node & Column Descriptions: Auto-generated, easy-to-understand explanations of column transformations, logic, and business context — no more manual notes or guesswork. AI-Generated Git Commit Messages: Helpful, context-aware commit messages to keep your Git history clean, descriptive, and useful.
Benefits
How It Helps:
Reduce Documentation Overhead: Free up time for development while Coalesce handles the docs.
Maintain Consistency: Ensure standardized documentation across all data projects, teams, and environments.
Improve Stakeholder Clarity: Make it easier for business users and analysts to understand transformation logic.
Accelerate Onboarding: Help new team members ramp up faster with auto-generated, clean documentation.
How to Opt-In
AI Features not enabled by default in Coalesce. Organization admins can opt-in to the AI Documentation Assistant by going to Org Settings > Preferences and toggling AI Features.
AI-Generated Documentation: Automatic Descriptions for Nodes, Columns, and Git Commit Messages
These features are currently in Private Preview. Please reach out to your Coalesce account manager to sign up.
Coalesce is introducing AI-generated descriptions for Node, Columns, and Git Commit messages.
By analyzing your data pipelines lineage and transformation metadata, it creates natural language descriptions. AI-generated descriptions streamlines documentation by creating clear explanations of data transformations and Git commits. Now you can focus on development while making sure your data pipelines are well documented.
Organization admins can opt-in by going to Organization Settings > Preferences and toggling AI Features.
Updates
Run results, Column Headers now support numeric names, ensuring your data displays accurately.
We've temporarily rolled back Workspace Onboarding based on valuable customer feedback. This change was made to ensure the best customer experience possible. We're working on improvements to deliver a refined version in the future. Sign up for our changelog email to keep to date.
Bug Fixes
We fixed an issue where, when switching tabs in multi-source Nodes the incorrect join string was saved.