v3.4 - Kanchenjunga Patch 4 - Bug Fixes
Posted by Alex Engelmann 3 days ago
- Previously, the node type editor had developed a distracting text overflow issue. That has been fixed now.
- Clearing your search from the source cascader no longer throws an error.
- Pagination for Job history now works as expected.
- Improved issues with git versions
- Improved column lineage calculation
- Fixed a bug where column propagation would not create a new column correctly
- Fixed performance issues with the source select dropdown
- We tweaked many other issues as well
v3.4 - Kanchenjunga Patch 4 - What's New
Posted by Alex Engelmann 3 days ago
- You can now use profiles to set frequently used configurations in the coa command-line interface.
- Key pair authentication is now available for coa CLI.
- Override Snowflake authentication parameters via API and CLI.
- Viewing a node ID for a node is just a hover away.
- Run node refreshes via CLI selector syntax (limited support).
fixed
v3.3 - Kanchenjunga Patch 3 - Bug Fixes
Posted by Greg Henkhaus 2 months ago
- "Validate Run All" from the graph actually ran the nodes rather than appending the SQL with
EXPLAIN
. This is now working as expected.
added
v3.3 - Kanchenjunga Patch 3 - What's New
Posted by Greg Henkhaus 2 months ago
- Ability to set read-only variables (Parameters) that can be accessed via node templates. Parameters can be set to control the behavior of nodes during development and deploy time via the GUI interface. CLI and API options are coming soon which will allow the user to set parameters during both refresh and deploy.
- SSO Authentication to Coalesce via Azure Active Directory
- Improved switcher to change the view of Node and Column browser between Graph, Node Grid, and Column Grid
- Improved the "Something went wrong" page when Coalesce encounters a bug. Errors are automatically sent to an on-call engineer for an investigation to improve our product continually.
- Ability to execute multiple jobs at the same time in a given environment
- Deleting columns now presents the user with an option to abort the action. We have observed that very few users use the propagate deletion flow when deleting a column from the grid. To kick off deletion propagation, you must now do this from the Column Lineage interface.
- Various minor improvements to make the app better!
fixed
v3.2 - Kanchenjunga Patch 2 - Bug Fixes
Posted by Greg Henkhaus 3 months ago
- Inside of the node mapping grid, we now alphabetically sort all items in the source selector.
added
v3.2 - Kanchenjunga Patch 2 - What's New
Posted by Greg Henkhaus 3 months ago
- We are excited to release multi-branch git support to our customers! You can now check out older versions of your data pipelines, branch for new feature development or implement a hotfix, merge in changes, and handle merge conflicts—all from within the app!
- Run status now displayed in Node grid to have a tabular view of what is running in your DAG.
- Introduction of Column-level grid to browse all columns in your DAG. Currently, this feature is read-only...but exciting things are to come!
fixed
v3.1.1 - Kanchenjunga Patch 1 Hotfix - Bug Fixes
Posted by Greg Henkhaus 4 months ago
- Improved general app performance
- Addressed a bug that prevented hash column metadata from upgrading to the new format when a node is opened. Please contact support if you are still experiencing issues.
fixed
v3.1 - Kanchenjunga Patch 1 - Bug Fixes
Posted by Alex Engelmann 4 months ago
- Addressed an issue where only the first
{{ stage() }}
in the create template would execute on a deployment
added
v3.1 - Kanchenjunga Patch 1 - What's New
Posted by Alex Engelmann 4 months ago
- Coalesce Command Line Interface (coa) is now available via npm. You can read more details here.
- We redesigned our interface for assigning columns to hash columns. Now the order of these columns can be explicitly set.
- Coalesce no longer pre-fetches data previews during "Run All"
- General improvements to the UX and internal logging
fixed
v3.0 - Kanchenjunga - Bug Fixes
Posted by Shruthi Pillaipakkam 5 months ago
- Previously, the syntax for the SHA256 hash generator algorithm was incorrect. Now it’s fixed.
- Writing a join condition caused the text to flicker sometimes. Typing in the Join field is now flicker-free.
- Minor improvements in general. Hopefully, the app should be even better for everyone.