메뉴
Generate column-level lineage for a specific task
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Manage GizmoSQL processes: start, stop, list, and stop-all DuckLake-backed SQL servers
Create or modify database connections in application.sl.yml
Manage Quack DuckDB query servers exposing DuckLake over a thin remote protocol — serve (foreground), start/stop/list/stop-all (background)
Automatically infer schemas and load data from the incoming directory
Data quality expectations syntax, built-in macros, and validation patterns
Apply Row Level Security (RLS) and Column Level Security (CLS) policies
| name | col-lineage |
| description | Generate column-level lineage for a specific task |
Generates column-level lineage for a specific transform task, showing how each output column traces back to its source columns through SQL transformations. This provides fine-grained data provenance information.
starlake col-lineage [options]
--task <value>: Task name in the form domain.task (required)--output <value>: Output JSON file path (default: console output)--accessToken <value>: Access token for authentication (e.g. GCP)--reportFormat <value>: Report output format: console, json, or htmlAnalyzes the SQL query for a task and traces each output column back to its source columns. For example, given:
-- metadata/transform/kpi/revenue_summary.sql
SELECT
o.order_id,
o.timestamp AS order_date,
SUM(ol.quantity * ol.sale_price) AS total_revenue
FROM
starbake.orders o
JOIN starbake.order_lines ol ON o.order_id = ol.order_id
GROUP BY
o.order_id, o.timestamp
The column lineage output would show:
order_id ← starbake.orders.order_idorder_date ← starbake.orders.timestamptotal_revenue ← starbake.order_lines.quantity, starbake.order_lines.sale_pricestarlake col-lineage --task kpi.revenue_summary
starlake col-lineage --task kpi.order_summary --output col_lineage.json
starlake col-lineage --task kpi.revenue_summary --accessToken $GCP_TOKEN