Merge pull request #154 from DataRecce/feature/drc-1059-update-doc-fo…

…r-udtf-of-breaking-change-analysis Remove the UDTF part
DataRecce · Feb 3, 2025 · cf3b4eb · cf3b4eb
2 parents 5c1e6fa + 7d7c82f
commit cf3b4eb
Showing 1 changed file with 0 additions and 5 deletions.
diff --git a/docs/docs/features/breaking-change-analysis.md b/docs/docs/features/breaking-change-analysis.md
@@ -39,11 +39,6 @@ The current implementation of breaking change analysis is still very conservativ
 1. Adding a `LEFT JOIN` to a table and selecting columns from it. This is often used to enrich the current model with additional dimension table data without affecting existing downstream tables.
 1. All modified python models or seeds are treated as breaking change.
 
-
-In some cases, breaking changes may be mistakenly identified as non-breaking changes, such as:
-
-1. Adding a new column can result in a table expansion effect, similar to the functionality of DuckDB's [unnest function](https://duckdb.org/docs/sql/query_syntax/unnest.html). The unnest function flattens lists or structs, potentially transforming a single upstream row into multiple downstream rows.
-
 ## Technology
 
 Breaking Change Analysis is powered by the SQL analysis and AST diff capabilities of [SQLGlot](https://github.com/tobymao/sqlglot) to  compare two SQL semantic trees.