coltrace 0.1.0.dev8__tar.gz → 0.1.0.dev9__tar.gz

{coltrace-0.1.0.dev8/src/coltrace.egg-info → coltrace-0.1.0.dev9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coltrace
-Version: 0.1.0.dev8
+Version: 0.1.0.dev9
 Summary: Static Pandas column lineage, impact analysis, and local dependency graphs
 Author: Cristiano Diniz
 License-Expression: MIT
@@ -32,7 +32,7 @@ column versions across direct function calls. Static scanning never imports or
 executes the project or reads its input data. Optional read capture observes
 column labels while you explicitly execute your own pipeline.
 
-**Development preview: `0.1.0.dev8`.** The supported subset is deliberately small.
+**Development preview: `0.1.0.dev9`.** The supported subset is deliberately small.
 Unsupported operations produce diagnostics and may interrupt lineage. A graph
 with no edge is not proof that a dependency does not exist.
 
@@ -65,6 +65,9 @@ Query filters are control metadata rather than value dependencies of every
 output. `spark.sql(build_query(table)).toPandas()` keeps its SQL text even with
 an injected, unresolved session; SQL assembled from f-strings, `.format`, `%`
 and joins keeps its known text, with unknown parts shown as `{expression}`.
+`SELECT *`, `UNION`, tables read by name (`spark.table`, Snowpark
+`session.table`, `dbt.ref`) and SQL files read inside the project are modeled
+too; see [extraction architectures](docs/extraction-architectures.md).
 
 `report.readers` inventories resolved `pd.read_*` calls with file, line, context,
 return shape and resulting DataFrame identity. File schemas are unknown unless