Skip to content

[FAQ Bot] UPDATE: Why use a layered data pipeline (raw → canonical → analytics → mart) ins#265

Open
github-actions[bot] wants to merge 1 commit intomainfrom
faq-bot/issue-264
Open

[FAQ Bot] UPDATE: Why use a layered data pipeline (raw → canonical → analytics → mart) ins#265
github-actions[bot] wants to merge 1 commit intomainfrom
faq-bot/issue-264

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

📝 FAQ UPDATE

Course: data-engineering-zoomcamp
Section: module-3 (Expands the module-3 coverage to reflect canonical layering and ELT reasoning; clarifies why this layered approach is chosen.)
Related Issue: #264

Question

Why use a layered data pipeline (raw → canonical → analytics → mart) instead of directly analyzing raw data, and how do the canonical and analytics layers improve schema, metrics, and stability?

Decision Rationale

The new proposal expands the existing layered data-warehouse guidance by introducing a canonical layer and ELT reasoning, merging with current content to provide a more complete explanation without creating a separate entry.

Placement Details

  • Section ID: module-3
  • Sort Order: 51
  • Document ID: a198f6959c

🤖 Generated by FAQ Bot

Closes #264

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FAQ] Why is the pipeline structured into multiple layers instead of directly analyzing raw data?

0 participants