Skip to content

Add blog discrepancy summary document #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add blog discrepancy summary document #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/blog_post_vs_project.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Blog Post vs. Project Differences

| Blog Post Claim | Actual Project Implementation | Correction Needed |
| --- | --- | --- |
| Watermarks are stored in a dedicated `watermarks` table created by the Postgres init scripts. | The pipeline reads and writes watermarks via Airflow Variables; the Postgres bootstrap scripts only create schemas and raw tables—no `watermarks` table exists. | Update the blog/script to explain that Airflow Variables hold the incremental load watermarks (or add the table to the repo if desired). |
| DAG imports the hook from `airflow.hooks.postgres_hook`. | The DAG uses the provider package import `airflow.providers.postgres.hooks.postgres.PostgresHook`. | Align the blog/script with the provider-style import so readers copy the working code. |
| The BI user only has access to the analytics schema. | `02_bi_read.sql` grants the `bi_read` role `USAGE/SELECT` on both `public_analytics` **and** `raw`. | Either adjust the blog/script to mention the raw schema access, or tighten the SQL to restrict the role to `public_analytics` only. |