col-lineage

Generates column-level lineage across tasks as JSON for metadata systems.

209|30|Updated Sep 18, 2021
One-click install
npx skills add https://github.com/starlake-ai/starlake --skill col-lineage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: col-lineage
Source: https://github.com/starlake-ai/starlake/tree/main/.agent/skills/col-lineage
Command: npx skills add https://github.com/starlake-ai/starlake --skill col-lineage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Column-level lineage generation to track how data flows and transforms across tasks, enabling governance and impact analysis.

Core Features & Use Cases

  • Generate column-level lineage to trace dependencies from source to target columns across tasks.
  • Use for data governance, impact analysis, and debugging of data pipelines.
  • Use Case: Identify downstream effects when a source column is modified to propagate changes accurately.

Quick Start

Execute the command to generate column lineage for a specified task, for example starlake col-lineage --task <task_name>.

Frequently Asked Questions about col-lineage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is column-level data lineage and why do I need it for data governance?

Column-level data lineage tracks how data flows and transforms from source to target columns across tasks. You need it for data governance, impact analysis, and debugging data pipelines to accurately propagate downstream changes when a source column is modified.

How do I generate column lineage for a specific task?

To generate column lineage for a specific task, execute the command starlake col-lineage --task <task_name>. This traces dependencies from source to transform across tasks and produces a structured lineage output for your specified task.

Does column lineage extraction produce output compatible with existing metadata systems?

Yes, column lineage extraction produces a structured lineage in JSON format. This JSON output is designed for seamless integration with existing data governance workflows and metadata systems.

Can I trace end-to-end data dependencies across multiple tasks for impact analysis?

Yes, you can trace end-to-end data dependencies across tasks to perform impact analysis. The lineage extraction identifies and maps source to target column transformations, enabling you to see downstream effects accurately.

What is the best way to analyze downstream effects when modifying a source column in a data pipeline?

The best way to analyze downstream effects is by generating column-level lineage. It traces dependencies across tasks to identify exactly which target columns are affected, ensuring accurate change propagation and pipeline debugging.