Draft
feat: add NB_FMD_PURVIEW_LINEAGE_TABLE_COLUMN for standalone column-level Purview lineage#241
Conversation
Copilot
AI
changed the title
feat: add NB_FMD_PURVIEW_LINEAGE_TABLE_COLUMN notebook for column-level Purview lineage
feat: add NB_FMD_PURVIEW_LINEAGE_TABLE_COLUMN for standalone column-level Purview lineage
Jul 3, 2026
Copilot created this pull request from a session on behalf of
edkreuk
July 3, 2026 17:47
View session
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a dedicated notebook for registering column-level lineage in Microsoft Purview, decoupled from the parallel orchestration notebook. The core addition is dual-mode schema resolution: columns can be read from either a registered Delta table in the attached lakehouse (
"table") or any readable path — Delta, Parquet, or CSV — via an explicit ABFSS URI or lakehouse-relative path ("path").New notebook:
NB_FMD_PURVIEW_LINEAGE_TABLE_COLUMNSchema resolution (
source_type/target_typeper side):"table"spark.read.format("delta").load("Tables/{schema}/{table}")"path"spark.read.format(fmt).load(path)— delta / parquet / csvPurview Atlas entities registered per call:
azure_datalake_gen2_resource_setwithonelake://{workspace_guid}/{lakehouse_name}/{schema}/{table}qualified namesProcessentity carryingcolumnMapping(case-insensitive column-name match) enabling column-level lineage in the Purview catalog graphExit value — JSON summary (
purview_status,mapped_columns,total_runtime) so the notebook is callable from pipelines or orchestration notebooks with inspectable results.